design-exploration

Frame design problems and export structured briefs for variation generation.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/CRAJKUMARSINGH/M3_Bridge --skill design-exploration-crajkumarsingh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-exploration
Source: https://github.com/CRAJKUMARSINGH/M3_Bridge/tree/main/.local/skills/design-exploration
Command: npx skills add https://github.com/CRAJKUMARSINGH/M3_Bridge --skill design-exploration-crajkumarsingh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Frames the design problem and creates a structured brief before generating design variations, ensuring meaningful exploration rather than shallow edits.

Core Features & Use Cases

  • Reads the target component or workflow context and builds a problem model covering function, content, interaction, and constraints.
  • Identifies hard and soft constraints and articulates degrees of freedom to guide meaningful variation axes.
  • Generates a concise design brief with selected axes and concrete variation specifications, then delegates to the design subagent.
  • Applicable to requests like "generate variations", "explore alternatives", or "show me options" for components, pages, or flows.

Quick Start

Provide a component or design scenario to explore and I will return a structured brief outlining evaluation axes and three concrete design variations.

Frequently Asked Questions about design-exploration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate design variations for a component without making shallow edits?

To generate meaningful design variations, first frame the design problem by building a structured brief covering function, content, interaction, and constraints. This ensures exploration occurs across meaningful variation axes rather than superficial tweaks.

What is problem framing in design exploration and when do I need it?

Problem framing in design exploration is the process of identifying hard and soft constraints to articulate degrees of freedom. You need it when asked to explore alternatives or show options for pages and workflows, ensuring structured and purposeful variation.

How do I create a structured design brief for exploring UI alternatives?

Create a structured design brief by reading the target component context, identifying constraints, and selecting meaningful variation axes. Export this brief with concrete variation specifications to guide downstream design subagents in generating the alternatives.

Can I use this approach to explore workflow variations for complex flows?

Yes, you can explore workflow variations for complex flows. The process builds a problem model covering function and interaction, identifies degrees of freedom, and generates a concise brief with concrete variations applicable to pages and workflows.

What is the best way to guide downstream design subagents during exploration?

The best way to guide downstream design subagents is to export a concise design brief containing selected axes and concrete variation specifications. This brief acts as a clear directive, ensuring subagents generate structured and relevant design options.