principle-laziness-protocol
Skill1 starsChanged 12 days agoMITView on GitHub
Apply before writing new analysis code, when refactoring, reviewing the size of an analysis diff, or tempted to add abstractions, layers, or parameters to a pipeline or notebook. Run the decision ladder first, then bias toward deletion and the smallest change that solves the problem.
46 other projects use a version of this, 43 of them edited.
Adopted by
Most recently taken up by
- paramcodes/skillsedited, first seen Nov 8, 2026
- tristanphvn/keeledited, first seen Nov 8, 2026
- requie/endostacktheir own version, first seen Nov 8, 2026
- creedants/pstack-t3edited, first seen Nov 3, 2026
- painhardcore/pstackedited, first seen Nov 2, 2026
- christofferbergj/agent-skillsedited, first seen Nov 1, 2026
Used with
Projects with it also use setup-pstack, poteto-help and 4 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 19 projects that use this
tristanphvnSkillketchup-video
Catch the user up like /keel:ketchup, with a short silent video of slides for what happened and the waiting calls as text under it. Use for /keel:ketchup-video.
Also in 11 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
instructureSkillketchup
Rebuild context after /clear by analyzing uncommitted changes across Canvas LMS and all plugin repositories
Also in 18 projects that use this
Other versions46 projects use a version of this.
Word for word · 0
None found.
Edited · 43
- backnotprop/pstack★ 3.8k47% same
- jtaroreh/agystack★ 12815% same
- uzairansaruzi/p3-stack★ 12617% same
- dsebban/skills★ 7147% same
- creedants/pstack-t3★ 1853% same
- painhardcore/pstack★ 1853% same
- mariusflorescu/pstack-t3★ 1347% same
- adjohn/pstack★ 947% same
- kkgogogo17/pi-pstack★ 915% same
- 0xrsydn/pstack-pi★ 615% same
33 more not listed
Wrote their own version · 3
- TheOnlyFusionCube/potetos-for-everyone★ 21same name
- Scino/fstack★ 18same name
- requie/endostack★ 4same 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 repository50 other files it gives its agents.
- analyst-modeSkill
- architectSkill
- arenaSkill
- astack-helpSkill
- benchmark-checklistSkill
- blast-radiusSkill
- catch-upSkill
- correctSkill
- create-formal-verification-skillSkill
- figure-it-outSkill
- howSkill
- interrogateSkill
- in-your-own-wordsSkill
- maintain-formal-verification-skillSkill
- no-commentsSkill
- plain-wordsSkill
- principle-attack-the-premiseSkill
- principle-boundary-disciplineSkill
- principle-build-the-leverSkill
- principle-define-the-questionSkill
- principle-encode-lessons-in-structureSkill
- principle-experience-firstSkill
- principle-explain-the-numberSkill
- principle-fix-root-causesSkill
- principle-foundational-thinkingSkill
- principle-guard-the-context-windowSkill
- principle-make-operations-idempotentSkill
- principle-minimize-reader-loadSkill
- principle-model-the-domainSkill
- principle-name-the-estimandSkill
- principle-never-block-on-the-humanSkill
- principle-prove-it-worksSkill
- principle-reproduce-from-clean-stateSkill
- principle-respect-the-grainSkill
- principle-sequence-verifiable-unitsSkill
- principle-simulate-the-methodSkill
- principle-subtract-before-you-addSkill
- principle-test-behavior-not-implementationSkill
- recallSkill
- reflectSkill
- retail-analyticsSkill
- sharpenSkill
- show-me-your-workSkill
- statechartSkill
- swarmSkill
- tddSkill
- teachSkill
- technical-writingSkill
- unslopSkill
- whySkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 46 edited versions we read keep these.
1
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
- Distinctive: line 14
Never cut: validation at trust boundaries (an incoming feed, a file drop, an API response), error handling that prevents data loss or a …
“Common” is measured: kept by at least 6 in 10 of the 46 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
Laziness Protocol
- Run the ladder before you write, and take the first rung that fully does the job. (1) It does not need to exist: skip the feature, option, or flexibility nobody asked for. (2) Something in this codebase already does it: a helper, a shared query fragment, a pattern the surrounding code uses. (3) The standard library or the platform does it: a Polars or SQL construct, a notebook or dashboard feature. (4) An installed dependency does it; never add a dependency for a few lines. (5) It fits in one line a reader gets at a glance. (6) Otherwise, write the minimum code that works.
- Consolidate decisions. Do not repeat the same choice in several places, such as a date window, a currency conversion, or a rule for active users. Put it behind one source of truth, a single config value or a named function, and pass the result as a simple parameter.
- Minimize the diff. Make the smallest change that solves the problem. Fewer lines beat elegant boilerplate. A three-line filter in a query beats a new module with a class hierarchy.
- Be lazy about the solution, never about the change itself. Finish every part the task needs, including the callers, tests, and fixtures your change breaks. For a bug, grep every caller of the code you touch and fix the root cause once in the shared code, not once per call site.
- New non-trivial logic (a branch, a loop, a parser, money or identity matching, or a whole new script) leaves one small test or an assert-based self-check. Trivial changes need none.
- A shortcut with a known limit gets a comment in this form:
shortcut: <the limit>, <when to upgrade>. - Never cut: validation at trust boundaries (an incoming feed, a file drop, an API response), error handling that prevents data loss or a silently wrong number, security, accessibility in a chart or dashboard a reader sees, and anything the user asked for.
- Laziness never overrides verification. Data checks, result-validity and statistical-validity review, and the data guard rules apply at full strength, even when they make the change bigger.
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.

