design-exploration

To generate meaningful UI design variations, you need a structured design brief that analyzes component context, identifies constraints, and selects variation axes to ensure testable divergences rather than superficial aesthetic changes.

A structured design brief is a document that analyzes a target component's function, content, interaction, and context. You need one when requesting design variations to ensure rigorous problem comprehension before generating visual directions or possibilities.

You identify constraints and degrees of freedom by analyzing the target component's function, content, interaction, and context. This process distinguishes hard limits from soft constraints, enabling the selection of meaningful variation axes for downstream design exploration.

You should use structural, content or semantic, conceptual, behavioral, and aesthetic variation axes to explore different design directions. Selecting these axes helps articulate concrete design hypotheses and guide the generation of testable component variations.

You do not need any specific design tools or dependencies to create a design brief. The process works by describing your target component and asking for variations, which triggers the brief composition without requiring external packages or modules.

Design exploration produces inconsistent results when it lacks a structured brief to define degrees of freedom and variation axes. Generating a detailed brief before delegating to a design subagent ensures repeatable and testable exploration across components.