principle-exhaust-the-design-space

Builds competing prototypes to compare alternatives before committing to novel design decisions.

4|1|Updated Dec 16, 2023

Search Tags:#design patterns #prototyping #ui design #architecture decisions #design exploration #side-by-side comparison

One-click install

npx skills add https://github.com/Shtian/AuthentiClash --skill principle-exhaust-the-design-space-shtian

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: principle-exhaust-the-design-space
Source: https://github.com/Shtian/AuthentiClash/tree/main/.claude/skills/principle-exhaust-the-design-space
Command: npx skills add https://github.com/Shtian/AuthentiClash --skill principle-exhaust-the-design-space-shtian

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 multiple concrete alternatives before implementation. ## Core Features & Use Cases - Prototype Comparison: Guides 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, feel-driven product decisions) and when it does not (mechanical implementations, bug fixes, constraint-dictated changes). - Use Case: When designing a new game score-entry interaction with no prior art in the codebase, build three distinct interaction prototypes, evaluate them side by side, and only then commit to one. ## Quick Start Ask the AI to apply the exhaust-the-design-space principle to explore alternatives for a novel UI interaction before implementing it.

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 UI design 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; 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 exploration 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 are the limitations of prototype-based design exploration?▼

Exploration costs time upfront, so it is wasteful for decisions with obvious answers or established patterns. It also requires genuinely distinct alternatives; minor variations of one idea provide no real comparison value.