Apply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the rule as a lint, metadata flag, runtime check, or script instead of more text.
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
# Encode Lessons in Structure
Encode recurring fixes in mechanisms (tools, code, metadata, automation) instead of textual instructions. Every error, human correction, and unexpected outcome is a learning signal. Capture it, route it, and close the loop.
**Why:** Textual instructions are easy to miss. They require the reader to notice, remember, and comply. Structural mechanisms (lint rules, metadata flags, runtime checks, automation scripts) enforce the rule without cooperation.
**Pattern:**
When you catch yourself writing the same instruction a second time:
1. Ask: can this be a lint rule, a metadata flag, a runtime check, or a script?
2. If yes, encode it. Delete the instruction
3. If no (genuinely requires judgment), make the instruction more prominent and add an example of the failure mode
**Pick the strongest rung.** When more than one mechanism would work, choose the strongest the situation allows (an unrepresentable state that cannot compile, then a lint or banned API that fails CI, then a canonical helper, then a runtime check), because agents copy whatever the surrounding code already does and a weaker guard becomes the next template.
…
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_5g5ryutfnsdayjm7
GET https://markdownregistry.com/api/v1/resolve?ref=painhardcore/pstack/principle-encode-lessons-in-structure
GET https://markdownregistry.com/api/v1/blob/9ab0e6d979982260ead6410e51709fba4e37add615871993ff8a4725b5f2af3d
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 · pstack/skills/principle-encode-lessons-in-structure/SKILL.md · Apply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the…
cursor/plugins · harness/pstack/claude-code/skills/principle-encode-lessons-in-structure/SKILL.md · Apply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the…
michael-denyer/pstack-claude · plugins/pstack/skills/principle-encode-lessons-in-structure/SKILL.md · Apply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the…
backnotprop/pstack · skills/principle-encode-lessons-in-structure/SKILL.md · Apply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the…
j-star-films-studios/vibecode-protocol-suite · assets/.agent/skills/engineering-principles/encode-lessons-in-structure/SKILL.md · Apply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the…
creedants/pstack-t3 · skills/principle-encode-lessons-in-structure/SKILL.md · Apply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the…
arjitj2/open-pstack · plugins/pstack/skills/principle-encode-lessons-in-structure/SKILL.md · Apply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the…
edbertchan/catstack · corpus/skills/principle-encode-lessons-in-structure/SKILL.md · Apply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the…
