design-brief

To generate a design brief for a new UI feature, you run a guided interview to extract goals and success metrics. This process compiles decisions into a standardized, shareable markdown brief for your team.

A design brief is a structured document capturing goals, constraints, and success metrics for a specific UI direction. You need one to ensure design planning is produced consistently and shared across your project team.

You can document UI design patterns by running an exploration process that surfaces design-relevant tokens, themes, and components from your codebase. These organizational patterns are then compiled directly into your design brief.

Yes, you can use a structured interview to plan onboarding flows, dashboards, or settings pages. The interview extracts the necessary feature requirements and compiles them into a standardized design brief file.

No, this design brief generation process does not require any external dependencies or components to function. It operates independently to analyze your codebase and output the templated brief file.

You should save the output file for your design documentation at the designated path of .design/<feature-slug>/DESIGN_BRIEF.md. This enforces a standardized template location for all your feature planning documents.