design-exploration

A design exploration brief structures your design options by first analyzing a component's function, interaction model, and constraints. It then defines 2–3 meaningful variation axes across structural, semantic, behavioral, or aesthetic categories before generating alternatives.

You start a design exploration by providing a target component or design task. The system comprehends the problem by analyzing the visual structure and context, identifies constraints, and outputs a structured design brief detailing concrete variation specifications.

Yes, design exploration applies to requests for variations or alternatives across UI components, layouts, and flows. It identifies constraints and defines variation axes across structural, behavioral, conceptual, and aesthetic categories to produce design directions.

Design exploration uses a delegation workflow that passes the generated structured design brief and source file path to a design subagent. This ensures problem comprehension happens before generating variations, rather than producing direct outputs.

No, it does not output final mockups directly. Design exploration streamlines exploratory work by ensuring problem comprehension first, producing a structured design brief that is delegated to a design subagent for downstream generation steps.