ux-audit
Real-user dogfooding with emotional friction tracking, click efficiency counting, and resilience testing to produce ranked audit reports.
- Supports three operating modes: UX Walkthrough (persona-based task completion), QA Sweep (systematic feature testing), and Targeted Check (focused area validation)
- Tracks emotional friction signals (trust, anxiety, confusion), click efficiency, form resilience (mid-navigation, back button, refresh), and asks "would I come back?"
- Three depth levels (quick 5–10 min, standard 20–40 min, thorough 1–3 hours overnight) with autonomy scaling; thorough mode includes multi-persona testing, responsive breakpoint screenshots, automated layout detection, and six scenario tests
- Auto-detects Chrome MCP (for authenticated sessions) or Playwright; resolves URLs from wrangler.jsonc, deployed endpoints, or local dev servers; produces structured markdown reports with findings ranked by severity
UX Audit (v2)
Walk through a live web app AS a real user. The audit is interaction-first — typing, clicking, sending, watching, screenshotting. A static DOM sweep cannot produce a verdict.
Why this skill exists in v2
Most catastrophic UX bugs only surface under interaction:
- The Send button that doesn't clear the input
- The @-mention picker that double-inserts the handle
- The thread pane that breaks layout when the sidebar is also open at 1280px
- The form submit that disables the button but silently 5xx's
- The console warning that's been logging for weeks but no audit ever flagged
A DOM probe sees none of these. They require: type → wait → screenshot → diff → console-read → repeat. The previous audit method drifted toward sweep mode (faster, feels productive, blind to behaviour). v2 makes that drift impossible — the agent cannot output "Pass" without an Interaction Manifest that proves real clicks happened.
Verdict states
The audit ends in exactly one of:
More from jezweb/claude-skills
tailwind-v4-shadcn
|
2.7Ktanstack-query
|
2.5Kshadcn-ui
Install and configure shadcn/ui components for React projects. Guides component selection, installation order, dependency management, customisation with semantic tokens, and common UI recipes (forms, data tables, navigation, modals). Use after tailwind-theme-builder has set up the theme infrastructure, when adding components, building forms, creating data tables, or setting up navigation.
2.5Ktailwind-theme-builder
>
2.2Kfastapi
|
2.0Kcolor-palette
>
1.9K