first-principles
Skill0 starsChanged 2 months agoMITView on GitHub
Triggers: 第一性原理 / 别打补丁了推倒重来 / 回到本质重新想 / 这个方案一直在缝缝补补. Strip the problem back to verified facts vs unverified assumptions vs real goals vs constraints, then re-derive a fresh path from scratch instead of patching.
33 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- kaisco37/first-principlestheir own version, first seen Nov 15, 2026
- swap-cameroon/kuro-antigravity-configtheir own version, first seen Nov 15, 2026
- dvy1987/agent-loomtheir own version, first seen Nov 15, 2026
- m1nga/first-principlestheir own version, first seen Nov 8, 2026
- waltyou/skillstheir own version, first seen Nov 8, 2026
- shetengteng/skillix-hubtheir own version, first seen Nov 8, 2026
Used with
Projects with it also use second-order-thinking, inversion and 3 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
itzcullSkillsecond-order-thinking
Use second-order thinking to examine consequences beyond immediate effects. Use when evaluating decisions across time horizons, asking what happens next, or avoiding short-sighted optimization.
Also in 3 projects that use this
itzcullSkillinversion
Use inversion to solve problems by reasoning backward from failure, bad outcomes, or the opposite of success. Use when identifying risks, running premortems, or escaping overly idealized thinking.
Also in 3 projects that use this
Ingramradical235Skillpre-mortem
Pre-mortem analysis, scenario planning, future state narratives, and contingency frameworks. Use before finalizing any Strategy Kernel, when planning major initiatives, or when preparing Plan B triggers.
Also in 3 projects that use this
GoogleSkilltdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Also in 3 projects that use this
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 3 projects that use this
Other versions33 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- mingxinbi112-source/OBI-xiao-skill★ 039% same
Wrote their own version · 32
- agentcrew-academy/harness-starter-kit★ 42same name
- reshadat/first-principles-destructor★ 24same name
- kirillgreen/skills★ 23same name
- eliasstravik/skills★ 22same name
- ironyjk/strategy-frameworks★ 14same name
- deciqAI/knowledge-skills★ 13same name
- jackjin1997/ClawForge★ 12same name
- docxology/codomyrmex★ 11same name
- ccomkhj/skills★ 10same name
- MasihMoafi/skills★ 8same name
22 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- cross-domain-borrowSkill
- daodejing-overviewSkill
- expert-panelSkill
- fact-check-claimSkill
- family-experiment-trackingSkill
- ian-xiaohei-illustrationsSkill
- jingang-dialogueSkill
- life-designerSkill
- macos-app-installSkill
- meeting-action-itemsSkill
- min-experiment-designSkill
- reverse-deconstructSkill
- skill-authoringSkill
- socratic-interviewSkill
- steelman-decisionSkill
- talent-diggerSkill
- third-party-handoverSkill
- two-layer-explainSkill
- weekly-review-planningSkill
The file
Files
第一性原理 · 停止打补丁,回到地基重建
一句话:当方案上补丁摞补丁,用第一性原理把问题拆回四样东西——已确认的基本事实、没验证过的假设、真正想实现的目标、现实的资源约束——暂时放下行业惯例,从这四样重新推导一条新路。
什么时候触发
- 用户说"第一性原理""推倒重来""别打补丁了"
- 同一个问题反复修不好、越修越乱
- 组织流程、产品架构、复杂系统的重构前思考
你的执行规则
- 把问题拆成四层,逐层列清楚:
- 已经确认、无法绕开的基本事实;
- 习惯性接受、却没有验证过的假设;
- 真正想实现的目标;
- 现实中的资源与约束。
- 暂时放下行业惯例和现成方案,只从基本事实+目标+约束出发,重新推导可行路径。
- 最后输出四件套:
- 原方案中只在修补表面的部分(点名哪些补丁可以扔);
- 从基本事实重新推导出的新路径;
- 这条路径成立的前提;
- 验证它的第一步。
- 注意师兄的规矩精神:推倒重来 ≠ 推翻用户验证过的东西。哪些是"用户验证过的有效经验"要先单独标出来保护起来,重推的是流程和架构,不是推翻已被现实验证的事实。
可复制的完整提示词
我想解决的问题是:【填写你的问题】。
请用第一性原理把它拆回最底层,区分:
1. 已经确认、无法绕开的基本事实;
2. 习惯性接受、却没有验证过的假设;
3. 真正想实现的目标;
4. 现实中的资源与约束。
暂时放下行业惯例和现成方案,只从基本事实、目标和约束出发,重新推导可行路径。
最后请输出:
1. 原方案中只在修补表面的部分;
2. 从基本事实重新推导出的新路径;
3. 这条路径成立的前提;
4. 验证它的第一步。本机适配场景举例
- 部署流程改造:如果 staging→生产链路反复出问题,别再加检查项补丁,用这个重推导一遍发布管线。
- 九宫引擎类算法重构:算错了先分清"公式本身如此(事实)"还是"我实现错了(假设)",再动手。
关联技能
行业内部推不动时换 hengzong-research 的横向轴找参照;推出新路后用 min-experiment-design 验证。
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.

