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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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
The line at the top of this page pins the label git:20260827.04830a9, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_tvphoc3va3p63meu
GET https://markdownregistry.com/api/v1/resolve?ref=painhardcore/pstack/principle-exhaust-the-design-space
GET https://markdownregistry.com/api/v1/blob/67e7e29ab4f484bfddcac55ece4d70f6efc25ccbf91de7de31fcec385f9f059e
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
painhardcore/pstack · .opencode/skills/architect/SKILL.md · Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use…
painhardcore/pstack · .opencode/skills/arena/SKILL.md · Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for…
painhardcore/pstack · .opencode/skills/blast-radius/SKILL.md · Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe…
painhardcore/pstack · .opencode/skills/create-verification-skill/SKILL.md · Generate a project-local verification skill that drives your app the way a user does — any language, framework, or…
painhardcore/pstack · .opencode/skills/figure-it-out/SKILL.md · Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a…
painhardcore/pstack · .opencode/skills/how/SKILL.md · Explain how a subsystem works, trace a runtime flow, or determine where code and ownership belong before making a…
painhardcore/pstack · .opencode/skills/interrogate/SKILL.md · Use for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find…
painhardcore/pstack · .opencode/skills/principle-boundary-discipline/SKILL.md · Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI…
cursor/plugins · pstack/skills/principle-exhaust-the-design-space/SKILL.md · Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3…
cursor/plugins · harness/pstack/claude-code/skills/principle-exhaust-the-design-space/SKILL.md · Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3…
michael-denyer/pstack-claude · plugins/pstack/skills/principle-exhaust-the-design-space/SKILL.md · Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3…
backnotprop/pstack · skills/principle-exhaust-the-design-space/SKILL.md · Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3…
j-star-films-studios/vibecode-protocol-suite · assets/.agent/skills/engineering-principles/exhaust-the-design-space/SKILL.md · Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3…
creedants/pstack-t3 · skills/principle-exhaust-the-design-space/SKILL.md · Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3…
arjitj2/open-pstack · plugins/pstack/skills/principle-exhaust-the-design-space/SKILL.md · Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3…
shiwenbin1617/pstack · skills/principle-exhaust-the-design-space/SKILL.md · Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3…