shape

Run a structured discovery interview covering the feature's purpose, users, content ranges, design goals, and constraints, then synthesize the answers into a design brief. This Skill automates that process and requires explicit confirmation of the brief before finishing.

A design brief is a structured artifact describing a feature's summary, primary user action, design direction, layout strategy, key states, interaction model, and content requirements. It guides implementation so code decisions are grounded in discovery rather than guesswork.

No, this Skill explicitly does not write code. Its scope is design planning only, producing a brief that can be handed off to implementation skills such as /impeccable craft or any other build approach.

Use design planning when the feature's purpose, users, or states are unclear, or when consistency with existing product patterns matters. Skip it only for trivial changes where the design direction is already established.

Ask about the problem it solves, the specific users, realistic content ranges and edge cases, the single most important user action, technical and accessibility constraints, and anti-goals describing wrong directions.