What problem does it solve? Hard or ambiguous problems often get attacked with mechanism before the problem is precisely stated, producing over-parameterized code that solves the wrong problem. This Skill forces the framing questions that make the real problem collapse before any implementation starts. ## Core Features & Use Cases - Three-stage method: Frame (concrete scenario, kill the naive approach with numbers, define desired behavior, borrow structure from solved problems), Build (toy version, minimal working version, one delta at a time), and Stress (state limits, measure what distinguishes, verify against unfitted cases). - Anti-pattern detection: Flags mechanism-before-motivation, unlabeled simplifications, vague failure claims, and complexity with no chain back to a simple working design. - Compressed checklist: A scannable Frame/Build/Stress checklist for design reviews and architecture decisions. - Use Case: Before committing to a new caching architecture, use this Skill to state the concrete scenario, quantify why the naive approach fails, and define the metric that separates a sound design from a memorized one. ## Quick Start Use the first-principles skill to help me frame and stress-test my proposed design for the dashboard caching layer before I write any code.
