Individual skill
FirstPrinciples
Physics-based reasoning framework (Musk methodology) that deconstructs a problem to irreducible fundamental truths, classifies every element as hard constraint, soft constraint, or assumption, then reconstructs the optimal solution from fundamentals alone. USE WHEN first principles, fundamental truths, challenge assumptions, real constraint, rebuild from scratch, start over, physics first, question everything, reasoning by analogy. NOT FOR structural feedback loops (use SystemsThinking).
LifeOS/install/skills/FirstPrinciples/SKILL.md
Source commit b7efec97d8c3885feee285bee468c35602fb0606
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Local scripts
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.
Repository context
- Repository stars (not skill ratings)
- 19,779
- Repository last updated
- Nov 5, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai Repository topic
- augmentation Repository topic
- productivity Repository topic
- humans Repository topic
- ai-harness Repository topic
- intent-engineering Repository topic
- personal-ai Repository topic
- coding Repository topic
- lifeos Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Intents/Challenge.mdruns · 5,926 bytesIntents/Deconstruct.mdruns · 2,931 bytesIntents/Reconstruct.mdruns · 4,760 bytesSKILL.mdcore · 8,562 bytes
Read excerpt
# FirstPrinciples
**Contents:** Ideal State · Intent Routing · Constraint Classification · The Core Distinction · The Load-Bearing Rules · Output Format · Data & Config · Gotchas · Examples
Breaks a problem down to its fundamental truths and rebuilds the solution from there, instead of copying what already exists. Three steps, each an intent: 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. It is analysis, not implementation: a request to fix something is done directly, not through this skill. Other skills call it when inherited assumptions may be limiting the solution space: architecture work asking "constraint or convention?", RedTeam and pentests attacking assumed boundaries, RedTeam building counter-proposals with Reconstruct, and engineering escaping a local maximum.
## Ideal State
- What the analysis calls fundamental is only physics, math, verified fact or a truly immutable requirement; every market price, best practice and policy is shown to be convention and taken apart.
- The irreducible function of the subject is stated as an outcome, not a mechanism ("pick the right model and effort for a piece of work", not "a router"), and every component under discussion is marked as serving that function or not. Costing from fundamentals appears only when cost is part of the question.
- Output length matches the request: an inline, brief or terse pass returns the irreducible job, the classification with its evidence, and the key insight in a few lines, without empty template sections; the full templates are for full runs.
- A full run ends with a solution rebuilt from the hard constraints and compared against the current approach, plus the one assumption that was limiting it.
## Intent Routing