Frontend Design

Turn a resolved product problem into a visual decision. Produce three runnable directions in the repository's real frontend stack, or an explicitly approved isolated host for a true greenfield repository, capture evidence, grill the user on concrete reactions, and record the approved direction at docs/design/<feature>/DESIGN.md.

Do not use this skill to discover the product. Never invent a missing audience, workflow, content model, platform, or constraint merely to begin drawing.

Gate on prerequisites

Confirm all of these before writing visual code:

• Product intent and success criteria
• Primary audience and its priority tasks
• In-scope flows and navigation boundaries
• Real or representative content and data states
• Target platform, viewport classes, and input modes
• Brand, design-system, technical, accessibility, and delivery constraints
• A runnable frontend host, or for a true greenfield repository an explicitly approved isolated exploration scaffold and run command
• A stable feature slug for docs/design/<feature>/