uxspec

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

Run a systematic quality audit on a completed UXSpec — design intent, consistency, accessibility, and state coverage

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.

Design the $machine section — map happy paths, error paths, and all state types into a complete behavioral skeleton

Define $tokens for color, typography, spacing, and timing that give a spec its visual identity

Write $visual blocks that define layout, elements, descriptions, and test hooks for each state

Connect the spec to behavior — wire up $context, $events, actions, effects, guards, and element bindings