design-exploration

Analyze a component and create a structured design brief before generating variations.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/mecolejr/EVL-mOC5 --skill design-exploration-mecolejr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-exploration
Source: https://github.com/mecolejr/EVL-mOC5/tree/main/.local/skills/design-exploration
Command: npx skills add https://github.com/mecolejr/EVL-mOC5 --skill design-exploration-mecolejr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The design exploration skill ensures problem comprehension precedes generation by creating a structured design brief before proposing variations, preventing premature outputs and aligning intent with design objectives.

Core Features & Use Cases

  • Builds an internal understanding of a component by analyzing its function, content, interaction, and context to ground design decisions.
  • Identifies hard constraints, soft constraints, and degrees of freedom to map the space of meaningful variations.
  • Selects 2–3 high-impact variation axes (structural, content/semantic, conceptual, behavioral, or aesthetic) and composes a concrete design brief for the design subagent.
  • Creates a precise, multi-step brief that communicates hypotheses, trade-offs, and evaluation criteria for exploration.
  • Applies to requests like “generate variations,” “explore alternatives,” or when a user selects a component and asks for ideas, directions, or possibilities.

Quick Start

Ask the agent to generate a design exploration brief for a component before requesting 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 without getting premature or misaligned outputs?

To generate effective design variations, you must first create a structured design brief. This ensures problem comprehension precedes generation by analyzing component constraints, mapping degrees of freedom, and defining high-impact variation axes before producing outputs.

What is a design brief in the context of component analysis and exploration?

A design brief is a structured document that communicates hypotheses, trade-offs, and evaluation criteria for exploration. It maps the space of meaningful variations by analyzing component function, context, and interaction to align intent with design objectives.

How do I choose meaningful variation axes for divergent design exploration?

Choose 2-3 high-impact variation axes by identifying hard constraints, soft constraints, and degrees of freedom. Select from structural, content/semantic, conceptual, behavioral, or aesthetic categories to compose a concrete design brief.

Can I use a design exploration brief for generating UI alternatives and directions?

Yes, you can use a design exploration brief when you request divergent exploration or select a component for ideas, directions, or possibilities. It applies to requests like generating variations or exploring alternatives by building an internal understanding of the component.

When should I not use a structured brief before generating design variations?

You should avoid using a structured brief if you need rapid, unconstrained ideation without alignment. The brief prevents premature outputs by ensuring problem comprehension, which may slow down immediate, spontaneous design generation.