design-exploration

Use the design-exploration skill to turn vague requests into a structured design brief by analyzing your selected component, separating hard constraints from soft assumptions, and defining distinct variation axes for structural, conceptual, behavioral, and aesthetic exploration.

Component analysis in UI prototyping involves reading a selected component and its context to understand function, content, interaction, and visual structure. You need it when requests for alternatives or options require meaningful, feasible divergent exploration rather than superficial reskins.

Plan variations for divergent design exploration by selecting useful axes such as structure, concept, behavior, content, or aesthetics, ensuring the resulting hypotheses distinguish structural, conceptual, behavioral, and aesthetic differences across pages and flows.

Yes, you can use design exploration for interaction and visual structure variations. The process applies to requests for alternatives, directions, or options, distinguishing behavioral and aesthetic differences to produce delegation-ready design hypotheses across components, pages, and flows.

The best way to separate hard constraints from soft assumptions in a design brief is to perform constraint analysis on the selected component and its context, ensuring divergent exploration stays meaningful and feasible before generating any structural or aesthetic options.

Design exploration produces superficial reskins instead of distinct options when variation axes are not properly defined. Generating a structured brief with delegation-ready hypotheses that separate structural, conceptual, behavioral, and aesthetic differences ensures meaningful divergent alternatives.