shape

To plan UX and UI before coding, use a structured discovery interview to gather context and produce a design brief. This approach establishes design direction, constraints, and strategy during the planning phase to guide subsequent implementation.

A design brief is a document that guides feature implementation based on discovery rather than guesswork. You need it during the planning phase to ensure design direction and constraints are defined before any coding begins.

The shape skill focuses strictly on design planning and produces no code. It runs a structured discovery interview to establish UX and UI strategy, direction, and constraints before the implementation phase starts.

To start a discovery interview and create a UX design brief, describe your feature and run the Context Gathering Protocol via /impeccable. This structured process captures project requirements before generating the final design brief.

You should conduct a discovery interview before coding to avoid guesswork and establish a clear design strategy. It produces a design brief that defines constraints and direction early, ensuring subsequent implementation is properly guided.

Yes, you can use this design planning skill without external dependencies. It operates independently to run a discovery interview and generate a design brief, requiring only the /impeccable protocol to gather the necessary project context.