Use this skill when turning a rough feature idea or redesign request into a concrete, build-ready UI specification.
Steps
- Load repo context first: Run
exonui-context(readDESIGN.md, token files, andexonui.jsonprofile/packs) so the brief extends the existing system instead of fighting it. - Clarify missing product & UX constraints concisely: · Audience & job to be done: Who uses this screen and what action marks success? · Hierarchy & states: Primary focal point, secondary controls, plus explicit loading, empty, error, disabled, and success states. · Layout & responsiveness: Behaviour at desktop (
1280px+), tablet, and narrow mobile (360pxwith zero horizontal overflow). · Theme & accessibility: Light/dark parity, WCAG 2.2 AA contrast (4.5:1text /3:1UI), keyboard navigation order, focus visibility. · Motion intent: Purposeful transitions/micro-interactions using compositor properties (transform,opacity) with explicitprefers-reduced-motionbehaviour. - Validate colour & scale numbers early: Use
design_utils(contrast,palette,type_scale,spacing_scale) to lock accessible token pairings before coding. - Record outputs cleanly: · Summarize the brief in a concise Markdown section or update
DESIGN.md/ feature plan with explicit "Done when" criteria. · Save a Relay checkpoint (relay_checkpoint) if implementation will happen in another session or agent.
Done when
- Personas, key user flows, all UI states (loading/empty/error/success), responsive rules down to
360px, and AA contrast/motion constraints are agreed before implementation starts.