shape

To turn a feature idea into an actionable UX design brief, use a structured discovery interview to clarify user goals, content needs, and constraints before producing an implementation-guiding artifact.

A UX design brief defines structure, hierarchy, key states, and interaction models. You need one during product discovery to clarify feature requirements and prevent costly UI rework before engineering begins.

Plan a UI interaction model and layout strategy by running a discovery process that uncovers feature states and content requirements, synthesizing the findings into a comprehensive design brief for handoff.

Generating a design brief requires a mandatory context gathering protocol beforehand to ensure all user goals, data needs, and anti-goals are uncovered before finalizing the implementation-guiding document.

The best way to define feature states and content requirements for handoff is to conduct a discovery interview that explicitly outlines constraints and synthesizes them into a structured design brief.

You cannot use this design brief skill to write code or make final UI design decisions, as it is strictly scoped for planning direction, defining strategy, and shaping the feature interaction model.