ux-heuristics
ux heuristics
What it does
- Clever names lose to clear names every time
- Marketing-speak creates friction; plain language removes it
- Unfamiliar categories force users to stop and interpret
- Ambiguous links and buttons cause hesitation
- Action-oriented buttons: verb + noun ("Create account", "Download report")
- Avoid jargon: "Save" not "Persist", "Remove" not "Disassociate"
- If a label needs explanation, simplify the label
Requirements & configuration
- If a label needs explanation, simplify the label
- Three mindless clicks beat one click that requires deliberation
- Before: "Please kindly note that you will need to enter your password in order to proceed to the next step." → After: "Enter your password to continue."
- Provide clear "emergency exits." Undo beats "Are you sure?" dialogs — users click through confirmations without reading. Every flow needs cancel/exit, and back buttons must never break.
- | Does anything make me stop and think "huh?" | Cognitive load too high | Simplify — if it needs explanation, redesign it |
Derived from the skill's own SKILL.md documentation · extracted 2026-07-23
ux-heuristics FAQ
What does the ux-heuristics skill do?
Evaluate and improve interface usability using heuristic analysis. Use when the user mentions "usability audit", "users are confused", "form usability", "navigation problems", "Nielsen heuristics", "cognitive walkthrough", or "is this easy to use". Also trigger when reviewing a design for usability issues, improving form-completion rates, or evaluating information architecture and navigation. Covers Krug''s laws, Nielsen''s 10 heuristics, severity ratings, dark-pattern recognition, and accessibility. For visual design fixes, see refactoring-ui. For conversion-focused audits, see cro-methodology. Clever names lose to clear names every time Marketing-speak creates friction; plain language removes it
What does ux-heuristics require?
If a label needs explanation, simplify the label Three mindless clicks beat one click that requires deliberation Before: "Please kindly note that you will need to enter your password in order to proceed to the next step." → After: "Enter your password to continue." Provide clear "emergency exits." Undo beats "Are you sure?" dialogs — users click through confirmations without reading. Every flow needs cancel/exit, and back buttons must never break. | Does anything make me stop and think "huh?" | Cognitive load too high | Simplify — if it needs explanation, redesign it |
How do I install ux-heuristics?
Run: npx -y skills add https://github.com/wondelai/skills --skill ux-heuristics --agent claude-code — the source lives at github.com/wondelai/skills.
Maintain ux-heuristics?
Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.
[ux-heuristics on getagentictools](https://getagentictools.com/skills/wondelai-skills-ux-heuristics?ref=badge) npx agentictools info skills/wondelai-skills-ux-heuristics The second line is the CLI lookup for this page — handy in READMEs and docs.