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 does NOT write code. It produces the thinking that makes code good.

Output: A design brief that can be handed off to any implementation skill.

Context Gathering

Before the interview, ground yourself in the project so the brief reflects what already exists:

• Design context — if the repo carries any of PRODUCT.md, DESIGN.md, .impeccable.md, or a ## Design Context block in .github/copilot-instructions.md, read it. Skip silently if none exist.
• Existing system — read the established design system (CSS / tokens / theme and one representative component or page) to learn the conventions in play. Use what's there; branch out only when the UX wins.
• Register — decide whether design is the product (marketing, landing, portfolio → identity and boldness lead) or design serves the product (app, dashboard, tool → clarity and restraint lead). This frames every direction choice below.

Philosophy

Most AI-generated UIs fail not because of bad code, but because of skipped thinking. They jump to "here's a card grid" without asking "what is the user trying to accomplish?" This skill inverts that: understand deeply first, so implementation is precise.

Phase 1: Discovery Interview