← ClaudeAtlas

first-principles-solvelisted

Solve novel technical or academic problems from first principles — debug, derive, or design from scratch. Use when user says "solve from first principles", "debug from scratch", "derive X", "design X from fundamentals", "stuck on X problem", "reason from first principles".
xshubhamg/voidskills · ★ 0 · DevOps & Infrastructure · score 60
Install: claude install-skill xshubhamg/voidskills
# First-Principles Solve Solve from bedrock, not analogy. No memorized templates. Build custom solution from truths → rebuild → validate. For technical/coding + academic problems. ## The Canvas (follow in order, no skipping) ### 1. Restate (1 sentence + constraints) - Restate goal: "We need [output] given [input] with [limits]." - Split constraints: Real (time/memory/spec/physics) vs Assumed (habit/library/pattern). If user pastes code, name observable symptom first. - Exit if goal vague: ask "What does success look like in one testable sentence?" ### 2. Decompose to Truths - Break into base parts (inputs, state, transforms, invariants). See `references/canvas.md`. - For each shaky claim make mini-table: Claim | True or Assumed? | Test. - Go 2 Whys deep: symptom → mechanism → root cause ("we do X needlessly / miss Y"). ### 3. Root Cause (pivot, 1-2 sentences) - Format: "Root cause is: ..." - Must be falsifiable. If you have 2 causes, pick the one that explains most pain. ### 4. Rebuild (2-3 candidates from truths) - Generate from truths, ignoring conventional approach: "Given truths, what could remember/skip/reorder?" - Compare minimal table: Candidate | Truth it uses | Cost | When it fails. - Pick minimal that kills root cause. State invariant that must hold. ### 5. Validate (required, see `references/validation.md`) - 1 minimal test / edge case + complexity or termination argument. - For code: before→after snippet + "verify by [log/test/profile]". - For academic: wal