Physics-based reasoning framework (Musk methodology) that deconstructs problems to irreducible fundamental truths rather than reasoning by analogy.
Ask a generic AI to challenge your architecture and it'll reason by analogy — comparing to what worked elsewhere, citing convention, anchoring to market prices as if they were physics. The result is a polished version of the status quo. You don't get someone asking whether the constraint is real or whether you're optimizing form instead of function. Inherited assumptions stay invisible because nobody decomposed the problem far enough to find them.
The skill runs a three-step framework: Deconstruct (break the problem into constituent parts and actual values, not market prices or received wisdom), Challenge (classify every element as a hard constraint from physics, a soft constraint from policy, or an unvalidated assumption — only the first category is truly immutable), then Reconstruct (build the optimal solution from the hard constraints alone, ignoring inherited form). The constraint table is the core artifact. Every time you call Challenge, you get a row: what the constraint is, what type it is, the evidence for that classification, and what happens if you remove it. Reconstruct only works from the hard column. Other skills call FirstPrinciples as a sub-step when they're stuck — RedTeam, Ideate, architects mid-analysis.
What you say to your DA, and what the FirstPrinciples skill actually does.
The thinking, frameworks, and architecture that distinguish this skill from a generic version of the same task.
Breaks a problem down to its fundamental truths and rebuilds the solution from there, instead of copying what already exists. Three steps: DECONSTRUCT (break it into constituent parts and real values), CHALLENGE (classify every element as hard constraint, soft constraint, or unvalidated assumption — only physics is truly immutable), and RECONSTRUCT (build the optimal solution from the fundamentals alone). Outputs a parts breakdown, a constraint table, and a reconstructed solution.
Most reasoning is reasoning by analogy: "how did we solve something similar," "what do others do," then copy it with small tweaks. That inherits everyone else's assumptions and treats policy and convention as if they were laws of physics. So you optimize the suitcase instead of inventing wheels, and accept costs and constraints that were never real. This skill forces the split between what's actually immutable and what's just inherited, then rebuilds from only the parts that can't change.
A reasoning methodology based on Elon Musk's physics-based thinking framework. It deconstructs problems to fundamental truths rather than reasoning by analogy.
Reasoning by Analogy (default, often wrong):
Reasoning from First Principles (this skill):
┌─────────────────────────────────────────────────────────┐
│ STEP 1: DECONSTRUCT │
│ "What is this really made of?" │
│ Break down to constituent parts and fundamental truths │
└─────────────────────────────────────────────────────────┘
↓
┌─────────────────────────────────────────────────────────┐
│ STEP 2: CHALLENGE │
│ "Is this a real constraint or an assumption?" │
│ Classify each element as hard/soft constraint │
└─────────────────────────────────────────────────────────┘
↓
┌─────────────────────────────────────────────────────────┐
│ STEP 3: RECONSTRUCT │
│ "Given only the truths, what's optimal?" │
│ Build new solution from fundamentals, ignoring form │
└─────────────────────────────────────────────────────────┘
When analyzing any system, classify constraints:
| Type | Definition | Example | Can Change? |
|---|---|---|---|
| Hard | Physics/reality | "Data can't travel faster than light" | No |
| Soft | Policy/choice | "We always use REST APIs" | Yes |
| Assumption | Unvalidated belief | "Users won't accept that UX" | Maybe false |
Rule: Only hard constraints are truly immutable. Soft constraints and assumptions should be challenged.
Other skills invoke FirstPrinciples like this:
→ Use FirstPrinciples/Challenge on all stated constraints → Classify each as hard/soft/assumption
→ Use FirstPrinciples/Deconstruct to break down the problem → Use FirstPrinciples/Reconstruct to rebuild from fundamentals
→ RedTeam uses FirstPrinciples/Challenge to attack assumptions → Pentester uses FirstPrinciples/Deconstruct on security model ```
Problem: "We need microservices because that's how modern apps are built"
First Principles Analysis:
Problem: "The firewall protects the internal network"
First Principles Analysis:
Problem: "Cloud hosting costs $10,000/month - that's just what it costs"
First Principles Analysis:
| Constraint | Type | Evidence | Challenge |
|---|---|---|---|
| [X] | Hard/Soft/Assumption | [Why] | [What if removed?] |
[One sentence: what assumption was limiting us?] ```
Attribution: Framework derived from Elon Musk's first principles methodology as documented by James Clear, Mayo Oshin, and public interviews.
Workflows/Challenge.md Workflows/Deconstruct.md Workflows/Reconstruct.md Say any of these to your DA and PAI activates the FirstPrinciples skill automatically:
Or invoke explicitly:
Skill("FirstPrinciples")The thinkers, books, frameworks, and research this skill is built on. The ideas belong to them — the integration belongs to PAI.
Install PAI on your machine — your DA gets the FirstPrinciples skill plus 44 others, all hooked into one Life OS.