Craft Distinct UI
Create a concrete art direction before writing component code.
Workflow
- •Define intent in one sentence: user type, product tone, and business action.
- •Choose exactly one primary direction from
references/art-directions.md. - •Define a token set first: typography, spacing scale, radius, border weight, shadow, and color roles.
- •Implement one strong visual motif that appears in at least three places.
- •Build layout with clear rhythm: dense areas + breathing areas, not uniform spacing everywhere.
- •Add motion only where it supports meaning: entry hierarchy, state change, or cause/effect.
- •Run the quality gate in
references/quality-gate.mdbefore final output.
Output Contract
Return these items when generating a design:
- •Chosen direction and short rationale.
- •Token snapshot (font stack, palette roles, spacing/radius scale).
- •Key layout decisions for desktop and mobile.
- •Reusable component rules (cards, buttons, nav, section headers).
- •Final implementation code.
Execution Rules
- •Preserve the existing design system when the repository already has one.
- •Avoid default-safe stacks (
Inter,Roboto,Arial, plain system-only stacks) unless explicitly required. - •Avoid purple-first palettes and dark-mode-first assumptions unless requested.
- •Avoid generic hero + three cards + gradient blob composition unless justified by product requirements.
- •Prefer bold but readable contrast, intentional whitespace shifts, and visible hierarchy breaks.