skills.rest
jnyross
jnyrossCOMMUNITY
Explore all skills by this author →
GitHub

principle-exhaust-the-design-space

Builds competing prototypes to compare design alternatives before committing to an implementation.

Updated Sep 2, 2026
Search Tags:#prototyping#design principles#architecture decisions#design exploration#side-by-side comparison#ui interactions
One-click install
npx skills add https://github.com/jnyross/pstack-muse --skill principle-exhaust-the-design-space-jnyross
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: principle-exhaust-the-design-space
Source: https://github.com/jnyross/pstack-muse/tree/main/skills/principle-exhaust-the-design-space
Command: npx skills add https://github.com/jnyross/pstack-muse --skill principle-exhaust-the-design-space-jnyross

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 exploring multiple concrete alternatives before implementation. ## Core Features & Use Cases - Prototype Comparison: Build 2-3 competing prototypes or sketches and compare them side by side before committing. - Applicability Rules: Clear guidance on when the rule applies (novel UI interactions, architectural choices, feel-driven product decisions) and when it does not (mechanical implementations, bug fixes, single-approach constraints). - Use Case: You need to design a new drag-and-drop interaction with no prior art in the codebase. Use this Skill to 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 your novel UI interaction or architectural decision by building and comparing two or three competing prototypes.

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; 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 exploring design alternatives not worth it?▼

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 design prototypes should I build?▼

Build 2-3 competing prototypes. Fewer than two means no real comparison, and the goal is to compare distinct shapes side by side, not to exhaustively explore every possibility.

What is the design it twice principle?▼

Design it twice is another name for exhausting the design space: explore several concrete alternatives before implementation because building the wrong thing costs more than exploring three options upfront.

Related Skills

Explore More Software Engineering Skills→
adjohnadjohn
3

principle-exhaust-the-design-space

Builds and compares competing prototypes before committing to novel design decisions.

Community
Basic
thoughtbotthoughtbot
17

feature-dev

Orchestrate a multi-phase Rails development workflow with feature slicing, TDD, and automated review.

Official
Advanced
cursorcursor
6.6k

principle-exhaust-the-design-space

Builds competing prototypes to compare design alternatives before committing to an implementation.

Official
Basic
yersonargotevyersonargotev
1

principle-exhaust-the-design-space

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

Community
Basic