Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that solves the problem.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Laziness Protocol
Writing code is cheap for you, which makes over-engineering easy. Counter it by borrowing a human maintainer's fatigue. Aim for the most result with the least code and complexity.
- **Prefer deletion.** When asked to refactor or improve, look for removals before additions.
- **Maintain a flat call hierarchy.** Avoid deep call chains. A rich interface that hides substantial work is not a deep call chain. If answering a question requires tracing through more than 3 files or layers, flatten it.
- **Consolidate decisions.** Do not repeat the same choice in several places. Put it behind one source of truth and pass the result as a simple flag.
- **Minimize the diff.** Make the smallest change that solves the problem. Fewer lines beat "elegant" boilerplate.
- **Question the threading.** If a task asks you to pass a new signal through types, schemas, pipelines, or similar layers, stop and look for a more direct path.
- **Sweat the small leaks.** Remove tiny pass-throughs, representation leaks, and duplicated choices before they spread. Small leaks compound into permanent coordination costs.
…
The line at the top of this page pins the label git:20260827.04830a9, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_vslckvjhnwllugmt
GET https://markdownregistry.com/api/v1/resolve?ref=painhardcore/pstack/principle-laziness-protocol
GET https://markdownregistry.com/api/v1/blob/02cd2c474b9ceec8611ce9bd8861eb4e5129aa324223d8b6b0e1a1d847347585
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
painhardcore/pstack · .opencode/skills/architect/SKILL.md · Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use…
painhardcore/pstack · .opencode/skills/arena/SKILL.md · Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for…
painhardcore/pstack · .opencode/skills/blast-radius/SKILL.md · Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe…
painhardcore/pstack · .opencode/skills/create-verification-skill/SKILL.md · Generate a project-local verification skill that drives your app the way a user does — any language, framework, or…
painhardcore/pstack · .opencode/skills/figure-it-out/SKILL.md · Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a…
painhardcore/pstack · .opencode/skills/how/SKILL.md · Explain how a subsystem works, trace a runtime flow, or determine where code and ownership belong before making a…
painhardcore/pstack · .opencode/skills/interrogate/SKILL.md · Use for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find…
painhardcore/pstack · .opencode/skills/principle-boundary-discipline/SKILL.md · Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI…
cursor/plugins · harness/pstack/claude-code/skills/principle-laziness-protocol/SKILL.md · Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward…
cursor/plugins · pstack/skills/principle-laziness-protocol/SKILL.md · Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward…
michael-denyer/pstack-claude · plugins/pstack/skills/principle-laziness-protocol/SKILL.md · Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward…
backnotprop/pstack · skills/principle-laziness-protocol/SKILL.md · Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward…
j-star-films-studios/vibecode-protocol-suite · assets/.agent/skills/engineering-principles/laziness-protocol/SKILL.md · Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward…
creedants/pstack-t3 · skills/principle-laziness-protocol/SKILL.md · Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward…
arjitj2/open-pstack · plugins/pstack/skills/principle-laziness-protocol/SKILL.md · Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward…
edbertchan/catstack · corpus/skills/principle-laziness-protocol/SKILL.md · Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward…
