design-exploration

Generates structured design briefs for divergent component variation exploration.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/AmirEmad11/instabot --skill design-exploration-amiremad11
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-exploration
Source: https://github.com/AmirEmad11/instabot/tree/main/.local/skills/design-exploration
Command: npx skills add https://github.com/AmirEmad11/instabot --skill design-exploration-amiremad11

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When users ask for design variations, agents often skip analysis and produce shallow reskins of the same idea. This Skill enforces a comprehension-first workflow that analyzes a component's function, constraints, and degrees of freedom before delegating generation to a design subagent. ## Core Features & Use Cases - Component Comprehension: Reads source code and context to model function, content, interaction, and visual structure before any generation. - Variation Axis Selection: Chooses 2-3 meaningful axes (structural, content, conceptual, behavioral, aesthetic) based on where the user is in the exploration funnel. - Structured Design Briefs: Produces a brief naming distinct design hypotheses with rationale, then delegates it to the design subagent instead of passing raw file paths. - Use Case: A user selects a pricing section and asks to "show me options." The Skill analyzes the component, holds the comparison-table structure fixed, and varies content hierarchy and conceptual framing to produce three genuinely different design hypotheses. ## Quick Start Select a component and ask the agent to generate variations or explore alternative design directions for it.

Frequently Asked Questions about design-exploration

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

FAQPage Schema
How do I generate meaningful UI design variations instead of reskins?

Analyze the component's function, constraints, and degrees of freedom first, then select 2-3 variation axes such as structural or conceptual. Each variation should represent a distinct design hypothesis, not the same layout with different colors or fonts.

What is a design brief for component variation exploration?

A design brief is a structured document covering component analysis, hard and soft constraints, chosen variation axes with rationale, and concrete variation specifications. It is passed to the design subagent so generation is grounded in reasoning rather than a raw file path.

When should I use structural versus aesthetic variation axes?

Use structural and conceptual axes for complex components like pages, flows, and dashboards. Use aesthetic axes for visually-driven components like cards or heroes, or when the user gives tonal signals like "more premium" or "more playful."

Why do my generated design variations all look the same?

Variations look the same when they answer the same design question with only color, font, or spacing changes. This happens when comprehension is skipped; fix it by varying distinct axes like information hierarchy or interaction paradigm.

Can this skill handle vague requests like "show me options"?

Yes. When the user gives no direction, the skill analyzes the component to find axes with the most unexplored space, defaulting to structural and conceptual axes for complex components and structural plus aesthetic axes for simple visual ones.