design-exploration

Analyze component context and constraints to compose a structured design brief.

Updated Dec 1, 2025
One-click install
npx skills add https://github.com/KartikSharma4448/MyPortfolio --skill design-exploration-kartiksharma4448
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-exploration
Source: https://github.com/KartikSharma4448/MyPortfolio/tree/main/.local/skills/design-exploration
Command: npx skills add https://github.com/KartikSharma4448/MyPortfolio --skill design-exploration-kartiksharma4448

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures the agent performs problem comprehension before generation when handling requests for variations, reads the target component to understand its function, constraints, and potential degrees of freedom, and produces a structured design brief to guide downstream design actions.

Core Features & Use Cases

  • Read and analyze the selected component's function, content model, interaction model, visual structure, and context to build a comprehensive internal model.
  • Identify hard constraints, soft constraints, and degrees of freedom to inform meaningful variation strategies.
  • Select meaningful variation axes across structural, content/semantic, conceptual, behavioral, and aesthetic dimensions to maximize exploration impact.
  • Compose a structured design brief that documents analysis, constraints, axes, and concrete variation specifications for the design subagent.
  • Delegate with the brief to the design subagent, ensuring each variation is a distinct design hypothesis and not a mere color or copy.

Quick Start

Provide a structured design brief to the design subagent before starting any variation exploration.

Frequently Asked Questions about design-exploration

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

FAQPage Schema
How do I generate structured design briefs for UX design variations?

To generate structured design briefs for UX design variations, use an agent that reads component context, identifies constraints, selects variation axes, and composes a structured brief to pass to a design subagent.

Why do my design variations look like simple color or copy changes?

Design variations often look like simple color or copy changes because analysis is skipped. Composing a structured design brief beforehand ensures each variation is treated as a distinct design hypothesis rather than a superficial tweak.

How do I identify constraints and degrees of freedom before exploring design alternatives?

To identify constraints and degrees of freedom before exploring design alternatives, read the target component to understand its function, content model, and interaction model, then document hard constraints, soft constraints, and variation axes.

What is the best way to explore design variations across different dimensions?

The best way to explore design variations across different dimensions is to select meaningful variation axes spanning structural, content, conceptual, behavioral, and aesthetic categories to maximize exploration impact.

Can I use a structured brief to guide a design subagent through component ideation?

Yes, you can use a structured brief to guide a design subagent through component ideation by delegating the brief document, which ensures the subagent receives concrete variation specifications based on prior component analysis.

Does design thinking require problem comprehension before generating variations?

Design thinking requires problem comprehension before generating variations to ensure the agent reads the target component, builds a comprehensive internal model, and produces a structured design brief to guide downstream design actions.