principle-separate-before-serializing-shared-state from painhardcore/pstack is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
Apply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first; serialize structurally only when one shared writer is a real invariant.
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
# Separate Before Serializing Shared State
When concurrent actors might share mutable state, first ask whether they truly need the same mutable object. If not, eliminate the sharing. When sharing is real, enforce serialization structurally: lockfiles, sequential phases, exclusive ownership. Instructions and conventions are not concurrency control.
**Why:** Concurrent writes to shared state create race conditions that are intermittent, hard to reproduce, and expensive to debug. Telling agents or goroutines to "take turns" does not work.
**Pattern:**
1. **Identify shared mutable state** (files both read and write, branches both push to, APIs both define and consume).
2. **Default: eliminate the shared write target.** Ask: do these actors need one canonical object, or are they publishing independent facts? Give each actor its own owned file, key, branch, or state directory, and merge only at the read/reporting boundary. Two workers writing their own `lastX` field into one `state.json` is still shared mutation; `indexer-state.json` + `metrics-state.json` is not.
…
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_5u25fnhkwzwbjcxs
GET https://markdownregistry.com/api/v1/resolve?ref=painhardcore/pstack/principle-separate-before-serializing-shared-state
GET https://markdownregistry.com/api/v1/blob/d3fc7b258718c845ec880e14a0ef36fab59a6a4c1ccb16d811a2bcb1f46e5489
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-separate-before-serializing-shared-state/SKILL.md · Apply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first…
cursor/plugins · pstack/skills/principle-separate-before-serializing-shared-state/SKILL.md · Apply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first…
michael-denyer/pstack-claude · plugins/pstack/skills/principle-separate-before-serializing-shared-state/SKILL.md · Apply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first…
backnotprop/pstack · skills/principle-separate-before-serializing-shared-state/SKILL.md · Apply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first…
j-star-films-studios/vibecode-protocol-suite · assets/.agent/skills/engineering-principles/separate-before-serializing-shared-state/SKILL.md · Apply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first…
creedants/pstack-t3 · skills/principle-separate-before-serializing-shared-state/SKILL.md · Apply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first…
arjitj2/open-pstack · plugins/pstack/skills/principle-separate-before-serializing-shared-state/SKILL.md · Apply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first…
edbertchan/catstack · corpus/skills/principle-separate-before-serializing-shared-state/SKILL.md · Apply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first…
