[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CQKG3ECEXVZ4SWMHFWB6RK":3,"skill-same:01M7CQKG3ECEXVZ4SWMHFWB6RK":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":13,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7CQKG3ECEXVZ4SWMHFWB6RK","design-system",null,"Ratify a visual DESIGN.md. Use for a UI design system: colors, type, layout, and component tokens. 視覺設計系統 \u002F デザインシステム.","kouko\u002Floom-plugins","kouko","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1480254?v=4","01M7CQCPAJR9C92XDGR0QDCQ98","01M7CQCPB8FTVY1BT26ENK1YP4",0,"MIT","https:\u002F\u002Fgithub.com\u002Fkouko\u002Floom-plugins\u002Fblob\u002Fmain\u002Floom-design\u002Fskills\u002Fdesign-system\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: design-system\ndescription: |\n  Ratify a visual DESIGN.md. Use for a UI design system: colors, type, layout, and component tokens. 視覺設計系統 \u002F デザインシステム.\nversion: 1.0.0\n---\n\n## What this tool does\n\nRelative paths in this document are relative to this skill's own\ndirectory.\n\nDeliver local documents with actual absolute paths from the active worktree or\nexternal location, including in copyable instructions. For known local Markdown\nsupport, use the document's project-relative path as link text (external files:\nbasename) and absolute targets; otherwise show full absolute paths. Enclose\ntargets with spaces in angle brackets: `[doc.md](\u003C\u002Fworktree name\u002Fdoc.md>)`. Preserve bundled references, stored\nrelative paths, quoted examples and incidental filenames.\n\nThe user names a product with a UI. You run one short interview, write\n`DESIGN.md` at the consumer project's root, restate it, and — on \"yes\" —\nwrite the `ratified-by:` line. `DESIGN.md` documents the product's\n**visual system only** — brand, color, type, spacing, elevation, shape,\nand component tokens — never flows, screens, or navigation.\n\n## Step 1 — When to run\n\nWhen a visual-system choice depends on missing consequential evidence about\nusers or usage, identify that decision and use `loom-design:design-research`\nas needed. Reuse adequate evidence directly; return findings or uncertainty to\nthis task without changing confirmed preferences, scope or ratification authority.\n\nRun this **before or during `write-spec`**, for any product with a UI a\nuser reads or types into. `DESIGN.md` is **never required**: an absent or\nunratified `DESIGN.md` never blocks a change, at any station — unlike\n`PRINCIPLES.md`, there is no reject rule for it. Run it on request, or\nwhen `write-spec` surfaces that the UI has no governing visual system yet\nand the user wants one before drafting flows.\n\nRead `PRINCIPLES.md` at the consumer project's root first, when present,\nas the governing constraint every token must be defensible against. If it\nis absent, derive the direction from the user's own words in the interview\nbelow, say explicitly that the mood is derived rather than inherited, and\nproceed only on the user's say-so — never invent a constitution to satisfy\nthis step.\n\nBefore inventing any color, type, or component convention not derivable\nfrom `PRINCIPLES.md` or the user's own words, check\n`references\u002Fknowledge-triage.md` and classify the question first; never\nguess a domain-semantic default.\n\n## Step 2 — Interview → DESIGN.md\n\nAsk, in the user's own words:\n\n1. **Brand and mood** — a few adjectives for how the product should feel,\n   and one committed visual direction (e.g. \"editorial print weekly\" \u002F\n   \"utilitarian terminal\").\n2. **Palette** — the brand color(s), and whether dark mode matters.\n3. **Type** — an existing type choice, or a general character (serif \u002F\n   sans \u002F mono, tight \u002F generous).\n4. **Density and shape** — compact or spacious, sharp or rounded.\n\nEmit `DESIGN.md` at the consumer project's root (product-level, one per\nproduct — never per-feature), following `references\u002Fdesign-md-schema.md`\nfor the section shape and content. Its YAML token blocks use the token\ngroups **`scripts\u002Finterface\u002Fdesign_md_spec_keys.py`** freezes as the\nschema's source of truth — read `TOKEN_GROUPS` there for the exact set\nand do not retype it here; a value in this file that drifts from the\nscript's is a defect in this file, not the script. Verify WCAG-AA\ncontrast (body ≥ 4.5:1, large text ≥ 3:1) for every color pairing before\npresenting it; a failure is a blocker, not a note.\n\nThen check the file's structure before showing it to anyone, with\n`\u003Cloom-design>` standing for this plugin's own checkout:\n\n```\npython3 \u003Cloom-design>\u002Fscripts\u002Finterface\u002Fvalidate_design_output.py DESIGN.md\n```\n\nExit 0: go to step 3. Non-zero: fix what it names and run it again. Never\nread a `DESIGN.md` back to the user that has not exited 0 here — the\nrestatement is the user's only view of the file, so a structural defect\nthey cannot see is one they will ratify by accident.\n\n## Step 3 — Restate and ratify\n\nRead the whole file back to the user in plain words — the committed\ndirection, the palette, the type, the density — not a diff. On a\ncorrection, fix it and read back again. On \"yes\", write one line at the\ntop of the file, directly under the title:\n\n```\nratified-by: \u003Cname> \u003Cdate>\n```\n\n`\u003Cname>` is the user's own name or handle; `\u003Cdate>` is today,\n`YYYY-MM-DD`.\n\n## Step 4 — Commit\n\n```\ngit add DESIGN.md\ngit commit -m \"docs(loom): DESIGN.md ratified\"\n```\n\n## Downstream — how the rest of the flow uses it\n\n`write-spec` reads `DESIGN.md`, when present, for its UI-flow vocabulary —\nthe palette, component, and spacing tokens a flow's screens and states are\ndescribed against — so its `UI flows` section names things this file\nalready named, instead of inventing new visual vocabulary mid-spec. At\n`closing-review`, the `design-conformance` dimension scores the diff against\n`DESIGN.md`'s tokens; with no `DESIGN.md`, or a finding it cannot speak\nto, the dimension is scored **N\u002FA with a one-line reason**, never forced.\nA missing or unratified `DESIGN.md` never blocks any station.\n\n\u003C!-- gate: design-system.never-blocks -->\n**This tool never rejects a change for lacking a ratified `DESIGN.md`.**\nOnly `PRINCIPLES.md` carries a reject rule\n(`standing.product-principles-reject`); `DESIGN.md`'s absence is at most\na WARN the checker prints, never a gate any station enforces.\n","## What this tool does\n\nRelative paths in this document are relative to this skill's own\ndirectory.\n\nDeliver local documents with actual absolute paths from the active worktree or\nexternal location, including in copyable instructions. For known local Markdown\nsupport, use the document's project-relative path as link text (external files:\nbasename) and absolute targets; otherwise show full absolute paths. Enclose\ntargets with spaces in angle brackets: `[doc.md](\u003C\u002Fworktree name\u002Fdoc.md>)`. Preserve bundled references, stored\nrelative paths, quoted examples and incidental filenames.\n\nThe user names a product with a UI. You run one short interview, write\n`DESIGN.md` at the consumer project's root, restate it, and — on \"yes\" —\nwrite the `ratified-by:` line. `DESIGN.md` documents the product's\n**visual system only** — brand, color, type, spacing, elevation, shape,\nand component tokens — never flows, screens, or navigation.\n\n## Step 1 — When to run\n\nWhen a visual-system choice depends on missing consequential evidence about\nusers or usage, identify that decision and use `loom-design:design-research`\nas needed. Reuse adequate evidence directly; return findings or uncertainty to\nthis task without changing confirmed preferences, scope or ratification authority.\n\nRun this **before or during `write-spec`**, for any product with a UI a\nuser reads or types into. `DESIGN.md` is **never required**: an absent or\nunratified `DESIGN.md` never blocks a change, at any station — unlike\n`PRINCIPLES.md`, there is no reject rule for it. Run it on request, or\nwhen `write-spec` surfaces that the UI has no governing visual system yet\nand the user wants one before drafting flows.\n\nRead `PRINCIPLES.md` at the consumer project's root first, when present,\nas the governing constraint every token must be defensible against. If it\nis absent, derive the direction from the user's own words in the interview\nbelow, say explicitly that the mood is derived rather than inherited, and\nproceed only on the user's say-so — never invent a constitution to satisfy\nthis step.\n\nBefore inventing any color, type, or component convention not derivable\nfrom `PRINCIPLES.md` or the user's own words, check\n`references\u002Fknowledge-triage.md` and classify the question first; never\nguess a domain-semantic default.\n\n## Step 2 — Interview → DESIGN.md\n\nAsk, in the user's own words:\n\n1. **Brand and mood** — a few adjectives for how the product should feel,\n   and one committed visual direction (e.g. \"editorial print weekly\" \u002F\n   \"utilitarian terminal\").\n2. **Palette** — the brand color(s), and whether dark mode matters.\n3. **Type** — an existing type choice, or a general character (serif \u002F\n   sans \u002F mono, tight \u002F generous).\n4. **Density and shape** — compact or spacious, sharp or rounded.\n\nEmit `DESIGN.md` at the consumer project's root (product-level, one per\nproduct — never per-feature), following `references\u002Fdesign-md-schema.md`\nfor the section shape and content. Its YAML token blocks use the token\ngroups **`scripts\u002Finterface\u002Fdesign_md_spec_keys.py`** freezes as the\nschema's source of truth — read `TOKEN_GROUPS` there for the exact set\nand do not retype it here; a value in this file that drifts from the\nscript's is a defect in this file, not the script. Verify WCAG-AA\ncontrast (body ≥ 4.5:1, large text ≥ 3:1) for every color pairing before\npresenting it; a failure is a blocker, not a note.\n\nThen check the file's structure before showing it to anyone, with\n`\u003Cloom-design>` standing for this plugin's own checkout:\n\n```\npython3 \u003Cloom-design>\u002Fscripts\u002Finterface\u002Fvalidate_design_output.py DESIGN.md\n```\n\nExit 0: go to step 3. Non-zero: fix what it names and run it again. Never\nread a `DESIGN.md` back to the user that has not exited 0 here — the\nrestatement is the user's only view of the file, so a structural defect\nthey cannot see is one they will ratify by accident.\n\n## Step 3 — Restate and ratify\n\nRead the whole file back to the user in plain words — the committed\ndirection, the palette, the type, the density — not a diff. On a\ncorrection, fix it and read back again. On \"yes\", write one line at the\ntop of the file, directly under the title:\n\n```\nratified-by: \u003Cname> \u003Cdate>\n```\n\n`\u003Cname>` is the user's own name or handle; `\u003Cdate>` is today,\n`YYYY-MM-DD`.\n\n## Step 4 — Commit\n\n```\ngit add DESIGN.md\ngit commit -m \"docs(loom): DESIGN.md ratified\"\n```\n\n## Downstream — how the rest of the flow uses it\n\n`write-spec` reads `DESIGN.md`, when present, for its UI-flow vocabulary —\nthe palette, component, and spacing tokens a flow's screens and states are\ndescribed against — so its `UI flows` section names things this file\nalready named, instead of inventing new visual vocabulary mid-spec. At\n`closing-review`, the `design-conformance` dimension scores the diff against\n`DESIGN.md`'s tokens; with no `DESIGN.md`, or a finding it cannot speak\nto, the dimension is scored **N\u002FA with a one-line reason**, never forced.\nA missing or unratified `DESIGN.md` never blocks any station.\n\n\u003C!-- gate: design-system.never-blocks -->\n**This tool never rejects a change for lacking a ratified `DESIGN.md`.**\nOnly `PRINCIPLES.md` carries a reject rule\n(`standing.product-principles-reject`); `DESIGN.md`'s absence is at most\na WARN the checker prints, never a gate any station enforces.\n",{"name":5,"version":23,"description":24},"1.0.0","Ratify a visual DESIGN.md. Use for a UI design system: colors, type, layout, and component tokens. 視覺設計系統 \u002F デザインシステム.\n","main","3b1a9972644517911454530dc1876f88525b1f37","loom-design\u002Fskills\u002Fdesign-system","https:\u002F\u002Fgithub.com\u002Fkouko\u002Floom-plugins","https:\u002F\u002Fgithub.com\u002Fkouko","2026-11-15 00:45:02",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add kouko\u002Floom-plugins --skill design-system",{"tool":37,"command":38},"bunx","bunx skills add kouko\u002Floom-plugins --skill design-system",{"tool":40,"command":41},"pnpm","pnpm dlx skills add kouko\u002Floom-plugins --skill design-system","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkouko\u002Floom-plugins\u002Fblob\u002Fmain\u002Floom-design\u002Fskills\u002Fdesign-system\u002FSKILL.md",true,[45,51,55],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"README.md","REFERENCE","参考文档",1482,"https:\u002F\u002Fgithub.com\u002Fkouko\u002Floom-plugins\u002Fblob\u002Fmain\u002Floom-design\u002Fskills\u002Fdesign-system\u002FREADME.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fdesign-md-schema.md",17094,"https:\u002F\u002Fgithub.com\u002Fkouko\u002Floom-plugins\u002Fblob\u002Fmain\u002Floom-design\u002Fskills\u002Fdesign-system\u002Freferences\u002Fdesign-md-schema.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fknowledge-triage.md",5492,"https:\u002F\u002Fgithub.com\u002Fkouko\u002Floom-plugins\u002Fblob\u002Fmain\u002Floom-design\u002Fskills\u002Fdesign-system\u002Freferences\u002Fknowledge-triage.md",[60,67,74,81,88,95],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M7CQNVD2W5MP7PKX3MD0YSQE","using-loom-workflow","Route broad Loom workflow-tool requests to the right skill. Use when the request spans tools or the right workflow skill is unclear.","https:\u002F\u002Fgithub.com\u002Fkouko\u002Floom-plugins\u002Fblob\u002Fmain\u002Floom-workflow\u002Fskills\u002Fusing-loom-workflow\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M7CQNNTPVG52CS2C6Q9HJ2E2","skill-retro","Review selected past or current Claude Code or Codex sessions against readable target skill sources and related integration. Produce source-linked proposals without applying changes.","https:\u002F\u002Fgithub.com\u002Fkouko\u002Floom-plugins\u002Fblob\u002Fmain\u002Floom-workflow\u002Fskills\u002Fskill-retro\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M7CQNHR1BDKJ63CC4R1RY9GE","recap-state","Give an in-session recap of current progress for 'where were we', '我們剛剛在幹嘛', '剛剛講到哪', '我跟丟了', 'ちょっと振り返って', '今どこだっけ', or '振り返り'. The built-in \u002Frecap is an away-summary.","https:\u002F\u002Fgithub.com\u002Fkouko\u002Floom-plugins\u002Fblob\u002Fmain\u002Floom-workflow\u002Fskills\u002Frecap-state\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M7CQNE1A9272WPRE1MM3JRFK","project-retro","Review one current or specified coding session for source-backed project\ndevelopment improvements. Use for a requested retrospective, including\n振り返り seeking improvements; not for current-progress recaps or recurring skill mining.","https:\u002F\u002Fgithub.com\u002Fkouko\u002Floom-plugins\u002Fblob\u002Fmain\u002Floom-workflow\u002Fskills\u002Fproject-retro\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":18},"01M7CQNACJB36T0A039HT89P38","loom-visualization","Show comparisons, flows, decisions, states or reasoning chains as tables, ASCII or Mermaid in coding chat, including when a Loom station reports to the user (intent restatement, choices, acceptance test results); not Obsidian notes.","https:\u002F\u002Fgithub.com\u002Fkouko\u002Floom-plugins\u002Fblob\u002Fmain\u002Floom-workflow\u002Fskills\u002Floom-visualization\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":18},"01M7CQN7TVS0XF44JXQBWA32Z1","loom-memory","Record repo-wide lessons when saving to your own memory or asked to remember; recall, reconcile, or forget them when a task needs it.","https:\u002F\u002Fgithub.com\u002Fkouko\u002Floom-plugins\u002Fblob\u002Fmain\u002Floom-workflow\u002Fskills\u002Floom-memory\u002FSKILL.md",[],[]]