Apply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state in the reader's head; collapse one-caller wrappers and shrink mutable scope.
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
# Minimize Reader Load
Maintainability is the work a reader must do to understand code. Track two axes:
1. **Layers to trace.** How many indirections sit between the question and the answer.
2. **State to hold.** How much hidden or mutable context the reader must keep in their head.
**Why:** Code is read far more than it is written. LOC, cyclomatic complexity, and "clean architecture" are proxies. Reader load is the thing that matters. The two axes are independent. A flat file with 50 globals can be as hard to reason about as a 6-layer adapter stack. Guard both. This is the human analog of [Guard the Context Window](../principle-guard-the-context-window/SKILL.md): working memory is finite for readers too.
**The pattern:**
- **Collapse layers** that do not earn their keep: wrappers with one caller, adapters with no second implementation, indirection introduced for a future that never came. Inline them.
- **Make adjacent layers change the abstraction.** A layer that repeats the same methods and arguments adds reader load without compression. Collapse pass-through layers.
…
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_gosilnhrqmcljaug
GET https://markdownregistry.com/api/v1/resolve?ref=painhardcore/pstack/principle-minimize-reader-load
GET https://markdownregistry.com/api/v1/blob/02f1bf8431cb21e5011d9cf5f426f9d052167564dcb02eac0883965ec2494772
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-minimize-reader-load/SKILL.md · Apply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state…
cursor/plugins · pstack/skills/principle-minimize-reader-load/SKILL.md · Apply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state…
michael-denyer/pstack-claude · plugins/pstack/skills/principle-minimize-reader-load/SKILL.md · Apply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state…
backnotprop/pstack · skills/principle-minimize-reader-load/SKILL.md · Apply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state…
j-star-films-studios/vibecode-protocol-suite · assets/.agent/skills/engineering-principles/minimize-reader-load/SKILL.md · Apply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state…
creedants/pstack-t3 · skills/principle-minimize-reader-load/SKILL.md · Apply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state…
arjitj2/open-pstack · plugins/pstack/skills/principle-minimize-reader-load/SKILL.md · Apply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state…
edbertchan/catstack · corpus/skills/principle-minimize-reader-load/SKILL.md · Apply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state…
