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
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.
Verdict states
The audit ends in exactly one of:
- 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.
- Incomplete — Interaction Manifest missing required entries, a phase wasn't run, OR the audit-the-audit meta-check fires (manifest timestamps clustered < 0.5s apart, screenshots fewer than 2 × routes, console reads fewer than 1 × routes, Phase 3 took < 1m for an exhaustive audit). Not legal to upgrade to Pass even if everything observed looked fine.
If the work doesn't include a complete Interaction Manifest, the only legal verdict is Incomplete. "It looked OK" is not Pass. A clean Pass with implausible timings is rejected — the agent must redo the audit with real interaction.
Hard gates
These auto-fail the audit. They cannot be downgraded.
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
Set up Tailwind v4 + shadcn/ui themed UI with dark mode. Install deps, configure CSS variables via @theme inline, wire dark mode toggle, verify. Use whenever the user mentions Tailwind v4, setting up Tailwind theming, shadcn/ui colours, dark mode, or troubleshooting colours not working, tw-animate-css errors, @theme inline conflicts, @apply breaking after upgrade, or v3 → v4 migration issues.
2.2Kfastapi
|
2.0Kcolor-palette
Generate complete, accessible colour palettes from a single brand hex. Produces 11-shade scale (50-950), semantic tokens, dark mode variants, Tailwind v4 CSS output, WCAG contrast checks. Use whenever the user supplies a brand hex and asks for a palette, mentions setting up a design system, wants Tailwind theme colours from a brand colour, or asks to check colour accessibility / contrast.
1.9K