First Principles Cracker

Strip problems down to their fundamental truths and rebuild solutions from the ground up using first-principles thinking.

Overview

First Principles Cracker helps users break down complex problems to their fundamental truths — the irreducible facts that cannot be deduced further — and then reconstruct solutions from those building blocks. Inspired by Aristotle and popularized by thinkers like Elon Musk and Charlie Munger, this skill teaches users how to escape analogy-based thinking and build truly novel solutions.

This skill does not provide answers. It provides a disciplined thinking process for arriving at your own answers.

When to Use

Use this skill when the user asks to:

• Think from first principles
• Break down a problem to its fundamentals
• Find a novel solution instead of copying what others do
• Deconstruct an assumption or belief
• Rebuild an approach from scratch
• Escape analogy-based thinking

Trigger phrases: "First principles", "Break this down to basics", "What are the fundamentals here?", "Think from scratch", "Deconstruct this problem", "Why does it have to be this way?", "Strip away assumptions"

Workflow

Step 1 — Identify the Problem or Goal

Clarify what the user is trying to solve, decide, or understand:

• What specific outcome are you trying to achieve?
• What is the current approach or status quo?
• What makes this problem feel stuck or unsolvable?
• What assumptions are you already making about the solution?

Step 2 — Surface All Assumptions

List every assumption the user (and society/industry) is making about the problem:

• What does "everyone know" about this domain?
• What constraints are assumed to be fixed?
• What analogies are people using to reason about this? (e.g., "It's like X, so we do Y")
• What historical or conventional wisdom is being applied?
• What emotional or identity-based attachments exist to the current approach?

Flag especially:

• Analogy traps: Reasoning by comparison to what already exists
• Authority traps: Accepting something because experts say so
• Sunk-cost traps: Continuing because of past investment
• Norm traps: Doing it because "that's how it's done"

Step 3 — Deconstruct to Fundamental Truths

For each assumption, ask: "Is this true, or is it just accepted?"

Break the problem down to its physics, economics, human needs, or irreducible facts:

• What are the laws of nature that constrain this?
• What are the raw material costs or time requirements?
• What are the human needs or psychological truths involved?
• What constraints are real (cannot be changed) vs. assumed (can be challenged)?

Use the 5-Why Drill if needed: Ask "why?" up to 5 times until you hit a fundamental truth.

Step 4 — Rebuild from Fundamentals

With the fundamental truths identified, reconstruct a solution:

• Given only these truths, what is possible?
• What combinations of fundamentals have not been tried?
• What would the ideal solution look like if built from scratch?
• How does this new solution compare to the status quo approach?

Generate 2–3 distinct rebuild paths. Each should:

• Start from different fundamental truths or priorities
• Be describable in plain language
• Include a rough feasibility assessment

Step 5 — Stress-Test the Rebuild

For each rebuilt solution, challenge it:

• What assumptions did you introduce in the rebuild?
• What would falsify this solution?
• What is the cheapest/fastest way to test if this works?
• What are the second-order consequences?
• What expertise or resources would be needed?
• What is the simplest version you could try in 48 hours?

Step 6 — Synthesize and Act

Help the user choose a direction:

• Which rebuild aligns best with your goals and constraints?
• What is the smallest first step you can take to test it?
• What would make you abandon this path? (pre-mortem)
• What one assumption, if proven wrong, would change everything?

End with a clear action item and a checkpoint for revisiting the first-principles analysis.

Safety & Compliance

• This skill does not guarantee that first-principles thinking will produce a better solution
• Rebuilding from fundamentals can be time-consuming and risky — the skill flags when iterative improvement may be more practical
• Does not provide financial, legal, or medical advice
• Encourages testing and validation rather than theoretical confidence
• Acknowledges that some domains (regulated industries, safety-critical systems) have constraints that should not be casually challenged

Acceptance Criteria

1. User presents a problem; the skill surfaces at least 5 assumptions
2. At least 3 assumptions are challenged and traced to fundamental truths
3. At least 2 distinct rebuild paths are generated from fundamentals
4. Each rebuild path is stress-tested for feasibility and hidden assumptions
5. Output includes a concrete first step for testing the chosen direction
6. No analogy-based solutions are accepted without deconstruction
7. The distinction between real and assumed constraints is made explicit

Examples

Example 1: Reducing Living Costs

User says: "I need to reduce my living expenses but everything feels fixed."

Skill guides: Surface assumptions (rent/mortgage is fixed, car is necessary, food costs are what they are). Deconstruct: What is the fundamental need? Shelter, mobility, nutrition. Rebuild paths: (1) Co-living or house-hacking to restructure shelter cost; (2) Remote work + no car to eliminate vehicle expense; (3) Bulk cooking + local sourcing to cut food costs by design. Stress-test each for feasibility in user's city and lifestyle.

Example 2: Starting a Business

User says: "I want to start a business but I need funding, a team, and an office first."

Skill guides: Surface analogy trap (businesses look like established companies). Deconstruct: What is a business at its core? Creating value someone will pay for. What is truly needed? A paying customer. Rebuild: Start with a single customer, no office, no team. Validate demand before scaling. Compare to conventional startup path.

Example 3: Learning a New Skill

User says: "I want to learn programming but it takes 4 years of college."

Skill guides: Surface assumptions (degree required, 4 years needed, college is the only path). Deconstruct: What does "learn programming" mean? Write code that solves problems. What are the fundamentals? Syntax, logic, debugging, building projects. Rebuild: 3-month project-based path using free resources, building portfolio instead of taking courses.