AGENT SKILL

principle-separate-before-serializing-shared-state

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.

License 许可
MIT
最近更新
2026-10-28
Stars
★ 1
Forks
0

01 前言 Front Matter

name
principle-separate-before-serializing-shared-state
description
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.
disable-model-invocation
true

03 SKILL.md 正文

Separate Before Serializing Shared State

When concurrent actors might share mutable state, first ask whether they 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.

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.
  3. Only when one shared write target is a real invariant, serialize access structurally (lockfiles, sequential phases, single-writer actor, or atomic compare-and-swap). Treat "we need a lock" as a design smell to check, not as the default answer.

04 同仓库更多 Skills

willgosnold
willgosnold/patchbook

patchbook-update

Pull upstreams into a repo that keeps its changes in a patchbook (.patchbook/), repair what broke from each change's intent, test and review, then merge and deploy only when the sync was clean or the test command passes, and otherwise ask, opening a pull request when there are commits to push. Use when a scheduled task or the user says to update a patchbook repo, or for /patchbook-update or $patchbook-update.

★ 1
willgosnold
willgosnold/patchbook

why

Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.

★ 1
willgosnold
willgosnold/patchbook

verify-patchbook

Drive the patchbook CLI from this checkout in a disposable sandbox (its own git repos, store, config and a fake model) and capture a transcript as proof. Use to reproduce a patchbook bug, run an issue's repro script, or prove a change to clone, init, record, the pre-commit hook, build, status, check, sync or upstream works the way a user would see it.

★ 1
willgosnold
willgosnold/patchbook

unslop

Cut AI tells from any writing.

★ 1
willgosnold
willgosnold/patchbook

typescript-best-practices

TypeScript best practices. Use when reading or editing any .ts or .tsx file.

★ 1
willgosnold
willgosnold/patchbook

technical-writing

Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or $technical-writing, or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.

★ 1