principle-exhaust-the-design-space

Guides building and comparing multiple prototypes before committing to novel design decisions.

Updated Jul 29, 2026
One-click install
npx skills add https://github.com/mmdmcy/fluttAIrbar --skill principle-exhaust-the-design-space-mmdmcy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: principle-exhaust-the-design-space
Source: https://github.com/mmdmcy/fluttAIrbar/tree/main/plugins/pstack/skills/principle-exhaust-the-design-space
Command: npx skills add https://github.com/mmdmcy/fluttAIrbar --skill principle-exhaust-the-design-space-mmdmcy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When facing a novel UI interaction or architectural decision with no precedent in the codebase, teams often commit to the first idea and pay the cost of building the wrong thing. This Skill enforces a disciplined exploration of alternatives before implementation. ## Core Features & Use Cases - Prototype Comparison: Directs building 2-3 competing prototypes or sketches and comparing them side by side before committing. - Applicability Rules: Clearly defines when the principle applies (novel UI interactions, multi-approach architecture choices, feel-driven product decisions) and when it does not (mechanical implementations, bug fixes, single-approach constraints). - Use Case: When designing a new drag-and-drop interaction with no prior art in the codebase, build three interaction prototypes, evaluate them side by side, and only then commit to one direction. ## Quick Start Ask the AI to apply the exhaust-the-design-space principle to evaluate competing approaches for a novel UI interaction before writing production code.

Frequently Asked Questions about principle-exhaust-the-design-space

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

FAQPage Schema
How do I decide between multiple architectural approaches in a codebase?▼

Build 2-3 competing prototypes or sketches representing genuinely different approaches, then compare them side by side before committing. A second flavor of the same shape does not count as a distinct alternative.

When should I prototype multiple designs before implementing?▼

Prototype multiple designs when facing novel UI interactions with no prior art in the codebase, architectural choices with several viable approaches, or product decisions where user experience depends on feel rather than logic.

When is design space exploration not necessary?▼

Skip exploration for mechanical implementations with established patterns, bug fixes or refactors with a clear target state, and changes where constraints dictate a single viable approach.

How many prototypes should I build before committing to a design?▼

Build 2-3 competing prototypes or sketches. The goal is genuine diversity of approach, since building the wrong thing costs more than exploring three options upfront.

What is the difference between design exploration and iteration?▼

Exploration compares fundamentally different shapes side by side before commitment, while iteration refines a single chosen direction. A second flavor of the first shape is iteration, not exploration.