Cognitive ux finance
Research-traceable UI/UX skills for AI coding agents.
npx -y skills add kfeng209-oss/cognitive-ux --skill cognitive-ux-financeAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 25 days oldThe repository was created 25 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Design and audit banking, lending, investing, payments, and financial self-service websites using evidence-informed UX. Use when people must understand financial status, terms, risks, fees, eligibility, or move money; return disclosure hierarchy, transaction confirmation/recovery, security and fraud-support flow, accessible design checks, and informed-decision validation.
SKILL.md
2.7 KB, 449 tokens by cl100k_base, as published. Nobody here has run it
Cognitive UX: Financial Self-Service
Scope
Use for financial customer-facing experiences. It is not financial, legal, security, or regulatory compliance advice; require qualified review for the product and jurisdiction.
Intake
- Identify financial task, consequence/irreversibility, product terms, eligibility, risk, and jurisdiction.
- Identify fees, conflicts, timing, recurring effects, authentication, fraud/dispute, and receipt requirements.
- Identify user literacy, language, disability, device, support, and escalation needs.
State assumptions that could change the design. Define the primary task, its consequence of failure, and a measurable user outcome before proposing a layout.
Design procedure
- Make material costs, risks, conflicts, eligibility, timing, and irreversible consequences understandable before action.
- Use plain-language summaries with direct paths to complete terms; do not visually overshadow a material condition.
- Require meaningful review and confirmation for consequential actions; show what will happen, when, to whom, and how to recover or dispute.
- Design authentication, limits, status, receipt, fraud, and dispute flows with clear next steps and appropriate verification.
- Test comprehension and error prevention across users, not only transaction completion or revenue.
Read archetype evidence. Label each non-obvious recommendation Standard / requirement, Evidence-informed default, or Hypothesis to test.
Required outputs
- financial decision/disclosure hierarchy
- consequential-action review/confirmation/receipt flow
- authentication/fraud/dispute support model
- accessibility and plain-language checklist
- informed-decision and critical-error test
- Evidence-to-decision table: decision → mechanism → source → label → limitation → test metric.
- Accessibility, ethics, and recovery-path checklist.
Guardrails
Do not bury material terms, use misleading defaults, trivialize risk, gamify financially harmful behavior, or make a compliance claim without expert review.
Related skills
Use cognitive-ux-portal, cognitive-ux-commerce, and cognitive-ux-forms. Select the primary task before combining skills; add a secondary skill only when it changes the user outcome or risk.