principle-exhaust-the-design-space

Featured

Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3 competing prototypes and compare side by side before committing.

Code & Development 333 stars 40 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%
84
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
44
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Exhaust the Design Space When a novel interaction or architectural decision has no established precedent, explore several concrete alternatives before implementation. Building the wrong thing costs more than exploring three options. **The rule.** When the right answer is not obvious, build 2-3 competing prototypes or sketches. Compare them side by side. Only then commit. Design it twice is this rule by another name. A second flavor of the first shape does not count. **When it applies:** - Novel UI interactions (no prior art in the codebase) - Architectural choices with multiple viable approaches - Product design decisions where user experience depends on feel, not logic **When it doesn't:** - Mechanical implementation where the pattern is established - Bug fixes or refactors with a clear target state - Changes where constraints dictate a single viable approach

Details

Author
michael-denyer
Repository
michael-denyer/pstack-claude
Created
3 months ago
Last Updated
2 days ago
Language
TypeScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category