principle-build-the-lever
Skill1 starsChanged 42 days agoMITView on GitHub
Apply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks. Build the tool that does it or proves it (codemod, script, generator, or a skill your subagents follow) instead of working by hand. The tool is the artifact a reviewer can rerun.
53 other projects use a version of this, 37 of them edited; 14 of 37 edited versions we compared changed its rules.
How people change it
14 of 37 edited versions changed its rules, and some changes recur.
Of the 37 edited versions we compared: 23 keep every rule, 14 made changes of their own.
Rules people drop
- Commit the lever when the work outlives the session.dropped by 12 of 14
- When you fan work out to subagents, write the lever as a skill they all read: the recipe, the verification contract, and the do-not-touch fences in one artifact. Keep it outside the delegates' write scope so they can't quietly edit the contract.dropped by 11 of 14
- When the work isn't trivial, build the tool that does it instead of doing it by hand.dropped by 1 of 14
- Default to building the lever. Skip it only when the task is trivial, a couple of obvious edits you can see at a glance.dropped by 1 of 14
- Do the first unit by hand to learn the recipe, then build the tool. Prove it by rerunning it on that unit and diffing against your hand-done version. Make the lever safe to rerun.dropped by 1 of 14
Rules people add
- Commit the lever when the work outlives the session, so the next run reruns it instead of redoing it.added by 11 of 14
We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.
Adopted by
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Most recently taken up by
- gfunc/skillsword for word, first seen Nov 16, 2026
- shiwenbin1617/pstackword for word, first seen Nov 16, 2026
- Dimon94/dverityword for word, first seen Nov 15, 2026
- Dimon94/skillsword for word, first seen Nov 15, 2026
- backnotprop/pstackword for word, first seen Nov 15, 2026
- sammyjoyce/prime-pstackedited, first seen Nov 15, 2026
Used with
Projects with it also use setup-pstack, poteto-help 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.
bnemaSkillsetup-pstack
Configure which Pi models pstack uses per role. Detects available provider/model specs and writes pstack's user configuration. Use for /setup-pstack, "configure pstack models", or changing pstack model choices.
Also in 25 projects that use this
ianclearySkillpoteto-help
Guides users through pstack setup, /poteto-mode, and picking the skill, playbook, or principle for a task. Type /poteto-help with a question.
Also in 14 projects that use this
eryzerzSkillmake-bot-ui
Use when building a custom UI (page, dashboard, buttons) that should wake a Grok Bot over a webhook, when the user must provide a webhook sender key, or when exposing that UI on Tailscale.
Also in 18 projects that use this
TheOnlyFusionCubeSkillstatechart
Draw what an app's user sees as a Mermaid statechart from a TLA+ model. States are gray if they work, red if still wrong, and green if fixed. Each bug TLC finds is a numbered path. Use for /statechart, \"show the PM the bug\", or to turn an agreed chart into a TLA+ skeleton.
Also in 15 projects that use this
JoshueOsunaSkillPoteto Mode
poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style.
Also in 3 projects that use this
Other versions53 projects use a version of this.
Word for word · 13
- backnotprop/pstack★ 4.2k100% same
- Dimon94/dverity★ 107100% same
- Dimon94/skills★ 107100% same
- mariusflorescu/pstack-t3★ 13100% same
- adjohn/pstack★ 9100% same
- alexnthnz/keel★ 5100% same
- shiwenbin1617/pstack★ 4100% same
- conscientiousness/herdr-pstack-orchestrator★ 2100% same
- fullerzz/agent-skills★ 2100% same
- gfunc/skills★ 1100% same
3 more not listed
Edited · 37
- jtaroreh/agystack★ 12885% same
- uzairansaruzi/p3-stack★ 12694% same
- dsebban/skills★ 7195% same
- painhardcore/pstack★ 2299% same
- creedants/pstack-t3★ 1899% same
- Scino/fstack★ 1398% same
- kkgogogo17/pi-pstack★ 985% same
- mdsmithaustin/pstack★ 999% same
- 0xrsydn/pstack-pi★ 785% same
- bnema/pi-pstack★ 285% same
27 more not listed
Wrote their own version · 3
- TheOnlyFusionCube/potetos-for-everyone★ 21same name
- requie/endostack★ 4same name
- 3metaJun/mstack★ 0same name
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 repository56 other files it gives its agents.
- architectSkill
- arenaSkill
- automate-meSkill
- benchmark-checklistSkill
- blast-radiusSkill
- broSkill
- correctSkill
- create-formal-verification-skillSkill
- create-verification-skillSkill
- figure-it-outSkill
- helpSkill
- howSkill
- interrogateSkill
- in-your-own-wordsSkill
- ketchupSkill
- ketchup-videoSkill
- leadSkill
- maintain-formal-verification-skillSkill
- maintain-verification-skillSkill
- no-commentsSkill
- principle-attack-the-premiseSkill
- principle-boundary-disciplineSkill
- principle-encode-lessons-in-structureSkill
- principle-exhaust-the-design-spaceSkill
- principle-experience-firstSkill
- principle-explain-the-numberSkill
- principle-fix-root-causesSkill
- principle-foundational-thinkingSkill
- principle-guard-the-context-windowSkill
- principle-laziness-protocolSkill
- principle-make-operations-idempotentSkill
- principle-migrate-callers-then-delete-legacy-apisSkill
- principle-minimize-reader-loadSkill
- principle-model-the-domainSkill
- principle-never-block-on-the-humanSkill
- principle-outcome-oriented-executionSkill
- principle-prove-it-worksSkill
- principle-redesign-from-first-principlesSkill
- principle-separate-before-serializing-shared-stateSkill
- principle-sequence-verifiable-unitsSkill
- principle-subtract-before-you-addSkill
- principle-test-behavior-not-implementationSkill
- principle-type-system-disciplineSkill
- qmdSkill
- recallSkill
- reflectSkill
- setupSkill
- sharpenSkill
- show-me-your-workSkill
- swarmSkill
- tddSkill
- teachSkill
- technical-writingSkill
- typescript-best-practicesSkill
- unslopSkill
- whySkill
The file
We split this skill into the rules it gives an agent
5 rules. 5 are common, 0 are distinctive, and 0 are very specific to this project.
5
Common
Most of the 40 edited versions we read keep these.
0
Distinctive
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
- Common: line 8
When the work isn't trivial, build the tool that does it instead of doing it by hand.
- Common: line 12
Default to building the lever.
- Common: line 14
Do the first unit by hand to learn the recipe, then build the tool.
- Common: line 17
When you fan work out to subagents, write the lever as a skill they all read: the recipe, the verification contract, and the do-not-touch …
- Common: line 19
Commit the lever when the work outlives the session.
“Common” is measured: kept by at least 6 in 10 of the 40 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Build the Lever
When the work isn't trivial, build the tool that does it instead of doing it by hand.
A codemod, generator, or script does the work the same way every time and reruns for free. The tool is one artifact a reviewer can read and rerun to check the work. Hand-done changes can only be re-verified by redoing them. A deterministic script turns "trust me" into "run this".
Default to building the lever. Skip it only when the task is trivial, a couple of obvious edits you can see at a glance.
- Do the first unit by hand to learn the recipe, then build the tool. Prove it by rerunning it on that unit and diffing against your hand-done version. Make the lever safe to rerun.
- Codemod or script for edits, generator for repetitive files, a dump-to-sqlite query for analysis, a rerunnable check for verification.
- A deterministic lever beats fan-out. If the tool can process every unit in one pass, run it yourself. Don't fan out delegates to hand-apply what a script can do.
- When you fan work out to subagents, write the lever as a skill they all read: the recipe, the verification contract, and the do-not-touch fences in one artifact. Keep it outside the delegates' write scope so they can't quietly edit the contract.
- Applying this principle produces a file. If you cited it and there is no codemod, script, generator, or delegate skill in the diff, you didn't apply it.
- Commit the lever when the work outlives the session.
The bar is triviality, not repetition. A one-off still earns a lever when the lever is what makes the work checkable. Per the Laziness Protocol, build the smallest script that does or proves the job, never a framework.
Distinct from Encode Lessons in Structure, which makes a recurring instruction a durable guardrail. This is throughput and reviewability on the work in front of you. For scripting the verification itself, see Prove It Works.
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.

