| name | shape |
| description | Plan the UX and UI for a feature before writing code. Run a structured discovery interview, then produce a design brief (.design-context.md) that guides implementation. Establishes design direction, constraints, and strategy before any code is written. Triggers on plan the design, design brief, shape the UX, before we build, design discovery. |
| argument-hint | [feature to shape] |
Shape the UX and UI for a feature before any code is written. This skill produces a design brief — a structured artifact that guides implementation through discovery, not guesswork.
Scope: Design planning only. This skill produces design briefs, not code.
Preparation
Read ~/.claude/skills/minoan-frontend-design/SKILL.md for aesthetic principles and anti-pattern guidance. These inform the design direction but should not constrain the discovery interview.
Check for existing design context: .design-context.md in the project root, or a ## Design Context section in CLAUDE.md. If either exists, use it as a starting point — don't re-ask questions it already answers.
Phase 1: Discovery Interview
Do NOT make any design decisions during this phase. Understand the feature deeply enough to make excellent decisions later.
Interview cadence
Ask 2-3 questions per round, then wait for answers. One round is the default. Add a second only if the first answers leave material gaps — don't run a second round just to feel thorough.
Assert-then-confirm, not menu-with-escape. When the user's prompt and existing context make one option obvious, name it and ask the user to confirm or override. "This reads as Restrained, confirm?" beats a four-option menu when the answer is already clear.
