agentleFS
q2522879285-sourceq2522879285-source/red-monkey-reasoning-kit/skills/first-principles-rebuild/SKILL.md

first-principles-rebuild

Skill2 starsChanged 2 months agoMITView on GitHub

Rebuild a path from confirmed facts, unverified assumptions, the real objective, and hard constraints. Use when a process, architecture, product, or system is trapped in patchwork and path dependence, or the user asks to derive from first principles. Skip simple fixes, missing-fact lookups, emergencies needing containment, and cases where standards or tests already determine the answer.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use when recurring patches suggest a wrong frame or path dependence, historical choices block current options, or the user explicitly asks …

    line 12
  2. Very specific:

    Use $fact-claim-audit for disputed inputs.

    line 27
  3. Very specific:

    Use $cross-domain-mechanism-transfer only when the bottom structure is clear and direct domain routes are exhausted.

    line 28
  4. Very specific:

    Use $bidirectional-steelman for a material choice between the rebuilt path and credible alternatives.

    line 29

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

First-Principles Rebuild

Own the separation of facts, assumptions, goals, and constraints, followed by a fresh derivation. Do not use “first principles” to ignore evidence, standards, or safety limits.

Route

Use when recurring patches suggest a wrong frame or path dependence, historical choices block current options, or the user explicitly asks to derive from zero rather than inherit industry convention.

Skip direct facts, fixed procedures, deterministic bugs, and local repairs whose cost is proportionate and sufficient. During an incident, restore safety first; revisit architecture only after containment or when explicitly asked.

Procedure

  1. Define the desired result without naming the current solution.
  2. Make four lists: confirmed unavoidable facts; habitual but unverified assumptions; the real objective; and resources or hard constraints. Demote unsupported “facts” to assumptions.
  3. Identify which parts of the current approach merely preserve historical structure and which alleged constraints are changeable.
  4. Derive at least one path using only confirmed facts, the objective, and hard constraints; “everyone does it” is not a premise.
  5. State the new path’s necessary conditions and the variable most likely to invalidate it.
  6. Design the smallest reversible check that distinguishes the old path from the new one, with an observation and stop or pivot rule.

Handoffs and Boundaries

  • Use $fact-claim-audit for disputed inputs.
  • Use $cross-domain-mechanism-transfer only when the bottom structure is clear and direct domain routes are exhausted.
  • Use $bidirectional-steelman for a material choice between the rebuilt path and credible alternatives.

Completion Gate

Facts, assumptions, goals, and constraints are not mixed. The new path is traceable to them, its key premise is testable, and the first step has a measurable signal and a stop or pivot condition.

Source Status

Distilled from the user-supplied “第一性原理” method card. The card proposes a reconstruction workflow but supplies no comparative result evidence.

<!-- integration-watermark: 红猴子整合 -->

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.