design-exploration

Generate structured design briefs with variation hypotheses for design exploration.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/Mo7amed-Mahmoud/ZeinaGuard-Pro --skill design-exploration-mo7amed-mahmoud
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-exploration
Source: https://github.com/Mo7amed-Mahmoud/ZeinaGuard-Pro/tree/main/.local/skills/design-exploration
Command: npx skills add https://github.com/Mo7amed-Mahmoud/ZeinaGuard-Pro --skill design-exploration-mo7amed-mahmoud

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill ensures problem comprehension before generation by constructing a structured design brief that frames divergent exploration and prevents jumping straight to outputs when users request ideas, directions, or possibilities. It intercepts requests at the main agent level to produce a clear design brief before delegating to the design subagent.

Core Features & Use Cases

  • Builds an internal model of a component (function, content model, interaction, visual structure, context) to ground exploration.
  • Identifies hard constraints, soft constraints, and degrees of freedom to map the space for variation.
  • Selects 2–3 meaningful variation axes across Structural, Content/Semantic, Conceptual, Behavioral, and Aesthetic categories.
  • Composes a structured design brief with explicit variation hypotheses and rationale to guide downstream agents.
  • Delegates the brief to the design subagent for generation while preserving comprehension and guardrails.

Quick Start

Provide a complete design brief that analyzes the selected component and outlines 2–3 distinct design variation hypotheses.

Frequently Asked Questions about design-exploration

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

FAQPage Schema
How do I generate a structured design brief for component exploration?

To build a structured design brief, analyze the selected component's function, content model, and constraints to map variation axes and produce explicit design hypotheses.

Why do I need a design brief before creating design variations?

A design brief ensures problem comprehension before generation, preventing premature outputs by framing divergent exploration and mapping hard constraints and degrees of freedom.

How do I select meaningful axes for design variation?

To select design variation axes, evaluate the component across Structural, Content/Semantic, Conceptual, Behavioral, and Aesthetic categories, then choose two to three meaningful directions.

Can I use design exploration for any UI component request?

Design exploration applies to any component selected for exploration, specifically intercepting requests for ideas, directions, or possibilities to ground the generation process.

What is the best way to map degrees of freedom in a design component?

The best way to map degrees of freedom is to identify hard and soft constraints within the component model, clarifying the available space for structural and aesthetic variations.