[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A7XYKFSCZGFWWCWYE1RT4Q":3,"skill-same:01M7A7XYKFSCZGFWWCWYE1RT4Q":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":45},"01M7A7XYKFSCZGFWWCWYE1RT4Q","principle-separate-before-serializing-shared-state",null,"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.","am-will\u002Fgooey-pi","am-will","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42459108?v=4","01M6DGTYZDSE8HR73NQBJ31689","am.will","01M7A7TJ263XAJ06M4HD6MTTJD",974,"MIT","https:\u002F\u002Fgithub.com\u002Fam-will\u002Fgooey-pi\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpstack\u002Fprinciple-separate-before-serializing-shared-state\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: principle-separate-before-serializing-shared-state\ndescription: \"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.\"\ndisable-model-invocation: true\n---\n\n# Separate Before Serializing Shared State\n\nWhen 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.\n\n**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.\n\n**Pattern:**\n1. **Identify shared mutable state** (files both read and write, branches both push to, APIs both define and consume).\n2. **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\u002Freporting boundary. Two workers writing their own `lastX` field into one `state.json` is still shared mutation; `indexer-state.json` + `metrics-state.json` is not.\n3. **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.\n","# Separate Before Serializing Shared State\n\nWhen 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.\n\n**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.\n\n**Pattern:**\n1. **Identify shared mutable state** (files both read and write, branches both push to, APIs both define and consume).\n2. **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\u002Freporting boundary. Two workers writing their own `lastX` field into one `state.json` is still shared mutation; `indexer-state.json` + `metrics-state.json` is not.\n3. **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.\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","f63b9cfa707488880eeb9f47984fbf383e397322",".agents\u002Fskills\u002Fpstack\u002Fprinciple-separate-before-serializing-shared-state",87,"https:\u002F\u002Fgithub.com\u002Fam-will\u002Fgooey-pi","https:\u002F\u002Fgithub.com\u002Fam-will","Context Engineer, Developer, Husband, Father","2026-10-25 13:02:03",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":24},[35,38,41],{"tool":36,"command":37},"npx","npx skills add am-will\u002Fgooey-pi --skill principle-separate-before-serializing-shared-state",{"tool":39,"command":40},"bunx","bunx skills add am-will\u002Fgooey-pi --skill principle-separate-before-serializing-shared-state",{"tool":42,"command":43},"pnpm","pnpm dlx skills add am-will\u002Fgooey-pi --skill principle-separate-before-serializing-shared-state","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fam-will\u002Fgooey-pi\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpstack\u002Fprinciple-separate-before-serializing-shared-state\u002FSKILL.md",[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7A8040XWQF3KCYT7G12G1TA","prime-work-schedules","Create, inspect, edit, pause, resume, run, and delete durable GooeyPi scheduled tasks. Use when the user asks to schedule recurring or one-time work in the current project or thread. Use rlm-heartbeat instead for temporary internal polling while actively working.","https:\u002F\u002Fgithub.com\u002Fam-will\u002Fgooey-pi\u002Fblob\u002Fmain\u002Fassets\u002Fskills\u002Fprime-work-schedules\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7A7ZYRC65CS56VJV4CVKWFV","prime-work-browser","Drive the GooeyPi in-app browser for this thread with the browser_* tools - open tabs, navigate, read pages, click, type, scroll, screenshot, and extract data. Use when the user asks to open, test, inspect, or interact with a website or a local dev server inside GooeyPi.","https:\u002F\u002Fgithub.com\u002Fam-will\u002Fgooey-pi\u002Fblob\u002Fmain\u002Fassets\u002Fskills\u002Fprime-work-browser\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7A7ZV00WXP2QFC5YPDJXTNV","gooeypi-computer-use","Drive native applications on macOS, Windows, or Linux through the separately installed TryCUA driver CLI.","https:\u002F\u002Fgithub.com\u002Fam-will\u002Fgooey-pi\u002Fblob\u002Fmain\u002Fassets\u002Fskills\u002Fgooeypi-computer-use\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7A7ZNTPXAJ17VX4MTAND91G","verify-gooeypi","Launch and drive the GooeyPi desktop (Electron) app to prove user-facing behavior — sidebar navigation, Settings, and Capabilities — capturing screenshots and ARIA snapshots. Reach for this when verifying a GooeyPi UI change or confirming the app still works end to end.","https:\u002F\u002Fgithub.com\u002Fam-will\u002Fgooey-pi\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fverify-gooeypi\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7A7ZK9FBXTZC33HEAJ4C3HW","review-pr-viability","Review a pull request or issue for value, implementation quality, maintainability, regression risk, and reliance on upstream changes.","https:\u002F\u002Fgithub.com\u002Fam-will\u002Fgooey-pi\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Freview-pr-viability\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7A7ZDK2B6KE9ZE33GS4V180","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.","https:\u002F\u002Fgithub.com\u002Fam-will\u002Fgooey-pi\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpstack\u002Fwhy\u002FSKILL.md",[],[]]