design-exploration

Produces a structured design brief to coordinate exploration and delegate to the design subagent.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/binan-maker/QRS --skill design-exploration-binan-maker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-exploration
Source: https://github.com/binan-maker/QRS/tree/main/.local/skills/design-exploration
Command: npx skills add https://github.com/binan-maker/QRS --skill design-exploration-binan-maker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It ensures problem comprehension before generating design variations by producing a structured design brief that guides the design subagent, preventing shallow or repetitive outputs and aligning exploration with user goals.

Core Features & Use Cases

  • Builds a comprehensive design brief by analyzing component function, content model, interactions, and constraints.
  • Identifies hard constraints, soft constraints, and degrees of freedom to ground meaningful variation axes.
  • Generates distinct design hypotheses and delegates them to the design subagent for evaluation.
  • Use Case: when a user asks for "variations," "directions," or "possibilities" for a component, trigger a brief-first exploration workflow.

Quick Start

Provide a design brief for the selected component and pass it to the design subagent.

Frequently Asked Questions about design-exploration

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

FAQPage Schema
How do I explore design variations for a component without getting repetitive results?

To explore design variations effectively, you need a structured design brief that captures component analysis, constraints, and variation axes before generating options. This approach ensures problem comprehension and aligns outputs with user goals, preventing shallow or repetitive results.

What should be included in a design brief for UX component analysis?

A UX design brief should include component function, content model, interactions, hard constraints, soft constraints, and degrees of freedom. These elements ground meaningful variation axes and generate distinct design hypotheses for evaluation.

When do I need to use a structured design brief for UX directions?

You need a structured design brief when asking for variations, alternatives, or directions for a component. It triggers a brief-first exploration workflow that coordinates divergent design exploration and delegates design hypotheses to the subagent.

How do I generate distinct design hypotheses for component variations?

Generate distinct design hypotheses by identifying hard constraints, soft constraints, and degrees of freedom from component analysis. Use these to define concrete variation axes and specifications, then delegate them to the design subagent for evaluation.

What's the best way to coordinate divergent design exploration across multiple options?

The best way to coordinate divergent design exploration is producing a structured design brief that captures component analysis and variation specifications before delegating to the design subagent, ensuring meaningful and distinct design directions.

Can I define variation axes for a component without analyzing its constraints first?

Defining variation axes without analyzing constraints risks meaningless or repetitive design options. Component analysis identifies hard constraints, soft constraints, and degrees of freedom that ground the exploration in viable design directions.