Skip to content
alyn
tjboudreaux

Thinking First Principles skill

When a constraint is treated as fixed, separate physics from convention, keep only independently supported primitives, and rebuild the simplest solution that satisfies real constraints.

$npx skills add tjboudreaux/cc-thinking-skills --skill thinking-first-principles
View this skill on GitHubtjboudreaux/cc-thinking-skills/skills/thinking-first-principles/SKILL.md
Pack stars
1,724
Pack installs
20k
Alyn Score
53/99
Updated
3 months ago
License
MIT
– views – installs via Alyn

Install Thinking First Principles

Pick your agent. Every command is ready to paste.

$npx skills add tjboudreaux/cc-thinking-skills --skill thinking-first-principles

The open skills CLI detects your agents (Claude Code, Cursor, Codex and 70+ more) and installs to the right folder. Add -g to install globally.

01

Install it

Run the command above, or upload the folder in Claude.

02

Ask naturally

Describe the task. Your agent loads thinking-first-principles when the request matches its description.

03

Name it if needed

If it does not trigger, say “use the thinking-first-principles skill”. In Codex, type $thinking-first-principles.

The skill itself

SKILL.md

FolderGitHub

First Principles

Strip assumed constraints to independently supported primitives, then rebuild. Escape analogy when convention fails or looks artificially expensive.

When to Use

  • A constraint is treated as fixed ("too expensive," "impossible," "always done this way") without independent support.
  • Convention or analogy has failed, stalled, or only yields weak incremental variants.
  • Greenfield design where industry defaults may smuggle false requirements.
  • Cost or feasibility claims rest on pricing, precedent, or authority rather than physics, math, or measured need.

When NOT to Use

  • The constraint is verified physics, hard regulation, or measured capacity → accept it and optimize within it.
  • A proven standard library, protocol, or known-good pattern already fits → use it; do not re-derive.
  • Time-critical incidents → act on the most likely cause first; reserve first-principles rebuild for post-incident redesign.
  • Incremental polish of a working system with no false-constraint signal → skip.

Procedure

  1. State the problem and claimed constraints. List every limit treated as fixed (cost, scale, stack, process, "must use X").
  2. Classify each constraint. Tag as physics/math, regulation/contract, measured fact, or convention/analogy/authority. Keep only the first three as binding unless evidence upgrades a convention.
  3. Decompose to primitives. Required inputs, conservation/complexity bounds, true non-negotiables. Demand independent support (measurement, derivation, primary requirement)—not vendor pricing or competitor precedent.
  4. Discard unsupported assumptions. For each convention tag, state a falsifier. Drop or renegotiate anything lacking support.
  5. Rebuild from remaining primitives only. Simplest solution that satisfies binding constraints and ignores artificial ones. Prefer commodity inputs and fewer moving parts over analogy.
  6. Validate and stop. Check against real physics, contracts, and measured needs. Define the cheapest kill test. Stop when a coherent rebuild plus discriminating validation exists, or when only verified hard constraints remain.

Output

Emit a first-principles rebuild:

  • claimed_constraints: list with classification tags
  • primitives: independently supported truths only
  • discarded_assumptions: conventions dropped and why
  • rebuild: solution derived only from primitives
  • binding_residuals: real limits that remain
  • kill_test: cheapest check that would falsify the rebuild

Verification

  • Independence check: every primitive must cite measurement, derivation, or primary requirement—not precedent alone.
  • No smuggled analogy: if the rebuild still depends on "how others do it" without a primitive, strip it.
  • Constraint honesty: verified physics/regulation must remain; do not wish them away.
  • Over-application guard: if a standard solution is already optimal under verified constraints, do not rebuild for novelty.
  • Stop: one decompose → classify → rebuild → kill-test pass; do not recurse without new evidence.

Tips for Thinking First Principles

  • • Start a fresh session after installing so your agent picks up the new skill.
  • • It is part of a pack with 28 skills. Install only the ones you need with --skill to keep triggers precise.
  • • If two skills overlap, mention the one you want by name.

Questions about Thinking First Principles

What does the Thinking First Principles skill do?

When a constraint is treated as fixed, separate physics from convention, keep only independently supported primitives, and rebuild the simplest solution that satisfies real constraints.

How do I install Thinking First Principles?

Run "npx skills add tjboudreaux/cc-thinking-skills --skill thinking-first-principles" in your project. The skills CLI installs it for Claude Code, Cursor, Codex and 70+ other agents. In Claude on the web, upload the skill folder as a ZIP under Customize > Skills.

Does Thinking First Principles work in Cursor and Codex?

Yes. Thinking First Principles uses the open SKILL.md format, so it works in Claude Code, Claude, Cursor, OpenAI Codex, Gemini CLI, GitHub Copilot and other agents that support agent skills.

Is Thinking First Principles free?

Thinking First Principles is open source on GitHub under the MIT license. It is free to install; check the license before commercial use.

Who made Thinking First Principles?

Thinking First Principles is published by tjboudreaux in the tjboudreaux/cc-thinking-skills repository, together with 27 other skills.

Similar skills. From other creators.