[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F0GWR5FF5Q4CCYP1C4K244":3,"skill-same:01M7F0GWR5FF5Q4CCYP1C4K244":53},{"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":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7F0GWR5FF5Q4CCYP1C4K244","design-memory",null,"The .design-ops\u002F design memory contract — which files exist, the canonical style.json schema, which command owns which subtree, read order, and merge rules. Use whenever a command reads or writes .design-ops\u002F, or when design decisions from an earlier command must survive into a later one.","shotcowboystyle\u002Fag-skills","shotcowboystyle","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F62471?v=4","01M7EZTCFCZJ6K3MYW8BPM4X6R","Curtis Blanton","01M7EZTCG1S5M04J90A931X9BX",0,"MIT","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fdesign-memory\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: design-memory\ndescription: The .design-ops\u002F design memory contract — which files exist, the canonical style.json schema, which command owns which subtree, read order, and merge rules. Use whenever a command reads or writes .design-ops\u002F, or when design decisions from an earlier command must survive into a later one.\nallowed-tools: Read, Grep, Glob, Write, Edit\n---\n\n# Design Memory — the `.design-ops\u002F` contract\n\n`.design-ops\u002F` is what makes the commands compose. `\u002Fstyle` decides a visual direction\nonce; `\u002Fscreen`, `\u002Fcomponent`, `\u002Fpage`, `\u002Ffix` and a dozen others consume it\ninstead of re-inventing a palette every invocation.\n\nThat only works if every command agrees on the file shape. Until v4.1.0 none was\nwritten down, and four commands wrote `.design-ops\u002Fstyle.json` in four different\nshapes while other commands read whichever they assumed. This skill is the\nsingle definition.\n\n## Constants\n\nThe canonical `.design-ops\u002Fstyle.json`. Every writer emits this envelope; nobody\ninvents keys.\n\n```json\n{\n  \"$design_ops\": \"1\",\n  \"meta\": {\n    \"generated\": \"ISO-8601 timestamp\",\n    \"updatedBy\": [\"\u002Fstyle\"],\n    \"sector\": \"fintech\",\n    \"mood\": \"professional\",\n    \"platform\": \"web\"\n  },\n  \"project\": {\n    \"framework\": \"react | vue | svelte | vanilla | swiftui\",\n    \"styling\": \"tailwind | css | styled-components | swiftui\",\n    \"typescript\": true\n  },\n  \"tokens\": {\n    \"$schema\": \"https:\u002F\u002Fdesign-tokens.github.io\u002Fcommunity-group\u002Fformat\u002F\",\n    \"color\": {},\n    \"typography\": {},\n    \"space\": {},\n    \"radius\": {},\n    \"shadow\": {},\n    \"duration\": {},\n    \"easing\": {},\n    \"z\": {},\n    \"$themes\": { \"light\": {}, \"dark\": {} }\n  },\n  \"tone\": {\n    \"formality\": \"\",\n    \"traits\": [],\n    \"wordsToUse\": [],\n    \"wordsToAvoid\": []\n  },\n  \"references\": [{ \"app\": \"\", \"platform\": \"\", \"stealThis\": \"\", \"takeaway\": \"\" }]\n}\n```\n\nEverything under `tokens` is W3C DTCG. Everything outside it is Design Ops' own\nenvelope, because DTCG has no way to express a sector, a tone of voice, or a\nlist of reference apps.\n\n## The file set\n\n| File                                  | Written by                                        | Holds                                                                                                        |\n| ------------------------------------- | ------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |\n| `.design-ops\u002Fstyle.json`              | `\u002Fstyle`, `\u002Fpalette`, `\u002Ftype`, `\u002Ftokens`, `\u002Fdark` | the schema above                                                                                             |\n| `.design-ops\u002Fbrief.json`              | `\u002Fbrief`                                          | persona, HMW questions, constraints, success criteria                                                        |\n| `.design-ops\u002Fmap.json`                | `\u002Fmap`                                            | sitemap, screen inventory, content hierarchy                                                                 |\n| `.design-ops\u002Fvision.json`             | `\u002Fgrade`                                          | visual direction, designer-DNA match, score                                                                  |\n| `.design-ops\u002Fwireframe-\u003Cscreen>.json` | `\u002Fwireframe`                                      | layout structure, component map                                                                              |\n| `.design-ops\u002Fgenerated-\u003Casset>.json`  | `\u002Fgenerate`                                       | generation records, prompts, model, score                                                                    |\n| `.design-ops\u002Frefs\u002F`                   | `\u002Finspo`                                          | sourced references, captures, `board.json`. Schema in `reference-intelligence\u002Freferences\u002Fboard-synthesis.md` |\n| `.design-ops\u002Fscroll\u002F`                 | `\u002Fscroll`                                         | brief, subject truth, `plan.json`, `assets.json`, verify frames. Schema in `design-ops-file-schemas.md`      |\n| `.design-ops\u002Fdecisions.log`           | any command                                       | append-only NDJSON: `{ts, command, decision, reason, overrides}`                                             |\n\n## Ownership\n\nA writer touches its own subtree and nothing else. This is what allows four\ncommands to share one file without clobbering each other.\n\n| Command         | Owns                                                       |\n| --------------- | ---------------------------------------------------------- |\n| `\u002Fstyle`        | the whole file — it is the only command that may create it |\n| `\u002Fpalette`      | `tokens.color`                                             |\n| `\u002Ftype`         | `tokens.typography`                                        |\n| `\u002Ftokens`       | `tokens.*` (serialization only; it does not decide)        |\n| `\u002Fdark`         | `tokens.$themes.dark`                                      |\n| `\u002Finspo`        | `.design-ops\u002Frefs\u002F` only                                   |\n| `\u002Fscroll`       | `.design-ops\u002Fscroll\u002F`, and appends to the global `~\u002F.design-ops\u002Ffingerprints.ndjson` |\n| everything else | **read-only**                                              |\n\n## Read order\n\nBroad to specific. Later files override earlier ones where they overlap.\n\n1. `brief.json` — who it is for and what problem it solves\n2. `map.json` — what screens exist\n3. `refs\u002Fboard.json` — what the references say it should look like\n4. `style.json` — what it looks like (the decision; wins over the board)\n5. `vision.json` — the visual bar and DNA match\n6. `wireframe-\u003Cscreen>.json` — the layout of the screen actually in play\n7. `decisions.log` — the running override log; the last entry wins\n\n## Merge rules\n\n1. **Read-modify-write, never replace.** Load the file, deep-merge your subtree,\n   write it back. Append your command name to `meta.updatedBy` and refresh\n   `meta.generated`. A whole-file replacement destroys three other commands'\n   work and is the specific bug this contract exists to prevent.\n2. **Precedence: explicit user instruction > design memory > defaults.** An\n   instruction in the current turn wins immediately and appends to\n   `decisions.log` with its reason.\n3. **Absent is not empty.** No file means \"not decided yet\" — generate a value\n   and offer to persist it. A file present but partial means \"decided\" for the\n   sections that exist; fill only the gaps.\n4. **Never invent a token when `style.json` exists.** If the palette is on disk,\n   use it. Inventing a second palette mid-session is the most visible way to\n   break the illusion that the commands are one system.\n5. **Conflict: ask once.** If your write would change a value another command set\n   in a previous session, surface both values in one line and ask. Do not ask\n   twice in a session, and do not silently overwrite.\n\n## Routing\n\nFor **the full JSON Schema of every file**, worked merge examples, and the\nmigration note for pre-v4.1.0 files: read `references\u002Fdesign-ops-file-schemas.md`.\n\n## Cross-References\n\n- `design-systems-architecture` — the DTCG token tiers `tokens` serializes\n- `design-token-presets` — vetted starting token sets to seed `tokens` from\n- `design_ops-orchestrator` — pipelines that span several commands, which is when\n  design memory earns its keep\n","# Design Memory — the `.design-ops\u002F` contract\n\n`.design-ops\u002F` is what makes the commands compose. `\u002Fstyle` decides a visual direction\nonce; `\u002Fscreen`, `\u002Fcomponent`, `\u002Fpage`, `\u002Ffix` and a dozen others consume it\ninstead of re-inventing a palette every invocation.\n\nThat only works if every command agrees on the file shape. Until v4.1.0 none was\nwritten down, and four commands wrote `.design-ops\u002Fstyle.json` in four different\nshapes while other commands read whichever they assumed. This skill is the\nsingle definition.\n\n## Constants\n\nThe canonical `.design-ops\u002Fstyle.json`. Every writer emits this envelope; nobody\ninvents keys.\n\n```json\n{\n  \"$design_ops\": \"1\",\n  \"meta\": {\n    \"generated\": \"ISO-8601 timestamp\",\n    \"updatedBy\": [\"\u002Fstyle\"],\n    \"sector\": \"fintech\",\n    \"mood\": \"professional\",\n    \"platform\": \"web\"\n  },\n  \"project\": {\n    \"framework\": \"react | vue | svelte | vanilla | swiftui\",\n    \"styling\": \"tailwind | css | styled-components | swiftui\",\n    \"typescript\": true\n  },\n  \"tokens\": {\n    \"$schema\": \"https:\u002F\u002Fdesign-tokens.github.io\u002Fcommunity-group\u002Fformat\u002F\",\n    \"color\": {},\n    \"typography\": {},\n    \"space\": {},\n    \"radius\": {},\n    \"shadow\": {},\n    \"duration\": {},\n    \"easing\": {},\n    \"z\": {},\n    \"$themes\": { \"light\": {}, \"dark\": {} }\n  },\n  \"tone\": {\n    \"formality\": \"\",\n    \"traits\": [],\n    \"wordsToUse\": [],\n    \"wordsToAvoid\": []\n  },\n  \"references\": [{ \"app\": \"\", \"platform\": \"\", \"stealThis\": \"\", \"takeaway\": \"\" }]\n}\n```\n\nEverything under `tokens` is W3C DTCG. Everything outside it is Design Ops' own\nenvelope, because DTCG has no way to express a sector, a tone of voice, or a\nlist of reference apps.\n\n## The file set\n\n| File                                  | Written by                                        | Holds                                                                                                        |\n| ------------------------------------- | ------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |\n| `.design-ops\u002Fstyle.json`              | `\u002Fstyle`, `\u002Fpalette`, `\u002Ftype`, `\u002Ftokens`, `\u002Fdark` | the schema above                                                                                             |\n| `.design-ops\u002Fbrief.json`              | `\u002Fbrief`                                          | persona, HMW questions, constraints, success criteria                                                        |\n| `.design-ops\u002Fmap.json`                | `\u002Fmap`                                            | sitemap, screen inventory, content hierarchy                                                                 |\n| `.design-ops\u002Fvision.json`             | `\u002Fgrade`                                          | visual direction, designer-DNA match, score                                                                  |\n| `.design-ops\u002Fwireframe-\u003Cscreen>.json` | `\u002Fwireframe`                                      | layout structure, component map                                                                              |\n| `.design-ops\u002Fgenerated-\u003Casset>.json`  | `\u002Fgenerate`                                       | generation records, prompts, model, score                                                                    |\n| `.design-ops\u002Frefs\u002F`                   | `\u002Finspo`                                          | sourced references, captures, `board.json`. Schema in `reference-intelligence\u002Freferences\u002Fboard-synthesis.md` |\n| `.design-ops\u002Fscroll\u002F`                 | `\u002Fscroll`                                         | brief, subject truth, `plan.json`, `assets.json`, verify frames. Schema in `design-ops-file-schemas.md`      |\n| `.design-ops\u002Fdecisions.log`           | any command                                       | append-only NDJSON: `{ts, command, decision, reason, overrides}`                                             |\n\n## Ownership\n\nA writer touches its own subtree and nothing else. This is what allows four\ncommands to share one file without clobbering each other.\n\n| Command         | Owns                                                       |\n| --------------- | ---------------------------------------------------------- |\n| `\u002Fstyle`        | the whole file — it is the only command that may create it |\n| `\u002Fpalette`      | `tokens.color`                                             |\n| `\u002Ftype`         | `tokens.typography`                                        |\n| `\u002Ftokens`       | `tokens.*` (serialization only; it does not decide)        |\n| `\u002Fdark`         | `tokens.$themes.dark`                                      |\n| `\u002Finspo`        | `.design-ops\u002Frefs\u002F` only                                   |\n| `\u002Fscroll`       | `.design-ops\u002Fscroll\u002F`, and appends to the global `~\u002F.design-ops\u002Ffingerprints.ndjson` |\n| everything else | **read-only**                                              |\n\n## Read order\n\nBroad to specific. Later files override earlier ones where they overlap.\n\n1. `brief.json` — who it is for and what problem it solves\n2. `map.json` — what screens exist\n3. `refs\u002Fboard.json` — what the references say it should look like\n4. `style.json` — what it looks like (the decision; wins over the board)\n5. `vision.json` — the visual bar and DNA match\n6. `wireframe-\u003Cscreen>.json` — the layout of the screen actually in play\n7. `decisions.log` — the running override log; the last entry wins\n\n## Merge rules\n\n1. **Read-modify-write, never replace.** Load the file, deep-merge your subtree,\n   write it back. Append your command name to `meta.updatedBy` and refresh\n   `meta.generated`. A whole-file replacement destroys three other commands'\n   work and is the specific bug this contract exists to prevent.\n2. **Precedence: explicit user instruction > design memory > defaults.** An\n   instruction in the current turn wins immediately and appends to\n   `decisions.log` with its reason.\n3. **Absent is not empty.** No file means \"not decided yet\" — generate a value\n   and offer to persist it. A file present but partial means \"decided\" for the\n   sections that exist; fill only the gaps.\n4. **Never invent a token when `style.json` exists.** If the palette is on disk,\n   use it. Inventing a second palette mid-session is the most visible way to\n   break the illusion that the commands are one system.\n5. **Conflict: ask once.** If your write would change a value another command set\n   in a previous session, surface both values in one line and ask. Do not ask\n   twice in a session, and do not silently overwrite.\n\n## Routing\n\nFor **the full JSON Schema of every file**, worked merge examples, and the\nmigration note for pre-v4.1.0 files: read `references\u002Fdesign-ops-file-schemas.md`.\n\n## Cross-References\n\n- `design-systems-architecture` — the DTCG token tiers `tokens` serializes\n- `design-token-presets` — vetted starting token sets to seed `tokens` from\n- `design_ops-orchestrator` — pipelines that span several commands, which is when\n  design memory earns its keep\n",{"name":5,"description":7,"allowed-tools":24},"Read, Grep, Glob, Write, Edit","main","f846d9a97082ff30d613b55a085cef425d822473","plugins\u002Fdesign-ops\u002Fskills\u002Fdesign-memory","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle","https:\u002F\u002Fshotcowboystyle.github.io","Building smarter with AI, automation & modern tools. Exploring how far one person can go without a big team using today’s AI.","2026-11-10 04:58:27",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add shotcowboystyle\u002Fag-skills --skill design-memory",{"tool":39,"command":40},"bunx","bunx skills add shotcowboystyle\u002Fag-skills --skill design-memory",{"tool":42,"command":43},"pnpm","pnpm dlx skills add shotcowboystyle\u002Fag-skills --skill design-memory","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fdesign-memory\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fdesign-ops-file-schemas.md","REFERENCE","参考文档",10764,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fdesign-memory\u002Freferences\u002Fdesign-ops-file-schemas.md",[54,60,67,74,81,88],{"skillNo":55,"name":56,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7F1YRY5S5QRJ1V0BJS130QX","no-description","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fno-description\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7F1Y9BV2FJNQJ3NB32JS5CM","good-skill","Fixture skill that satisfies every rule.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fgood-skill\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7F1XXBQ3NQRXZSS0KAGAR9V","broken-link","Links to a reference file that does not exist.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbroken-link\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7F1XBX4R46NR9W0HXQ7XCDX","Bad_Name","Name violates the kebab-case rule and does not match the directory.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbad-name\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7F1WNAF8WNEQ7S5HKT5VK0D","skill-authoring","Write, review, and validate portable agent skills in SKILL.md format. Use when creating a new skill, editing an existing one, or asked whether a skill follows the Agent Skills spec.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fskills\u002Fskill-authoring\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7F1W30TC0XFNSF7YBRGETK2","weigh-bags","Record scale readings for each bag — empty (tare), outbound, current, final — and reconcile them against the itemised inventory to find unaccounted weight. Use when the user gives a bag weight, says how heavy something is, weighs their luggage, or asks how close to the limit they are. Appends to bags.yaml and runs scripts\u002Freconcile.py.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Ftravel-packing-assistant\u002Fskills\u002Fweigh-bags\u002FSKILL.md",[],[]]