UI Design Pipeline

Generic AI interfaces come from skipping decisions, not from a lack of rules. This skill forces the decisions in order: commit to a direction, lock it into a file, add motion sparingly, critique the result, then prove it in a real browser.

It is an orchestrator. It owns the sequence and the hand-offs; the specialist skills own the craft at each stage.

What This Skill Produces

• A direction statement: audience, purpose and one committed aesthetic stance, written before any code
• A persisted design system file that every later page reads, so pages do not drift
• A motion spec: what animates, how long, which easing, and what stays still
• A critique covering hierarchy, spacing, typography and "too safe vs too loud", with fixes applied
• Verification evidence: screenshots at mobile and desktop widths from a real browser, re-taken after each fix
• A stage log naming which skill handled each stage, or that the built-in fallback was used

Required Inputs