think-from-first-principles
Engage this skill fully on any request involving: - Design, architecture, invention, or optimization - Cost, efficiency, scalability, or “why is this…
Skill by pratikpakhale
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/pratikpakhale-think-from-first-principles
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: design
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/think-from-first-principles
What's inside
- Skill name
think-from-first-principles- Description
- Engage this skill fully on any request involving: - Design, architecture, invention, or optimization - Cost, efficiency, scalability, or “why is this expensive/slow?” - Challenging industry norms or “best practices” - Questions of the form “How should we…?”, “What’s the best way…?”, “Is X possible?
- License
- MIT
- Metadata
- author: pratikpakhale · version: 1.0.0
- Instructions
- 108 lines in SKILL.md · view on GitHub
Files (1)
- SKILL.md
SKILL.md (first lines)
# Think from First Principles ## Skill Overview This skill forces rigorous first-principles reasoning on every problem, design decision, optimization, architecture, cost analysis, or invention task. It is the antidote to “that’s how it’s always been done,” industry consensus, historical precedent, and analogical thinking. You must treat every accepted constraint, cost, process, or “best practice” as a hypothesis to be stress-tested against fundamental truths (physics, mathematics, logic, raw material realities, causality) rather than social or historical convention. ## Philosophical & Historical Foundation Aristotle defined a first principle (ἀρχή / archē) as “the first basis from which a thing is known” — the irreducible starting point of knowledge that cannot itself be deduced from anything prior. In physics and science this became “ab initio” reasoning: start from established laws and axioms, never from empirical models or fitted parameters that hide assumptions. Elon Musk revived and operationalized this for engineering and entrepreneurship as a “physics way of looking at the world”: > “Boil things down to the most fundamental truths and say, ‘OK, what are we sure is true, or as sure as possible is true?’ And then reason up from there.” > — Elon Musk > “First principles is kind of a physics way of looking at the world… you boil things down to the most fundamental truths… and then reason up from there. That takes a lot more mental energy.” Most people reason by analogy: “This is how it has always been done” or “slight iterations on what others are doing.” First-principles thinking rejects that shortcut when novelty or breakthrough performance is required. ## Canonical Real-World Examples (Internalize These) **SpaceX rockets** Industry price ≈ $65 million. First-principles decomposition: What is a rocket made of? Aerospace-grade aluminum alloys, titanium, copper, carbon fiber. Commodity market value of those materials ≈ 2 % of the finished rocket price. Conclusion: 98 % of the cost is process inefficiency, overhead, and legacy manufacturing. Therefore build vertically, reuse stages, and redesign around the material floor. **Tesla / battery packs (2012 analysis)** Industry consensus: “Batteries cost ~$600/kWh and always will.” First-principles: Material constituents = cobalt, nickel, aluminum, carbon, polymers, steel can. London Metal Exchange spot prices summed to ≈ $80/kWh. Conclusion: The gap is pure manufacturing and process inefficiency, not a law of physics. Clever combination of the same atoms can collapse the cost. These examples reveal the recurring pattern: the “idiot index” (finished cost ÷ raw-material cost). High idiot index = high opportunity. ## Mandatory Reasoning Protocol You must execute these steps explicitly (show your work) for every non-trivial task: ### 1. Surface and List All Assumptions Write down every belief, constraint, “requirement,” historical price, process step, or conventional wisdom currently accepted about the problem. Ask of each: “Is this a law of nature or merely an inherited habit?” ### 2. Reduce to Fundamental Truths / Axioms Strip the problem until only irreducible realities remain: - Laws of physics (conservation of energy/mass, thermodynamics, Maxwell’s equations, material strength limits, etc.) - Mathematical identities and logical necessities - Commodity / raw-material prices and physical properties - Causal chains that cannot be shortened further - Empirical measurements that have been repeatedly verified and cannot be reduced Discard everything else as provisional. ### 3. Compute the Theoretical Floor (Magic-Wand / Raw-Material Limit) Ask: “If I could magically reassemble the fundamental constituents with perfect efficiency and zero overhead, what is the absolute lower bound?” This is the “magic-wand number.” Everything above it is process waste or design inefficiency. ### 4. Rebuild from the Ground Up Construct the solution using only the axioms from Step 2. Prefer the simplest architecture that satisfies the physics. Vertical integration, deletion of steps, radical simplification, and novel geometries are default tools when the idiot index is high. ### 5. Stress-Test & Iterate - Attempt to disprove your own conclusion (Musk’s scientific-method step). - Scale variables to extremes (“thinking in the limit”) to expose hidden constraints. - Assign rough probabilities of truth to each axiom. - If a conventional tool or library survives the test, use it — but only after proving it is the optimal expression of the fundamentals, never as a default. ## Operational Heuristics Drawn from Musk’s Practice - **Idiot Index** = finished cost / raw-material cost. Target dramatic reductions. - **Make requirements less dumb** before optimizing them. - **Delete** before simplifying; simplify before accelerating; accelerate before automating (the Algorithm order). - Prefer physics and first-order effects over second-order social or historical arguments. - “All designs are wrong; it’s just a matter of how wrong.” Continuously question. ## Behavioral Rules for This Skill - Default mode for any invention, cost reduction, architecture, system design, process redesign, or “how should we…?” question is first-principles. - For routine, low-stakes tasks you may reason by analogy after a quick first-principles check confirms no breakthrough opportunity exists. - Never accept “nobody has done it” or “it’s always been this expensive” as evidence. - When code or tools are involved: derive the minimal correct approach from fundamentals first; only then reach for packages. - Explicitly flag any remaining assumptions or places where better fundamental data would change the answer. - Mental energy is high; do not apply full rigor to trivial queries, but always be ready to escalate. ## Preferred Output Structure (when useful) **Assumptions challenged** - … **Fundamental truths / axioms identified** - … **Theoretical floor / magic-wand number** - … **Rebuilt solution from first principles** - … **Why this is superior (or identical) to conventional approaches** - … **Remaining uncertainties or tests needed** - … You may still deliver the final answer in clean, natural prose, but the internal reasoning trace must follow the protocol above.
From pratikpakhale/pakhale, MIT.
More from pratikpakhale/pakhale
- 0.570score
consistency-check
pratikpakhale
Audit a set of changes (a branch, PR, or working tree) for consistency with the codebase's established conventions across many dimensions — code idioms…
SkillAFreshness: AClaude Code +9 - 0.570score
deslop
pratikpakhale
Clean up generated code changes — strip slop (dead code, one-use abstractions, redundant guards, comment noise, unnecessary effects), fix what the change…
SkillAFreshness: AClaude Code +9 - 0.570score
stackup
pratikpakhale
Stack up a new or under-tooled side project with the current best tooling — package manager, type checker, linter, formatter, dead-code detection, tests, git…
SkillAFreshness: AClaude Code +9 - 0.565score
sync-from-live
pratikpakhale
Detect drift between the live coding-agent state on this machine (~/.claude, ~/.agents, ~/.claude.json, ~/.config/opencode) and this repo's declarations, then…
SkillAFreshness: AClaude Code +9 - 0.550score
architecture
pratikpakhale
Visualize the codebase architecture provided a target.
SkillAFreshness: AClaude Code +9
Signals
- Stars
- 0
- Forks
- 0
- Open issues
- 0
- Last commit (this folder)
- Aug 12, 2026 (2 months ago)
- Last release
- Oct 9, 2026 (20 days ago)
From GitHub (fetched Oct 24, 2026).
Details
- Version
- 1.0.0
- License
- MIT
- Repository
- github.com/pratikpakhale/pakhale
- Website
- pakhale.com
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from pratikpakhale
- 0.570score
consistency-check
pratikpakhale
Audit a set of changes (a branch, PR, or working tree) for consistency with the codebase's established conventions across many dimensions — code idioms…
SkillAFreshness: AClaude Code +9 - 0.570score
deslop
pratikpakhale
Clean up generated code changes — strip slop (dead code, one-use abstractions, redundant guards, comment noise, unnecessary effects), fix what the change…
SkillAFreshness: AClaude Code +9 - 0.570score
stackup
pratikpakhale
Stack up a new or under-tooled side project with the current best tooling — package manager, type checker, linter, formatter, dead-code detection, tests, git…
SkillAFreshness: AClaude Code +9 - 0.565score
sync-from-live
pratikpakhale
Detect drift between the live coding-agent state on this machine (~/.claude, ~/.agents, ~/.claude.json, ~/.config/opencode) and this repo's declarations, then…
SkillAFreshness: AClaude Code +9 - 0.550score
architecture
pratikpakhale
Visualize the codebase architecture provided a target.
SkillAFreshness: AClaude Code +9
Cite this page
think-from-first-principles skill. Agent Mart. https://agentmart.dev/skills/pratikpakhale-think-from-first-principles (last updated 2026-10-24)