principle-exhaust-the-design-space

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

1|Updated Aug 27, 2025

Search Tags:#prototyping #architecture decisions #engineering principles #ui interaction #design exploration #side-by-side comparison

One-click install

npx skills add https://github.com/IgorGanapolsky/Random-Timer --skill principle-exhaust-the-design-space-igorganapolsky

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: principle-exhaust-the-design-space
Source: https://github.com/IgorGanapolsky/Random-Timer/tree/main/.cursor/skills/principle-exhaust-the-design-space
Command: npx skills add https://github.com/IgorGanapolsky/Random-Timer --skill principle-exhaust-the-design-space-igorganapolsky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When facing a novel UI interaction or architectural decision with no precedent in the codebase, committing to the first idea often leads to 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, architectural choices with multiple viable approaches, feel-driven product decisions) and when it does not (mechanical implementations, bug fixes, single-approach constraints). - Use Case: When designing a new gesture-based navigation pattern with no prior art in the codebase, build three distinct interaction prototypes, evaluate them side by side, and only then select the approach to implement. ## 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?▼

Build 2-3 competing prototypes or sketches and compare them side by side before committing. A second flavor of the first shape does not count as a genuine alternative, so each prototype must represent a distinct approach.

When should I prototype multiple designs before coding?▼

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

When is design space exploration not needed?▼

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

What counts as a valid alternative prototype?▼

Each prototype must be a genuinely different shape or approach, not a minor variation of the first idea. The goal is real comparison across distinct options, since building the wrong thing costs more than exploring three options.