design-exploration

A structured design brief for component variations captures constraints and hypotheses before generating divergent outputs. It identifies hard vs soft constraints and selects meaningful variation axes to ensure design exploration is grounded in rigorous problem comprehension.

To explore design variations, provide the component context to trigger a comprehension-first analysis. The system reads component behavior, identifies constraints and freedoms, selects variation axes, and outputs a structured brief with 2-3 distinct hypotheses for downstream delegation.

Yes, you can use this to plan design directions for user journeys. It analyzes journey constraints and behaviors to build a concise design brief, identifying hard vs soft constraints before delegating the composed brief to a design subagent for structured exploration.

You need to analyze constraints before generating design variations to ensure divergent outputs are grounded in understanding. Comprehension-first exploration distinguishes hard vs soft constraints and identifies component freedoms, preventing unstructured or irrelevant design directions.

The best way to structure a design brief for downstream agents is to capture component behavior, constraints, and freedoms. Identify hard vs soft constraints, select meaningful variation axes, and output a structured brief with 2-3 distinct hypotheses for evaluation.

Yes, this approach works for both interfaces and journeys. When applied to components, interfaces, or journeys, it reads the context, identifies constraints, selects variation axes, and outputs a structured brief for downstream agents to explore design variations.