@elasticdotventures/first-principles
BFirst-principles reasoning: refuse inherited assumptions; derive from base truths.
Install
agr install @elasticdotventures/first-principles --target claudeWrites 1 file into .claude/skills/, pinned to git-d384223b.
- .claude/skills/first-principles/SKILL.md
Document
name: first-principles type: skill hint: Decompose to atoms; rebuild from base truths; ignore analogy and precedent version: 1.0.0 tags: [transferable, first-principles, reasoning, decompose, atoms, assumptions, base-truth] tier: ch0nky complexity: 5 description: |- First-principles reasoning: refuse inherited assumptions; derive from base truths.
What
First-principles reasoning means refusing inherited assumptions and deriving conclusions from base truths. Step 1: state what you believe to be true about the problem. Step 2: for each belief, ask "is this a fact, or did I inherit it from convention?" Step 3: discard the inherited beliefs and rebuild from what remains.
Elon Musk's classic example: "batteries are expensive" → why? → materials → materials are cheap → rethink assembly. In software: "we need a database" → why? → persistent state → what's the simplest persistent state? The key test: "would this design make sense to someone who had never seen this domain before?"
When to Use
Apply first-principles thinking to high-stakes decisions where inherited assumptions may be hiding better solutions. It is expensive — do not use it for every micro-choice. Use it when analogy reasoning ("we do it this way because that's how X does it") would lead to a suboptimal outcome.
How
- State every belief you hold about the problem.
- Challenge each belief — is it a fact or inherited convention?
- Discard inherited beliefs. Rebuild from undeniable base truths.
- Verify: would this design make sense to a domain newcomer?
- Beware the anti-pattern of defaulting to analogy reasoning instead.
Trustgrade B
- passBody integrity
Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.
- passType matchnot applicable to this artifact type
Whether the artifact is really the kind of thing its metadata claims it is.
- passFreshness
How long since the source repository was last pushed to.
- passPrompt injection
Scans the artifact's own text for instructions aimed at your agent rather than at you.
- warnLicenseno SPDX license detected
Whether the source repository declares an SPDX license permissive enough to redistribute.
How the grade is calculated
Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:
- Aevery check passed
- Bone warning
- Ctwo warnings
- Dprompt injection or body integrity failed, or three warnings
- Fone of those failed, and something else is wrong
These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.
Versions
git-d384223bf9982026-07-31