What problem does it solve? It converts an approved design.md into a precise, developer-facing specification so engineers build from real component-library names and design tokens instead of bespoke, ad-hoc UI decisions. ## Core Features & Use Cases - Component resolution: Maps every screen element to the target project's own component library, or to shadcn/ui registry names under the declared default, with binding > default > TBD precedence. - Complete state coverage: Specifies empty, loading, error, and populated states per component, plus responsive behavior, interactions, and edge cases, with zero raw px/hex values. - Acceptance obligation preservation: Carries canonical acceptance obligations, component-states JSON declarations, and rendered-review plans into the spec for downstream verification. - Use Case: After the design phase approves design.md for a feature, run this skill to produce spec.md with a deduplicated components-to-install list and a design-system gaps report that the issues phase turns into setup work. ## Quick Start Run the spec phase over the approved design.md in the current feature directory to generate spec.md with component mappings, states, and install lists.
