// Run a systematic quality audit on a completed UXSpec — design intent, consistency, accessibility, and state coverage
Add purposeful motion to a UXSpec — $animations, onEnter choreography, and timing tokens
Improve every piece of text in a UXSpec — descriptions, labels, error messages, empty states, and loading copy
Identify repeated patterns and consolidate them into $elements and shared tokens for systematic reuse
Collect design context, audience, intent, and requirements before writing any UXSpec JSON
Strengthen a UXSpec against real-world conditions — overflow, missing data, network failures, and accessibility
Walk through building a UXSpec (.uxspec.json) file — gathering requirements, making design decisions about layout/typography/color/motion/accessibility, designing the state machine, defining visuals, then compiling and verifying the output.
| name | review |
| description | Run a systematic quality audit on a completed UXSpec — design intent, consistency, accessibility, and state coverage |
Systematic quality pass on a completed UXSpec before shipping. Checks design intent, consistency, accessibility, state coverage, and copy quality.
After all phases are complete and the spec compiles successfully. Before opening a PR or handing off for implementation.
If you showed this spec to someone and said "AI generated this," would they believe you? Check for:
$visualIf any are present, they need justification or replacement.
For each state's $visual, imagine blurring your vision:
If everything looks the same weight, spacing and typography tokens need work.
$visual?$description specific enough to produce a consistent implementation?testId?aria.label?aria.live?keyboard bindings, onEnter.focus)$events?$context?assign paths start with context.?Report findings as:
A review catches what the phases miss. Each phase focuses on building one layer; the review checks that all layers work together. The goal isn't perfection — it's confidence that the spec communicates clearly and handles the real world.