By gotalab
Run UX regression testing on browser-based and webview apps after E2E tests, catching usability, accessibility, and interface-quality issues with automated journey validation and heuristic checks
Journey Compiler for the uxaudit pipeline. Translates each natural-language primary_journey from project-context.json into an executable JSON action script that capture_journey.mjs can replay against the running app. Reads project-context.json + curls the running app for selector hints, writes one journey-scripts/<id>.json per journey plus the mandatory _ftue.json. Single dispatch per iteration. Invoked from Phase 03 Step 9 of the orchestrator playbook.
L3-vision Judge for the uxaudit pipeline. Reads ONE captured screenshot plus a check-specific prompt.md (and optional evaluation brief) and writes a strict pass/fail/unverifiable verdict to result.json. Has Read and Write only — physically cannot drive a browser, run curl, or grep code. Invoked from Phase 04 Step 11 of the orchestrator playbook, one dispatch per L3 check, batched in parallel.
L4-journey Judge for the uxaudit pipeline. Reads the per-journey capture directory (screenshots + steps.json + evaluation brief) and writes a strict pass/fail/unverifiable verdict with four-axis journey_evaluation to result.json. Has Read, Write, Glob — no Bash, no WebFetch — physically cannot drive a browser or curl the app. Invoked from Phase 04 Step 11 of the orchestrator playbook, one dispatch per L4 journey, batched in parallel.
Project locator for the uxaudit pipeline. Maps a repository, enumerates dev-server candidates per sub-app (URL + start command + running state + auditability), identifies shared design-token packages, and flags out-of-scope native siblings. Writes project-locator.json. Pure file-reading + port-probing — no taste judgments. Invoked from Phase 01 Step 2 of the orchestrator playbook.
Proposer for the uxaudit pipeline. Runs after Reconciler, producing the cross-check synthesis. Compresses a long per-check failure list into 2-3 ranked, project-aware fix proposals anchored to root causes. The first (and only) subagent allowed to see BOTH the Scout's project-context.json AND the Judges' verdicts — the Judge's verdicts are already locked by the time the Proposer runs, so there is no rationalization risk. Writes improvement-proposal.json conforming to schemas/improvement-proposal.schema.json. Single dispatch per iteration. Invoked from Phase 05 Step 15 of the orchestrator playbook.
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A Claude Code plugin for UX regression testing — evaluates whether people can understand, decide, act, and recover across real user journeys.
[!WARNING] Status: Experimental. UX Audit is still evolving, and interfaces, outputs, checks, and workflows may change without notice.
Every check cites a published source (WCAG 2.2, NN/g, Nielsen, Krug, Baymard, ISO 9241) — no vibes. Built for teams shipping fast with Claude Code and coding agents.
Actual run on a sample recipe app — journey scenarios were auto-generated, each walked on the live app:
Try it
# Inside Claude Code — URL is auto-detected from your project config
/uxaudit:uxaudit my-app
Quick catalog-only check (skip journey evaluation):
/uxaudit:uxaudit my-app --skip core-experience
Host support
/uxaudit:uxaudit.skills/uxaudit/ bundle is being designed to be portable, and broader host support is on the roadmap.Maturity: experimental. Catalog checks, capture pipeline, dashboard, and history/compare views are used today; richer decide / recover evaluation and tighter host portability are still being built out. A full audit (catalog + journey evaluation) typically takes 30–60 minutes in Claude Code; Max plan is recommended for regular use.
uxaudit runs ~40 checks grouped into five categories. Every check is backed by a published source — no opinion-only findings.
| Category | What it checks | Example findings |
|---|---|---|
| ai-slop | Fingerprints of AI-generated UI | purple gradients, shadcn defaults everywhere, "coming soon" stubs, emoji-as-icon, generic hero copy |
| accessibility | WCAG 2.2 AA floor | contrast, tap targets, focus rings, keyboard reach, axe-core violations |
| usability | Nielsen heuristics & journey continuity | dead-end flows, missing empty states, weak error recovery, inconsistent feedback |
| core experience | Primary journey completion | can a new user actually sign up, create the first thing, and share it? |
| desirability | Visual craft, microcopy, first impression | typography drift, generic voice, weak aesthetic impression |
Full citation list: skills/uxaudit/references/knowledge/sources.md.
| Playwright / Cypress | axe / Lighthouse | uxaudit | |
|---|---|---|---|
| Does the user flow execute? | ✅ | — | — |
| WCAG AA violations? | — | ✅ | ✅ (floor) |
| Core Web Vitals / perf? | — | ✅ | — |
| Can a new user reach first value without friction? | — | — | ✅ |
| Dead-end / recovery / decision-cost checks? | — | — | ✅ |
| AI-slop & design-system drift detection? | — | — | ✅ |
| Ranked fix plan with evidence & history? | — | — | ✅ |
E2E tells you the flow runs. uxaudit tells you the flow makes sense while running. It is meant to sit between your test suite and manual review — most teams run it between "E2E passes" and "merge".
See Overview and positioning for the longer explanation.
The dashboard is designed to be actionable:
UX issues / UI risk signals)
The report also makes it easy to inspect the difference between failures and healthy surfaces, so reviewers do not mistake "we found issues" for "everything is broken."

npx claudepluginhub gotalab/uxaudit --plugin uxauditUX testing toolkit for Claude Code — generate user journey stories, walk them through a real browser, and implement the issues found.
Persona-based user testing agent that simulates realistic user interactions with web applications. Embodies different user archetypes (Boomers, Millennials, Gen Z, Gen Alpha) with authentic behaviors, timing patterns, and frustration triggers to identify UX issues before real users do.
Audit and improve front-end usability using 15 established design principles. Acts as a Senior UX designer/engineer reviewing your interface end-to-end.
QA skills for accessibility-testing domain.
UX co-pilot — conversational UX designer with live preview. 376 rules, 161 palettes, 57 font pairings, 67 styles. Phases: Discovery (ABCD questions), Audit (code scan + scored report), Preview (local server + named versions), Export (spec + React/Svelte/Vue components).
Complete creative writing suite with 10 specialized agents covering the full writing process: research gathering, character development, story architecture, world-building, dialogue coaching, editing/review, outlining, content strategy, believability auditing, and prose style/voice analysis. Includes genre-specific guides, templates, and quality checklists.