C31-1st
Skill1 starsChanged 3 months agoMITView on GitHub
追本溯源的思考框架。当用户提到"第一性原理"、"本质"、"追本溯源"、"底层逻辑"、"为什么"、或需要从基本原理重新构建解决方案时触发。用于将复杂问题拆解至最基础的公理级事实,从底层真理出发重新推导,而非依赖类比或经验模仿。
In this repository56 other files it gives its agents.
- C31-adopt-projectSkill
- C31-brainstormSkill
- C31-coding-disciplineSkill
- C31-compound-refreshSkill
- C31-compoundSkill
- C31-context-engineeringSkill
- C31-curatorSkill
- c31-daily-intelSkill
- C31-debugSkill
- c31-devSkill
- C31-grillSkill
- C31-lfgSkill
- C31-planSkill
- C31-researchSkill
- C31-specSkill
- C31-stormSkill
- C31-strategySkill
- C31-workflow-bug-reproductionSkill
- C31-workSkill
- rl-workflowSkill
- C31-cvideoSkill
- c31-loopSkill
- c31-sxsSkill
- teachSkill
- video-content-analysisSkill
- agent-reachSkill
- kimiimSkill
- skillhub-preferenceSkill
- c31-communitySkill
- c31-growSkill
- c31-gutcheckSkill
- c31-marketSkill
- c31-mvpSkill
- c31-priceSkill
- c31-processSkill
- c31-sellSkill
- c31-validateSkill
- c31-valuesSkill
- growth-hackerSkill
- c31-improve-codebase-architectureSkill
- C31-multi-reviewSkill
- C31-review-adversarialSkill
- C31-review-architectureSkill
- C31-review-securitySkill
- C31-reviewSkill
- c31-wizardSkill
- external-privacy-guardSkill
- find-skillsSkill
- gsd-map-codebaseSkill
- gsd-new-projectSkill
- gsd-progressSkill
- gsd-quickSkill
- gsd-shipSkill
- humanize-aiSkill
- time-awarenessSkill
- worker-safetySkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 45
When executing First Principles thinking, strictly follow these three steps:
- Distinctive: line 65
If I remove the industry's default assumptions, what does the problem become?
- Distinctive: line 73
Ignoring constraints: Only decomposing without reconstructing — failing to build a viable solution from the ground up
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Multilingual Triggers
| Language | Trigger phrases |
| EN | C31-1st |
| ZH | 第一性原理, 追本溯源, 本质 |
| JA | 第一原理, 本質を探る |
Output language: Respond automatically in the user's conversation language.
First Principle Thinking
Trace back to the root, redefine — do not merely optimize.
Core Definition
First Principles Thinking is a method of breaking down complex things to the most fundamental physical or axiomatic facts, and then rebuilding solutions from those "ground truths" — rather than relying on analogy or imitating convention.
Analogical Thinking vs. First Principles
| Dimension | Analogical Thinking (conventional) | First Principles (ground-up innovation) |
| Starting point | Follow past experience, industry norms, or what others did | Strip away surface appearances and target the irreducible essential elements |
| Reasoning method | Inductive: others succeeded this way, so I'll do the same | Deductive: derive new solutions from fundamental laws and objective facts |
| End result | Incremental improvements and fine-tuning (optimizing what exists) | Innovative breakthroughs and reconstruction (redefining what exists) |
Classic Case: Elon Musk and SpaceX
Conventional thinking (analogical):
"Spacecraft have always been expensive — that's been true for decades. Buying a ready-made rocket is too costly, so lowering launch costs seems impossible."
First Principles:
"What are the core materials in a rocket? Aluminum, titanium, copper, carbon fiber. These raw materials are actually quite cheap on commodity markets — roughly 2% of the rocket's total price. So instead of buying finished products, we buy the raw materials and build it ourselves from scratch."
Result: Launch costs dropped to one-tenth or even one-hundredth of the original.
Practice Steps
When executing First Principles thinking, strictly follow these three steps:
Step 1: Identify and Define the Problem
- Clearly state the specific problem to solve
- Example: "Why is the product too expensive?" "Why does no one use this feature?"
Step 2: Decompose to Essential Facts
- Keep asking "why"
- Strip away all assumptions, conventions, and analogies
- Retain only undeniable physical laws, mathematical axioms, or core elements
- Key question: "If X were removed, would this thing still be itself?" If "no," X is essential. If "yes," X is an assumption.
Step 3: Rebuild from Fundamentals
- Abandon "what does everyone else do"
- Starting from the ground-level facts found in Step 2, derive a completely new solution upward
- The answer may look entirely different from existing approaches
Self-Check Questions (answer before each use)
- Am I relying on analogy / experience / convention, or on ground-level facts?
- If I remove the industry's default assumptions, what does the problem become?
- From a physics / math / logic perspective, what is the minimum necessary composition of this thing?
- Is my solution derived from "what everyone else does" or from "what this thing must be"?
Common Pitfalls
- Pseudo-first-principles: Decomposing only to "I think" or "experience tells me," not to "physics/mathematics proves"
- Over-decomposition: Going all the way to quantum mechanics when it has no bearing on the actual problem. Decomposition depth should match problem complexity
- Ignoring constraints: Only decomposing without reconstructing — failing to build a viable solution from the ground up
References
- Elon Musk: "I think it's important to reason from first principles rather than by analogy."
- Aristotle: "Each knowing about anything is based on first principles."
- Duan Yongping: "Walk the right path."
"Boil things down to the most fundamental truths and reason up from there." — Elon Musk
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

