design-exploration

This skill intercepts design variation requests by reading the selected component's source code and styles, identifying hard constraints and degrees of freedom, and producing a structured 2–3 variation design brief to guide the design subagent before any alternatives are generated.

You need a design brief to ensure upfront problem comprehension by defining explicit constraints and exploration axes; this prevents skipping the analysis phase and avoids passing raw file paths to the design subagent without a structured brief.

The best way to explore design directions is to analyze the component's context to identify hard constraints, soft constraints, and degrees of freedom, then outline distinct hypotheses in a structured brief to frame the subsequent exploration by the design subagent.

Yes, you can use this skill to analyze component dependencies and styles; it reads the selected component's context including source code, layout, dependencies, and styles to build a clear problem model before generating ideas.

You should not use a structured brief for divergent design exploration if your request requires direct, immediate generation without upfront problem comprehension, as this skill intercepts requests to enforce an analysis phase before delegating to the design subagent.