AGENT SKILL

principle-separate-before-serializing-shared-state

Use when concurrent actors may write shared state.

License 许可
MIT
最近更新
2026-11-01
Stars
★ 0
Forks
0

01 前言 Front Matter

name
principle-separate-before-serializing-shared-state
description
Use when concurrent actors may write shared state.
compatibility
Hermes Agent; repository file tools and terminal for checks.

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

ThomsenDrake
ThomsenDrake/agent-skills

using-omi-api

Use when a user wants to read, search, summarize, create, update, delete, import, or automate Omi memories, conversations, transcripts, action items, folders, goals, notifications, OAuth, webhooks, MCP, or omi-cli. Not for Omi device pairing or hardware setup.

★ 0
ThomsenDrake
ThomsenDrake/agent-skills

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.

★ 0
ThomsenDrake
ThomsenDrake/agent-skills

unslop

Cut AI tells from any writing.

★ 0
ThomsenDrake
ThomsenDrake/agent-skills

typescript-best-practices

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

★ 0
ThomsenDrake
ThomsenDrake/agent-skills

technical-writing

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

★ 0
ThomsenDrake
ThomsenDrake/agent-skills

teach

Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.

★ 0