[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FES29146C8DP9726GY330S":3,"skill-same:01M7FES29146C8DP9726GY330S":78},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7FES29146C8DP9726GY330S","system-design-case",null,"Document a system you designed as an interview case, with a design doc, decision records (why plus trade-offs), archify architecture\u002Fsequence diagrams that stay in sync, and a generated page to present it on screen share. Use when starting a case, recording or revising a design decision, adding a flow diagram to a case, presenting a case, or rehearsing a case for a reverse system design interview.","heynemann\u002Fdotfiles-stow","heynemann","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F60965?v=4","01M7DFBD9ZDB2J2QE7R4AR0PES","Bernardo Heynemann","01M7FERV0J6GMQ0RHEH6EHGYRW",0,"MIT","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Fdoordash\u002Fagent\u002Fskills\u002Fsystem-design-case\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: system-design-case\ndescription: Document a system you designed as an interview case, with a design doc, decision records (why plus trade-offs), archify architecture\u002Fsequence diagrams that stay in sync, and a generated page to present it on screen share. Use when starting a case, recording or revising a design decision, adding a flow diagram to a case, presenting a case, or rehearsing a case for a reverse system design interview.\n---\n\n# System design case\n\nA **case** is one system you designed, documented so you can present it in two minutes and defend every choice under questioning. Each artifact owns one meaning:\n\n- `README.md`: the narrative, from the pitch down to the deep dives.\n- `decisions\u002FD-NN-\u003Cslug>.md`: why each choice was made and what it cost.\n- `diagrams\u002F`: archify JSON sources (the diffable truth) and their rendered HTML.\n- `index.html`: the page you share on screen, generated from the three above; never edit it by hand.\n\n```\ncases\u002Findex.html                       ← generated hub linking every case\ncases\u002F\u003Cslug>\u002F\n  README.md                            ← from templates\u002Fcase.md\n  decisions\u002FD-01-\u003Cslug>.md             ← from templates\u002Fdecision.md\n  diagrams\u002Farchitecture.json → .html\n  diagrams\u002F\u003Cflow>.sequence.json → .html\n  figures\u002F                             ← optional diagram-design static figures\n  index.html                           ← generated by scripts\u002Fbuild-page.mjs\n```\n\nCases live under `cases\u002F` in the interview-prep repo (`\u002Fhome\u002Fheynemann\u002Fsrc\u002Fdoordash`); paths below are relative to that repo root. `cases\u002F` is its own git clone of [heynemann\u002Fcases](https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fcases) (private): commit case changes there, with `.evidence\u002F` git-ignored. Case diagrams are living documents rendered in place at these stable paths, which takes precedence over archify's timestamped `.archify\u002F` folders. Worked example: `cases\u002Fexample-order-dispatch\u002F`.\n\n## Starting a case\n\n1. **Grill the user.** Copy `templates\u002Fcase.md` to the case's `README.md`, then read the `grilling` skill and [`references\u002Finterview-map.md`](references\u002Finterview-map.md) and run a grilling session whose design tree starts from the map's branches. Facts about a past system come only from the user: a recommended answer is a hypothesis for them to correct, never recorded unconfirmed; look facts up yourself only in a repository the user points you to. After each round, write the settled answers where the map says (README sections, `decisions\u002FD-NN-\u003Cslug>.md` from `templates\u002Fdecision.md`, numbered from `D-01`), so stopping mid-session loses nothing. The session ends when every branch is settled; list every `TBD(\u003Cquestion>)` back to the user.\n2. **Diagrams**: read the archify skill, then author `diagrams\u002Farchitecture.json` and one sequence per key flow (usually the happy path plus the hardest failure path). Set `meta.output` to the matching `.html` path and run from the repo root, with a fresh timestamp each time the JSON changes (archify will not overwrite the previous run's check results, so retries of unchanged JSON reuse the same folder):\n\n   ```bash\n   node \u003Carchify-skill-dir>\u002Fbin\u002Farchify.mjs finalize \u003Ctype> cases\u002F\u003Cslug>\u002Fdiagrams\u002F\u003Cname>.json cases\u002F\u003Cslug>\u002Fdiagrams\u002F\u003Cname>.html \\\n     --quality showcase --out-dir cases\u002F\u003Cslug>\u002Fdiagrams\u002F.evidence\u002F\u003Cname>-\u003CYYYYMMDD-HHMMSS> --json\n   ```\n\n   A sequence segment's label is drawn 22px above its `from` and shifts up past any colliding message, so leave about 30px between each segment's `from` and the message or segment above it. Passing gates do not catch a misplaced label; look at a `visual-check` capture before calling a new sequence done.\n\n3. **Wire the links** per Sync below.\n4. **Build the page** per Presenting below.\n\nDone when: every interview-map branch is settled, every decision-log row has a record, every record's `Affects` IDs exist in its diagram, every accepted decision is wired per Sync, every diagram's `finalize` passes, the page is rebuilt, and every TBD has been reported.\n\n## Decision records\n\nThe interview value is the reasoning, so each record answers what a senior interviewer probes:\n\n- **Title states the choice**, not the topic: \"Batch dispatch every few seconds instead of greedy per-order assignment\".\n- **Options** include the alternative the interviewer will suggest (\"why not just use X?\"), each with its wins and costs.\n- **Deciding force**: the one constraint or number that tipped it. If the user can't name it, ask until they can; that gap is exactly where an interview goes wrong.\n- **Cost accepted**: what got worse, by how much, and how it was contained.\n- **Revisit when**: the observable signal that would flip the decision.\n\n**Supersede, keep history.** A changed decision gets a new record; the old one keeps its text with `Status: superseded by D-NN`. \"We started with X and moved to Y because Z\" is the strongest story in a reverse interview.\n\n## Sync\n\nLinks run both ways, and archify component\u002Fparticipant IDs are the stable join keys (renaming one breaks links):\n\n- **Decision → diagram**: the record's `Affects` line names the diagram file and the IDs it changes; its first architecture ID is the decision's **anchor** node.\n- **Diagram → decision**: the anchor component's `tag` is `\"D-NN · \u003C2-3 words>\"`, and the architecture's only card is `\"Decisions\"`, one item per accepted decision: `\"D-NN · \u003Cchoice>: \u003Cwhat it bought>, \u003Cwhat it cost>\"`. Sequence participants have no `tag`, so a sequence cites D-NN in its card items.\n- **README → interactive diagram**: the deep-dive menu links each decision to `diagrams\u002Farchitecture.html#focus=\u003Canchor-id>`, which dims the rest and opens the anchor's detail panel with its tag and connections. `#route=\u003Cfrom-id>~\u003Cto-id>` highlights a whole path for flow questions.\n- **README**: one decision-log row per record (ID, decision, deciding force, cost accepted).\n\nArchify still validates `meta.views` but renders nothing from it; use the links above instead.\n\nWhen a decision changes: grill the map's Decisions branch for the new record (and any branch the change reopens), supersede the old record, edit the JSON of every diagram in `Affects` (tag, card item), rerun `finalize` for each, update the log row and deep link, and rebuild the page.\n\n## Presenting\n\nRun from the repo root after any change to the markdown or diagrams:\n\n```bash\nnode \u002Fhome\u002Fheynemann\u002F.omp\u002Fprofiles\u002Fdoordash\u002Fagent\u002Fskills\u002Fsystem-design-case\u002Fscripts\u002Fbuild-page.mjs cases\u002F\u003Cslug>\n```\n\nIt writes `cases\u002F\u003Cslug>\u002Findex.html` and rebuilds the hub `cases\u002Findex.html`, which lists every case; pass `cases` instead of `cases\u002F\u003Cslug>` to rebuild all of them. Open the hub as a local file, pick the case, and share that browser tab:\n\n- The narrative scrolls beside a pinned, fully interactive archify viewer (path tracing, lens, map, node details all work in place). On each decision it shows archify's focus on the anchor (superseded decisions are stamped historical); on each key flow it switches to that flow's sequence diagram. Each state loads once and keeps whatever you traced in it when you scroll back.\n- `F` (or Expand) opens the current state full-screen for deep-dive questions; Esc closes it. README links with `#route=…` open that path live in the panel.\n- The D-NN chips and `Ctrl\u002F⌘K` jump to any decision when the interviewer asks about it.\n- The README's \"Interview prep\" section is never rendered, so pitch notes and hard-question answers stay private.\n\n`build-page` warns when an `Affects` id is not a node in its diagram's archify JSON, since archify's focus then has nothing to show.\n\nThe page reads the template structure (`##` section names, the `**Status:**`\u002F`**Affects:**` line, the Options table with the chosen option in bold), so keep records in template shape for them to render.\n\n## Rehearsing\n\nPlay the interviewer with the `grilling` skill (what `\u002Fgrill-me` runs), aimed at the case: pitch, then each record's cost and revisit-when, then failure modes, then the map's branches the README answers thinnest. Write every answer that holds up back into its record or the README's hard-questions list.\n","# System design case\n\nA **case** is one system you designed, documented so you can present it in two minutes and defend every choice under questioning. Each artifact owns one meaning:\n\n- `README.md`: the narrative, from the pitch down to the deep dives.\n- `decisions\u002FD-NN-\u003Cslug>.md`: why each choice was made and what it cost.\n- `diagrams\u002F`: archify JSON sources (the diffable truth) and their rendered HTML.\n- `index.html`: the page you share on screen, generated from the three above; never edit it by hand.\n\n```\ncases\u002Findex.html                       ← generated hub linking every case\ncases\u002F\u003Cslug>\u002F\n  README.md                            ← from templates\u002Fcase.md\n  decisions\u002FD-01-\u003Cslug>.md             ← from templates\u002Fdecision.md\n  diagrams\u002Farchitecture.json → .html\n  diagrams\u002F\u003Cflow>.sequence.json → .html\n  figures\u002F                             ← optional diagram-design static figures\n  index.html                           ← generated by scripts\u002Fbuild-page.mjs\n```\n\nCases live under `cases\u002F` in the interview-prep repo (`\u002Fhome\u002Fheynemann\u002Fsrc\u002Fdoordash`); paths below are relative to that repo root. `cases\u002F` is its own git clone of [heynemann\u002Fcases](https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fcases) (private): commit case changes there, with `.evidence\u002F` git-ignored. Case diagrams are living documents rendered in place at these stable paths, which takes precedence over archify's timestamped `.archify\u002F` folders. Worked example: `cases\u002Fexample-order-dispatch\u002F`.\n\n## Starting a case\n\n1. **Grill the user.** Copy `templates\u002Fcase.md` to the case's `README.md`, then read the `grilling` skill and [`references\u002Finterview-map.md`](references\u002Finterview-map.md) and run a grilling session whose design tree starts from the map's branches. Facts about a past system come only from the user: a recommended answer is a hypothesis for them to correct, never recorded unconfirmed; look facts up yourself only in a repository the user points you to. After each round, write the settled answers where the map says (README sections, `decisions\u002FD-NN-\u003Cslug>.md` from `templates\u002Fdecision.md`, numbered from `D-01`), so stopping mid-session loses nothing. The session ends when every branch is settled; list every `TBD(\u003Cquestion>)` back to the user.\n2. **Diagrams**: read the archify skill, then author `diagrams\u002Farchitecture.json` and one sequence per key flow (usually the happy path plus the hardest failure path). Set `meta.output` to the matching `.html` path and run from the repo root, with a fresh timestamp each time the JSON changes (archify will not overwrite the previous run's check results, so retries of unchanged JSON reuse the same folder):\n\n   ```bash\n   node \u003Carchify-skill-dir>\u002Fbin\u002Farchify.mjs finalize \u003Ctype> cases\u002F\u003Cslug>\u002Fdiagrams\u002F\u003Cname>.json cases\u002F\u003Cslug>\u002Fdiagrams\u002F\u003Cname>.html \\\n     --quality showcase --out-dir cases\u002F\u003Cslug>\u002Fdiagrams\u002F.evidence\u002F\u003Cname>-\u003CYYYYMMDD-HHMMSS> --json\n   ```\n\n   A sequence segment's label is drawn 22px above its `from` and shifts up past any colliding message, so leave about 30px between each segment's `from` and the message or segment above it. Passing gates do not catch a misplaced label; look at a `visual-check` capture before calling a new sequence done.\n\n3. **Wire the links** per Sync below.\n4. **Build the page** per Presenting below.\n\nDone when: every interview-map branch is settled, every decision-log row has a record, every record's `Affects` IDs exist in its diagram, every accepted decision is wired per Sync, every diagram's `finalize` passes, the page is rebuilt, and every TBD has been reported.\n\n## Decision records\n\nThe interview value is the reasoning, so each record answers what a senior interviewer probes:\n\n- **Title states the choice**, not the topic: \"Batch dispatch every few seconds instead of greedy per-order assignment\".\n- **Options** include the alternative the interviewer will suggest (\"why not just use X?\"), each with its wins and costs.\n- **Deciding force**: the one constraint or number that tipped it. If the user can't name it, ask until they can; that gap is exactly where an interview goes wrong.\n- **Cost accepted**: what got worse, by how much, and how it was contained.\n- **Revisit when**: the observable signal that would flip the decision.\n\n**Supersede, keep history.** A changed decision gets a new record; the old one keeps its text with `Status: superseded by D-NN`. \"We started with X and moved to Y because Z\" is the strongest story in a reverse interview.\n\n## Sync\n\nLinks run both ways, and archify component\u002Fparticipant IDs are the stable join keys (renaming one breaks links):\n\n- **Decision → diagram**: the record's `Affects` line names the diagram file and the IDs it changes; its first architecture ID is the decision's **anchor** node.\n- **Diagram → decision**: the anchor component's `tag` is `\"D-NN · \u003C2-3 words>\"`, and the architecture's only card is `\"Decisions\"`, one item per accepted decision: `\"D-NN · \u003Cchoice>: \u003Cwhat it bought>, \u003Cwhat it cost>\"`. Sequence participants have no `tag`, so a sequence cites D-NN in its card items.\n- **README → interactive diagram**: the deep-dive menu links each decision to `diagrams\u002Farchitecture.html#focus=\u003Canchor-id>`, which dims the rest and opens the anchor's detail panel with its tag and connections. `#route=\u003Cfrom-id>~\u003Cto-id>` highlights a whole path for flow questions.\n- **README**: one decision-log row per record (ID, decision, deciding force, cost accepted).\n\nArchify still validates `meta.views` but renders nothing from it; use the links above instead.\n\nWhen a decision changes: grill the map's Decisions branch for the new record (and any branch the change reopens), supersede the old record, edit the JSON of every diagram in `Affects` (tag, card item), rerun `finalize` for each, update the log row and deep link, and rebuild the page.\n\n## Presenting\n\nRun from the repo root after any change to the markdown or diagrams:\n\n```bash\nnode \u002Fhome\u002Fheynemann\u002F.omp\u002Fprofiles\u002Fdoordash\u002Fagent\u002Fskills\u002Fsystem-design-case\u002Fscripts\u002Fbuild-page.mjs cases\u002F\u003Cslug>\n```\n\nIt writes `cases\u002F\u003Cslug>\u002Findex.html` and rebuilds the hub `cases\u002Findex.html`, which lists every case; pass `cases` instead of `cases\u002F\u003Cslug>` to rebuild all of them. Open the hub as a local file, pick the case, and share that browser tab:\n\n- The narrative scrolls beside a pinned, fully interactive archify viewer (path tracing, lens, map, node details all work in place). On each decision it shows archify's focus on the anchor (superseded decisions are stamped historical); on each key flow it switches to that flow's sequence diagram. Each state loads once and keeps whatever you traced in it when you scroll back.\n- `F` (or Expand) opens the current state full-screen for deep-dive questions; Esc closes it. README links with `#route=…` open that path live in the panel.\n- The D-NN chips and `Ctrl\u002F⌘K` jump to any decision when the interviewer asks about it.\n- The README's \"Interview prep\" section is never rendered, so pitch notes and hard-question answers stay private.\n\n`build-page` warns when an `Affects` id is not a node in its diagram's archify JSON, since archify's focus then has nothing to show.\n\nThe page reads the template structure (`##` section names, the `**Status:**`\u002F`**Affects:**` line, the Options table with the chosen option in bold), so keep records in template shape for them to render.\n\n## Rehearsing\n\nPlay the interviewer with the `grilling` skill (what `\u002Fgrill-me` runs), aimed at the case: pitch, then each record's cost and revisit-when, then failure modes, then the map's branches the README answers thinnest. Write every answer that holds up back into its record or the README's hard-questions list.\n",{"name":5,"description":7},"main","e4d0a0940fd53fc8a3a1e1dcb967c0a18ea8ba0f","omp\u002F.omp\u002Fprofiles\u002Fdoordash\u002Fagent\u002Fskills\u002Fsystem-design-case","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow","https:\u002F\u002Fgithub.com\u002Fheynemann","http:\u002F\u002Fwww.thumbor.org","CTO @ Flutter Brazil | Former Meta & Coinbase","2026-10-29 20:46:15",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add heynemann\u002Fdotfiles-stow --skill system-design-case",{"tool":38,"command":39},"bunx","bunx skills add heynemann\u002Fdotfiles-stow --skill system-design-case",{"tool":41,"command":42},"pnpm","pnpm dlx skills add heynemann\u002Fdotfiles-stow --skill system-design-case","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Fdoordash\u002Fagent\u002Fskills\u002Fsystem-design-case\u002FSKILL.md",true,[46,52,58,62,66,70,74],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Finterview-map.md","REFERENCE","参考文档",4193,"https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Fdoordash\u002Fagent\u002Fskills\u002Fsystem-design-case\u002Freferences\u002Finterview-map.md",{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"scripts\u002Fbuild-page.mjs","SCRIPT","脚本",2965,"https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Fdoordash\u002Fagent\u002Fskills\u002Fsystem-design-case\u002Fscripts\u002Fbuild-page.mjs",{"path":59,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":60,"sourceHtmlUrl":61},"scripts\u002Fcase-data.mjs",7834,"https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Fdoordash\u002Fagent\u002Fskills\u002Fsystem-design-case\u002Fscripts\u002Fcase-data.mjs",{"path":63,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":64,"sourceHtmlUrl":65},"scripts\u002Findex-template.mjs",12662,"https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Fdoordash\u002Fagent\u002Fskills\u002Fsystem-design-case\u002Fscripts\u002Findex-template.mjs",{"path":67,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":68,"sourceHtmlUrl":69},"scripts\u002Fpage-template.mjs",67275,"https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Fdoordash\u002Fagent\u002Fskills\u002Fsystem-design-case\u002Fscripts\u002Fpage-template.mjs",{"path":71,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":72,"sourceHtmlUrl":73},"templates\u002Fcase.md",1984,"https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Fdoordash\u002Fagent\u002Fskills\u002Fsystem-design-case\u002Ftemplates\u002Fcase.md",{"path":75,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":76,"sourceHtmlUrl":77},"templates\u002Fdecision.md",590,"https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Fdoordash\u002Fagent\u002Fskills\u002Fsystem-design-case\u002Ftemplates\u002Fdecision.md",[79,86,93,100,107,114],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7FFA0PAN04C2DVK6A7CXK6K","unity-scriptableobjects","Architect Unity 6.3 LTS data and decoupling with ScriptableObjects: config\u002Fdata assets, shared runtime variables, event channels, and runtime sets\u002Fregistries. Use when designing data-driven systems, replacing singletons\u002Fmanagers, creating .asset data with CreateAssetMenu, or when the user mentions ScriptableObject, SO architecture, or data assets.","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Funity\u002Fskills-sh\u002F.agents\u002Fskills\u002Funity-scriptableobjects\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7FF9SPKA8BC4EGCHJGGJK5P","unity-package-management","Adds, removes, upgrades, and discovers Unity (UPM) packages from outside the Editor. Use for headless or CI package installs, verifying package IDs and versions, or choosing which packages a game needs. The Unity CLI doesn't manage packages.","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Funity\u002Fskills-sh\u002F.agents\u002Fskills\u002Funity-package-management\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7FF9KBCKR352R6ZSY2BB2J3","unity-input-system","Wire player input in Unity 6.3 LTS with the Input System package: Input Actions, action maps, the PlayerInput component, and reading values via callbacks or polling. Use when the project has a .inputactions asset or com.unity.inputsystem, or when the user mentions the Unity Input System, InputAction, action maps, PlayerInput, control schemes, or rebinding.","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Funity\u002Fskills-sh\u002F.agents\u002Fskills\u002Funity-input-system\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7FF9FREKNGB4PQP8ZHTN1D8","unity-ecs-patterns","Master Unity ECS (Entity Component System) with DOTS, Jobs, and Burst for high-performance game development. Use when building data-oriented games, optimizing performance, or working with large entity counts.","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Funity\u002Fskills-sh\u002F.agents\u002Fskills\u002Funity-ecs-patterns\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M7FF99B1DV7RDAY98QVFFMA9","unity-csharp-scripting","Write Unity 6.3 LTS C# gameplay scripts: the MonoBehaviour lifecycle (Awake\u002FOnEnable\u002FStart\u002FUpdate\u002FFixedUpdate\u002FLateUpdate), GameObject and component access, coroutines, and Inspector serialization. Use when creating or editing .cs scripts in a Unity project, or when the user mentions MonoBehaviour, Start\u002FUpdate, GetComponent, SerializeField, coroutines, or \"Unity script\".","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Funity\u002Fskills-sh\u002F.agents\u002Fskills\u002Funity-csharp-scripting\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":19},"01M7FF8ZK7PAPR4QZ44SY9ZDAJ","unity-cli","Controls the Unity Editor and projects from the command line, driving a running Editor to edit scenes and assets or run C#. Use when asked to install or manage Editors, licenses, or projects, set up version control, build, test, configure the Unity MCP server, or run any unity command.","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Funity\u002Fskills-sh\u002F.agents\u002Fskills\u002Funity-cli\u002FSKILL.md",[],[]]