What problem does it solve? Writing a screen specification that an implementer can build from without follow-up questions is hard: project-wide standards get silently overridden, layout decisions stay in the designer's head, and vague sentences become implementation bugs. This Skill produces a binding UX spec for one screen or flow by separating cited project invariants from original design decisions extracted through a structured interview. ## Core Features & Use Cases - Standards extraction: Mines the project's art bible, ADRs, rules, and neighboring specs for invariants that are cited rather than re-decided. - Batched interview: Asks the user only about the original design of the screen — composition, layout, states, interactions — in scoped question batches with recommended options. - Template-driven writing: Selects optional modules (arrival context, transitions) based on the screen's nature and writes against a binding template with numbered sections and acceptance criteria. - Autonomous review loop: Submits the approved draft to an independent reviewer subagent with a clean context, iterates on blocking findings, and escalates after repeated failures. - Use Case: Ask to document a new inventory screen; the Skill reads the art bible, interviews you about zones and components, writes the numbered spec, gets it reviewed, and hands back a document ready for implementation issues. ## Quick Start Ask the assistant to write a UX spec for the screen or flow you want documented, naming the screen or an existing spec number to update.
