What problem does it solve? Design specs often reach engineering with missing UI states, hardcoded style values, or accessibility gaps that cause rework. This Skill validates ux-flow-spec and ui-component-spec artifacts against user goals, design-system tokens, and accessibility requirements before Frontend implementation begins. ## Core Features & Use Cases - Spec Completeness Validation: Enforces the five critical UI states (Empty, Loading, Populated, Error, Unauthorized) on every screen spec and classifies findings as blocking, should-fix, or suggestion. - Token & AI-Generated UI Conformance: Checks Figma variable mappings, rejects hardcoded hex colors and magic spacing, and runs axe-core plus namespace-pollution checks on outputs from v0.dev, Galileo, or Builder.io. - Use Case: Before handing a checkout redesign to Frontend, run this Skill to verify the flow spec covers all error and permission states, confirm dark-mode token contrast, and emit a severity-classified findings report for the UI/UX Designer. ## Quick Start Use the design-review skill to critique this ux-flow-spec and ui-component-spec against our design-system tokens and list any blocking findings before implementation.