shape

Run a structured discovery interview covering purpose, audience, content ranges, edge cases, and constraints, then synthesize answers into a design brief. This Skill automates that process and requires explicit confirmation of the brief before implementation begins.

A design brief should include a feature summary, primary user action, design direction, layout strategy, key states (empty, loading, error, success), interaction model, content requirements, recommended references, and open questions for the implementer.

No, this Skill is scoped to design planning only and explicitly does not write code. Its output is a design brief meant to be handed off to implementation skills such as /impeccable craft or other build workflows.

Use discovery when the feature's user goals, data ranges, or edge cases are unclear, or when skipping thinking has previously led to generic UI output. For a combined discovery-and-build flow, use /impeccable craft, which runs this Skill internally.

The brief captures intent but cannot resolve every implementation detail, so it includes an open questions section for issues the implementer must settle during the build. It also depends on the quality of answers given during the interview phase.