Usability Heuristics Audit Skill

What this skill changes vs. default behavior

Without this skill, a usability review tends to produce a flat list of generic suggestions ("make it cleaner", "improve the CTA") with no framework, no severity, and no link to why something is a problem. This skill forces four things:

1. Every finding names the heuristic it violates — not a vague opinion.
2. Every finding gets a severity rating based on frequency × impact × persistence — so the list is prioritized, not equal-weighted.
3. Every finding has a concrete, specific fix — not "consider improving."
4. The audit resists over-flagging. Heuristics are principles, not a checklist to max out. A finding only earns a place if it plausibly costs a real user time, confidence, or task completion.

Scope discipline. When invoked directly (the user named this audit), review only this concern — don't pull in sibling audits. It runs alongside other lenses only when an orchestrator (ux-design-review) or a generative skill calls it under docs/orchestration-policy.md, where it sits in Tier A — always-relevant, auto-runs. Explicit scope always wins.

The 10 heuristics — what to check and what a violation looks like

Work through each. For every issue, capture: violated heuristic, severity, what's wrong, fix.