← pstackCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to pstack
Snapshot Sep 30, 2026 · 23:14 UTC · version 0.2.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "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.",
"included_files": [],
"name": "principle-exhaust-the-design-space",
"skill_md_contents": "---\nname: principle-exhaust-the-design-space\ndescription: \"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.\"\ndisable-model-invocation: true\n---\n\n# Exhaust the Design Space\n\nWhen 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.\n\n**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.\n\n**When it applies:**\n- Novel UI interactions (no prior art in the codebase)\n- Architectural choices with multiple viable approaches\n- Product design decisions where user experience depends on feel, not logic\n\n**When it doesn't:**\n- Mechanical implementation where the pattern is established\n- Bug fixes or refactors with a clear target state\n- Changes where constraints dictate a single viable approach\n"
}SHA-256 of public snapshot: 63a6ef24430384694df803118b21f793fba347782084a968142913ab1107e192