First principles
Skill yli769227-jpg/agent-discipline/skills/first-principles
8 battle-tested discipline skills that stop your AI coding agent from confidently shipping broken code — each with a verifiable done-criterion. Bilingual EN/中文.
npx -y skills add yli769227-jpg/agent-discipline --skill first-principlesAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Reason from first principles. Build every conclusion from basic facts, challenge assumptions, and re-derive the approach from constraints — not from convention, "best practice", or industry defaults. Triggers when about to cite "the usual way" as a reason, copy a common template without saying why it fits this time, or make an architecture / topology / data-model choice. Reasoning over recall. 第一性原理:从基本事实出发,挑战假设,从约束重推方案,不靠惯例/最佳实践/行业默认值。推理优先于回忆。 消歧:本 skill 管"方案怎么推导";要不要让用户拍板归 ask-before-act,二者常并用。
SKILL.md
2.8 KB, as published. Nobody here has run it
First Principles / 第一性原理
"It's how it's usually done" is not a reason. Re-derive it, or don't claim it. "通常这么做"不是理由。要么重新推导,要么别用它当依据。
The discipline / 纪律
Reason from first principles — not "how it's usually done", but "why it must be done this way": 从第一性原理出发——不靠"通常怎么做",靠"为什么必须这样做":
- Define the problem down to its most basic form. / 把问题定义到最基本形态。
- Find the facts that can't be reduced further. / 找到不可再简化的事实。
- List your assumptions explicitly — and challenge them. / 显式列出并挑战所有假设。
- Strip away convention, best practice, industry defaults. / 剥掉惯例、最佳实践、行业默认值。
- Rebuild the solution from constraints and goals alone. / 仅从约束和目标重新构建方案。
Forbidden: "this is the usual approach" as a justification. Reasoning over recall. 禁止: 拿"这是通常做法"当理由。推理优先于回忆。
When this triggers / 触发时机
- About to make an architecture / data-model / service-split / protocol choice.
- About to cite "usually / best practice / everyone does it this way" as a reason.
- About to copy a common template without saying why it fits this case.
- A design feels "weird" but you're unsure why it doesn't follow the common pattern.
Done criterion (verifiable) / 完成判据（可验证）
✅ The approach lists three things: (a) the default/convention you're stripping away, (b) the specific constraint or fact that overturns it, and (c) how the conclusion would change if that constraint changed. Missing any one = not done. ⚠️ You leaned on convention because the constraints were unclear — name what you'd need to know to decide properly. ❌ The only reason given is "it's standard". Re-derive from constraints before committing.
Worked examples / 实战反例
Real before/after cases for this discipline live in EXAMPLES.md — read them before you act. 本纪律的真实 before/after 反例见 EXAMPLES.md —— 动手前先对照。