Fintech design
Skill Dragoon0x/everything-design-taste/skills/fintech-design
Financial product design patterns including banking UX, trading interfaces, and money management.From its SKILL.md
npx -y skills add Dragoon0x/everything-design-taste --skill fintech-designAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 9 stars9 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.
SKILL.md
1.3 KB, 236 tokens by cl100k_base, as published. Nobody here has run it
Fintech Design
Fintech Design Principles
- Trust over novelty. Users are anxious about money. Calm, stable interfaces reduce anxiety.
- Show real numbers. Don't hide balances, fees, or transaction details.
- Explain jargon. APY, ACH, SWIFT — if a term isn't universally understood, define it inline.
- Confirm destructive actions. Money transfers get confirmation screens with full details.
- Show transaction status clearly. Pending, Processing, Completed, Failed — each needs distinct visual treatment.
Patterns
- Balance display: Large, prominent, always visible. Show pending separately.
- Transaction list: Date, description, amount, status. Debit in red, credit in green.
- Transfer flow: Amount → Recipient → Review → Confirm → Success.
- Security: 2FA prompts, session timeout warnings, suspicious activity alerts.
Compliance
- Required disclosures must be visible, not buried in footnotes.
- Consent checkboxes for terms (not pre-checked).
- Accessible design is legally required in many jurisdictions.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most finance skills give in 236 tokens
Counted across 469 of the 469 authors here whose files we hold, read 2026-08-07
- Extract date vendor amount and descriptionin 15 of 469, across 3 files
- Scan folder for invoice filesin 14 of 469, across 2 files
- Rename files to standard formatin 14 of 469, across 2 files
- Show organization plan before movingin 14 of 469, across 2 files
- Generate summary CSVin 14 of 469, across 2 files
- Organize files by categoryin 13 of 469, across 1 file
- Preserve original filesin 13 of 469, across 1 file
- Flag files missing critical infoin 13 of 469, across 1 file
- Produce the requested output filein 9 of 469, across 4 files
- Build best, base, and worst case scenariosin 9 of 469, across 5 files
- Implement backoff if rate limit errors occurin 8 of 469, across 3 files
- Determine the weighted average cost of capitalin 8 of 469, across 4 files
Said here and by no other author read
- prioritize calm stable interfaces
- show real balances fees and transactions
- define unfamiliar financial terms inline
- add confirmation screens for transfers
- give each transaction status distinct visual treatment
- display balances prominently and separately show pending
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.