ux-audit
ux audit
What it does
- Pass — Critical = 0, High = 0, all hard gates green, Interaction Manifest complete.
- Conditional Pass — Critical = 0, High = 0, all hard gates green, but Medium/Low present.
- Fail — at least one Critical or High finding, OR a hard gate red.
- One screenshot
- One console read
- One network request inventory
- One element selector query
Requirements & configuration
- The audit needs a persona before anything else. Without a locked persona, findings drift toward generic "looks fine".
- Every checkbox needs a tool call (a click, a screenshot, a console read) and the timestamps + selectors are logged. The agent cannot produce a "Pass" report without a complete manifest.
- | Is there a discoverable list of valid values when something needs to be entered? | Free-text inputs where a combobox should be |
- Component-level granularity that page-level audits miss. Six categories, each with concrete yes/no checks that need proof artefacts:
- | AI-tell catalogue, optical centring, design-token discipline | references/visual-polish.md |
Configuration: APP_URL
Derived from the skill's own SKILL.md documentation · extracted 2026-07-23
ux-audit FAQ
What does the ux-audit skill do?
Walk through a live web app AS a real user to find usability + behavioural bugs that static reviews miss. REQUIRES proof of interaction (typing, clicking, sending, observing) before any verdict — a sweep that didn't interact terminates with verdict 'Incomplete'. Walks threads, exercises every element, runs the multi-pane stress matrix, visual polish sweep, component perfection checklist, automated a11y (axe-core), pragmatic performance budget (LCP/CLS/INP), scenario battery (11 scenarios), and stress recipes including the real-flavour data battery. Hard gates: console errors/warnings = 0, network 5xx = 0, layout collapse = 0, axe Critical/Serious = 0, perf budget green. Audit-the-audit meta-check rejects rushed reports. Each finding has reproduction steps, evidence path, and suspected code location. Trigger with 'ux audit', 'walkthrough', 'qa sweep', 'audit the app', 'dogfood this', 'check all pages', 'find what's broken', 'stress the UI'. Pass — Critical = 0, High = 0, all hard gates green, Interaction Manifest complete. Conditional Pass — Critical = 0, High = 0, all hard gates green, but Medium/Low present.
What does ux-audit require?
The audit needs a persona before anything else. Without a locked persona, findings drift toward generic "looks fine". Every checkbox needs a tool call (a click, a screenshot, a console read) and the timestamps + selectors are logged. The agent cannot produce a "Pass" report without a complete manifest. | Is there a discoverable list of valid values when something needs to be entered? | Free-text inputs where a combobox should be | Component-level granularity that page-level audits miss. Six categories, each with concrete yes/no checks that need proof artefacts: | AI-tell catalogue, optical centring, design-token discipline | references/visual-polish.md | Configuration keys: APP_URL.
How do I install ux-audit?
Run: npx -y skills add https://github.com/jezweb/claude-skills --skill ux-audit --agent claude-code — the source lives at github.com/jezweb/claude-skills.
Maintain ux-audit?
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-audit on getagentictools](https://getagentictools.com/skills/jezweb-claude-skills-ux-audit?ref=badge) npx agentictools info skills/jezweb-claude-skills-ux-audit The second line is the CLI lookup for this page — handy in READMEs and docs.