[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7313G15KBHBJVP5ZDP7CVKP":3,"skill-same:01M7313G15KBHBJVP5ZDP7CVKP":75},{"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":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":52,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":54,"install":55,"resources":68},"01M7313G15KBHBJVP5ZDP7CVKP","design-md",null,"Author\u002Fvalidate\u002Fexport Google's DESIGN.md token spec files.","StarryCod\u002Fcogitum","StarryCod","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F200964623?v=4","01M7311AM3RY259SYKGHWBEDN0","OpenReason","01M7311AMRC1PBSTYZWSD1AQFJ",12,"MIT","https:\u002F\u002Fgithub.com\u002FStarryCod\u002Fcogitum\u002Fblob\u002Fmaster\u002Fcogitum\u002Fdata\u002Fskills\u002Fcreative\u002Fdesign-md\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: design-md\ndescription: Author\u002Fvalidate\u002Fexport Google's DESIGN.md token spec files.\nversion: 1.0.0\nauthor: Cogitum\nlicense: MIT\nplatforms: [linux, macos, windows]\nmetadata:\n  cogitum:\n    tags: [design, design-system, tokens, ui, accessibility, wcag, tailwind, dtcg, google]\n    related_skills: [popular-web-designs, claude-design, excalidraw, architecture-diagram]\n---\n\n# DESIGN.md Skill\n\nDESIGN.md is Google's open spec (Apache-2.0, `google-labs-code\u002Fdesign.md`) for\ndescribing a visual identity to coding agents. One file combines:\n\n- **YAML front matter** — machine-readable design tokens (normative values)\n- **Markdown body** — human-readable rationale, organized into canonical sections\n\nTokens give exact values. Prose tells agents *why* those values exist and how to\napply them. The CLI (`npx @google\u002Fdesign.md`) lints structure + WCAG contrast,\ndiffs versions for regressions, and exports to Tailwind or W3C DTCG JSON.\n\n## When to use this skill\n\n- User asks for a DESIGN.md file, design tokens, or a design system spec\n- User wants consistent UI\u002Fbrand across multiple projects or tools\n- User pastes an existing DESIGN.md and asks to lint, diff, export, or extend it\n- User asks to port a style guide into a format agents can consume\n- User wants contrast \u002F WCAG accessibility validation on their color palette\n\nFor purely visual inspiration or layout examples, use `popular-web-designs`\ninstead. For *process and taste* when designing a one-off HTML artifact\nfrom scratch (prototype, deck, landing page, component lab), use\n`claude-design`. This skill is for the *formal spec file* itself.\n\n## File anatomy\n\n```md\n---\nversion: alpha\nname: Heritage\ndescription: Architectural minimalism meets journalistic gravitas.\ncolors:\n  primary: \"#1A1C1E\"\n  secondary: \"#6C7278\"\n  tertiary: \"#B8422E\"\n  neutral: \"#F7F5F2\"\ntypography:\n  h1:\n    fontFamily: Public Sans\n    fontSize: 3rem\n    fontWeight: 700\n    lineHeight: 1.1\n    letterSpacing: \"-0.02em\"\n  body-md:\n    fontFamily: Public Sans\n    fontSize: 1rem\nrounded:\n  sm: 4px\n  md: 8px\n  lg: 16px\nspacing:\n  sm: 8px\n  md: 16px\n  lg: 24px\ncomponents:\n  button-primary:\n    backgroundColor: \"{colors.tertiary}\"\n    textColor: \"#FFFFFF\"\n    rounded: \"{rounded.sm}\"\n    padding: 12px\n  button-primary-hover:\n    backgroundColor: \"{colors.primary}\"\n---\n\n## Overview\n\nArchitectural Minimalism meets Journalistic Gravitas...\n\n## Colors\n\n- **Primary (#1A1C1E):** Deep ink for headlines and core text.\n- **Tertiary (#B8422E):** \"Boston Clay\" — the sole driver for interaction.\n\n## Typography\n\nPublic Sans for everything except small all-caps labels...\n\n## Components\n\n`button-primary` is the only high-emphasis action on a page...\n```\n\n## Token types\n\n| Type | Format | Example |\n|------|--------|---------|\n| Color | `#` + hex (sRGB) | `\"#1A1C1E\"` |\n| Dimension | number + unit (`px`, `em`, `rem`) | `48px`, `-0.02em` |\n| Token reference | `{path.to.token}` | `{colors.primary}` |\n| Typography | object with `fontFamily`, `fontSize`, `fontWeight`, `lineHeight`, `letterSpacing`, `fontFeature`, `fontVariation` | see above |\n\nComponent property whitelist: `backgroundColor`, `textColor`, `typography`,\n`rounded`, `padding`, `size`, `height`, `width`. Variants (hover, active,\npressed) are **separate component entries** with related key names\n(`button-primary-hover`), not nested.\n\n## Canonical section order\n\nSections are optional, but present ones MUST appear in this order. Duplicate\nheadings reject the file.\n\n1. Overview (alias: Brand & Style)\n2. Colors\n3. Typography\n4. Layout (alias: Layout & Spacing)\n5. Elevation & Depth (alias: Elevation)\n6. Shapes\n7. Components\n8. Do's and Don'ts\n\nUnknown sections are preserved, not errored. Unknown token names are accepted\nif the value type is valid. Unknown component properties produce a warning.\n\n## Workflow: authoring a new DESIGN.md\n\n1. **Ask the user** (or infer) the brand tone, accent color, and typography\n   direction. If they provided a site, image, or vibe, translate it to the\n   token shape above.\n2. **Write `DESIGN.md`** in their project root using `write_file`. Always\n   include `name:` and `colors:`; other sections optional but encouraged.\n3. **Use token references** (`{colors.primary}`) in the `components:` section\n   instead of re-typing hex values. Keeps the palette single-source.\n4. **Lint it** (see below). Fix any broken references or WCAG failures\n   before returning.\n5. **If the user has an existing project**, also write Tailwind or DTCG\n   exports next to the file (`tailwind.theme.json`, `tokens.json`).\n\n## Workflow: lint \u002F diff \u002F export\n\nThe CLI is `@google\u002Fdesign.md` (Node). Use `npx` — no global install needed.\n\n```bash\n# Validate structure + token references + WCAG contrast\nnpx -y @google\u002Fdesign.md lint DESIGN.md\n\n# Compare two versions, fail on regression (exit 1 = regression)\nnpx -y @google\u002Fdesign.md diff DESIGN.md DESIGN-v2.md\n\n# Export to Tailwind theme JSON\nnpx -y @google\u002Fdesign.md export --format tailwind DESIGN.md > tailwind.theme.json\n\n# Export to W3C DTCG (Design Tokens Format Module) JSON\nnpx -y @google\u002Fdesign.md export --format dtcg DESIGN.md > tokens.json\n\n# Print the spec itself — useful when injecting into an agent prompt\nnpx -y @google\u002Fdesign.md spec --rules-only --format json\n```\n\nAll commands accept `-` for stdin. `lint` returns exit 1 on errors. Use the\n`--format json` flag and parse the output if you need to report findings\nstructurally.\n\n### Lint rule reference (what the 7 rules catch)\n\n- `broken-ref` (error) — `{colors.missing}` points at a non-existent token\n- `duplicate-section` (error) — same `## Heading` appears twice\n- `invalid-color`, `invalid-dimension`, `invalid-typography` (error)\n- `wcag-contrast` (warning\u002Finfo) — component `textColor` vs `backgroundColor`\n  ratio against WCAG AA (4.5:1) and AAA (7:1)\n- `unknown-component-property` (warning) — outside the whitelist above\n\nWhen the user cares about accessibility, call this out explicitly in your\nsummary — WCAG findings are the most load-bearing reason to use the CLI.\n\n## Pitfalls\n\n- **Don't nest component variants.** `button-primary.hover` is wrong;\n  `button-primary-hover` as a sibling key is right.\n- **Hex colors must be quoted strings.** YAML will otherwise choke on `#` or\n  truncate values like `#1A1C1E` oddly.\n- **Negative dimensions need quotes too.** `letterSpacing: -0.02em` parses as\n  a YAML flow — write `letterSpacing: \"-0.02em\"`.\n- **Section order is enforced.** If the user gives you prose in a random order,\n  reorder it to match the canonical list before saving.\n- **`version: alpha` is the current spec version** (as of Apr 2026). The spec\n  is marked alpha — watch for breaking changes.\n- **Token references resolve by dotted path.** `{colors.primary}` works;\n  `{primary}` does not.\n\n## Spec source of truth\n\n- Repo: https:\u002F\u002Fgithub.com\u002Fgoogle-labs-code\u002Fdesign.md (Apache-2.0)\n- CLI: `@google\u002Fdesign.md` on npm\n- License of generated DESIGN.md files: whatever the user's project uses;\n  the spec itself is Apache-2.0.\n","# DESIGN.md Skill\n\nDESIGN.md is Google's open spec (Apache-2.0, `google-labs-code\u002Fdesign.md`) for\ndescribing a visual identity to coding agents. One file combines:\n\n- **YAML front matter** — machine-readable design tokens (normative values)\n- **Markdown body** — human-readable rationale, organized into canonical sections\n\nTokens give exact values. Prose tells agents *why* those values exist and how to\napply them. The CLI (`npx @google\u002Fdesign.md`) lints structure + WCAG contrast,\ndiffs versions for regressions, and exports to Tailwind or W3C DTCG JSON.\n\n## When to use this skill\n\n- User asks for a DESIGN.md file, design tokens, or a design system spec\n- User wants consistent UI\u002Fbrand across multiple projects or tools\n- User pastes an existing DESIGN.md and asks to lint, diff, export, or extend it\n- User asks to port a style guide into a format agents can consume\n- User wants contrast \u002F WCAG accessibility validation on their color palette\n\nFor purely visual inspiration or layout examples, use `popular-web-designs`\ninstead. For *process and taste* when designing a one-off HTML artifact\nfrom scratch (prototype, deck, landing page, component lab), use\n`claude-design`. This skill is for the *formal spec file* itself.\n\n## File anatomy\n\n```md\n---\nversion: alpha\nname: Heritage\ndescription: Architectural minimalism meets journalistic gravitas.\ncolors:\n  primary: \"#1A1C1E\"\n  secondary: \"#6C7278\"\n  tertiary: \"#B8422E\"\n  neutral: \"#F7F5F2\"\ntypography:\n  h1:\n    fontFamily: Public Sans\n    fontSize: 3rem\n    fontWeight: 700\n    lineHeight: 1.1\n    letterSpacing: \"-0.02em\"\n  body-md:\n    fontFamily: Public Sans\n    fontSize: 1rem\nrounded:\n  sm: 4px\n  md: 8px\n  lg: 16px\nspacing:\n  sm: 8px\n  md: 16px\n  lg: 24px\ncomponents:\n  button-primary:\n    backgroundColor: \"{colors.tertiary}\"\n    textColor: \"#FFFFFF\"\n    rounded: \"{rounded.sm}\"\n    padding: 12px\n  button-primary-hover:\n    backgroundColor: \"{colors.primary}\"\n---\n\n## Overview\n\nArchitectural Minimalism meets Journalistic Gravitas...\n\n## Colors\n\n- **Primary (#1A1C1E):** Deep ink for headlines and core text.\n- **Tertiary (#B8422E):** \"Boston Clay\" — the sole driver for interaction.\n\n## Typography\n\nPublic Sans for everything except small all-caps labels...\n\n## Components\n\n`button-primary` is the only high-emphasis action on a page...\n```\n\n## Token types\n\n| Type | Format | Example |\n|------|--------|---------|\n| Color | `#` + hex (sRGB) | `\"#1A1C1E\"` |\n| Dimension | number + unit (`px`, `em`, `rem`) | `48px`, `-0.02em` |\n| Token reference | `{path.to.token}` | `{colors.primary}` |\n| Typography | object with `fontFamily`, `fontSize`, `fontWeight`, `lineHeight`, `letterSpacing`, `fontFeature`, `fontVariation` | see above |\n\nComponent property whitelist: `backgroundColor`, `textColor`, `typography`,\n`rounded`, `padding`, `size`, `height`, `width`. Variants (hover, active,\npressed) are **separate component entries** with related key names\n(`button-primary-hover`), not nested.\n\n## Canonical section order\n\nSections are optional, but present ones MUST appear in this order. Duplicate\nheadings reject the file.\n\n1. Overview (alias: Brand & Style)\n2. Colors\n3. Typography\n4. Layout (alias: Layout & Spacing)\n5. Elevation & Depth (alias: Elevation)\n6. Shapes\n7. Components\n8. Do's and Don'ts\n\nUnknown sections are preserved, not errored. Unknown token names are accepted\nif the value type is valid. Unknown component properties produce a warning.\n\n## Workflow: authoring a new DESIGN.md\n\n1. **Ask the user** (or infer) the brand tone, accent color, and typography\n   direction. If they provided a site, image, or vibe, translate it to the\n   token shape above.\n2. **Write `DESIGN.md`** in their project root using `write_file`. Always\n   include `name:` and `colors:`; other sections optional but encouraged.\n3. **Use token references** (`{colors.primary}`) in the `components:` section\n   instead of re-typing hex values. Keeps the palette single-source.\n4. **Lint it** (see below). Fix any broken references or WCAG failures\n   before returning.\n5. **If the user has an existing project**, also write Tailwind or DTCG\n   exports next to the file (`tailwind.theme.json`, `tokens.json`).\n\n## Workflow: lint \u002F diff \u002F export\n\nThe CLI is `@google\u002Fdesign.md` (Node). Use `npx` — no global install needed.\n\n```bash\n# Validate structure + token references + WCAG contrast\nnpx -y @google\u002Fdesign.md lint DESIGN.md\n\n# Compare two versions, fail on regression (exit 1 = regression)\nnpx -y @google\u002Fdesign.md diff DESIGN.md DESIGN-v2.md\n\n# Export to Tailwind theme JSON\nnpx -y @google\u002Fdesign.md export --format tailwind DESIGN.md > tailwind.theme.json\n\n# Export to W3C DTCG (Design Tokens Format Module) JSON\nnpx -y @google\u002Fdesign.md export --format dtcg DESIGN.md > tokens.json\n\n# Print the spec itself — useful when injecting into an agent prompt\nnpx -y @google\u002Fdesign.md spec --rules-only --format json\n```\n\nAll commands accept `-` for stdin. `lint` returns exit 1 on errors. Use the\n`--format json` flag and parse the output if you need to report findings\nstructurally.\n\n### Lint rule reference (what the 7 rules catch)\n\n- `broken-ref` (error) — `{colors.missing}` points at a non-existent token\n- `duplicate-section` (error) — same `## Heading` appears twice\n- `invalid-color`, `invalid-dimension`, `invalid-typography` (error)\n- `wcag-contrast` (warning\u002Finfo) — component `textColor` vs `backgroundColor`\n  ratio against WCAG AA (4.5:1) and AAA (7:1)\n- `unknown-component-property` (warning) — outside the whitelist above\n\nWhen the user cares about accessibility, call this out explicitly in your\nsummary — WCAG findings are the most load-bearing reason to use the CLI.\n\n## Pitfalls\n\n- **Don't nest component variants.** `button-primary.hover` is wrong;\n  `button-primary-hover` as a sibling key is right.\n- **Hex colors must be quoted strings.** YAML will otherwise choke on `#` or\n  truncate values like `#1A1C1E` oddly.\n- **Negative dimensions need quotes too.** `letterSpacing: -0.02em` parses as\n  a YAML flow — write `letterSpacing: \"-0.02em\"`.\n- **Section order is enforced.** If the user gives you prose in a random order,\n  reorder it to match the canonical list before saving.\n- **`version: alpha` is the current spec version** (as of Apr 2026). The spec\n  is marked alpha — watch for breaking changes.\n- **Token references resolve by dotted path.** `{colors.primary}` works;\n  `{primary}` does not.\n\n## Spec source of truth\n\n- Repo: https:\u002F\u002Fgithub.com\u002Fgoogle-labs-code\u002Fdesign.md (Apache-2.0)\n- CLI: `@google\u002Fdesign.md` on npm\n- License of generated DESIGN.md files: whatever the user's project uses;\n  the spec itself is Apache-2.0.\n",{"name":5,"author":24,"license":15,"version":25,"metadata":26,"platforms":43,"description":7},"Cogitum","1.0.0",{"cogitum":27},{"tags":28,"related_skills":38},[29,30,31,32,33,34,35,36,37],"design","design-system","tokens","ui","accessibility","wcag","tailwind","dtcg","google",[39,40,41,42],"popular-web-designs","claude-design","excalidraw","architecture-diagram",[44,45,46],"linux","macos","windows","master","a99de210a5d82a24b7aa5020afa1f904f595d14c","cogitum\u002Fdata\u002Fskills\u002Fcreative\u002Fdesign-md",0,"https:\u002F\u002Fgithub.com\u002FStarryCod\u002Fcogitum","https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fcogitum","https:\u002F\u002Fgithub.com\u002FStarryCod","2026-05-25 23:49:07",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add StarryCod\u002Fcogitum --skill design-md",{"tool":61,"command":62},"bunx","bunx skills add StarryCod\u002Fcogitum --skill design-md",{"tool":64,"command":65},"pnpm","pnpm dlx skills add StarryCod\u002Fcogitum --skill design-md","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FStarryCod\u002Fcogitum\u002Fblob\u002Fmaster\u002Fcogitum\u002Fdata\u002Fskills\u002Fcreative\u002Fdesign-md\u002FSKILL.md",true,[69],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"templates\u002Fstarter.md","REFERENCE","参考文档",2566,"https:\u002F\u002Fgithub.com\u002FStarryCod\u002Fcogitum\u002Fblob\u002Fmaster\u002Fcogitum\u002Fdata\u002Fskills\u002Fcreative\u002Fdesign-md\u002Ftemplates\u002Fstarter.md",[76,83,90,97,104,111],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M731AYJQFFAGEQ8T8NMPKM72","yuanbao","Yuanbao (元宝) groups: @mention users, query info\u002Fmembers.","https:\u002F\u002Fgithub.com\u002FStarryCod\u002Fcogitum\u002Fblob\u002Fmaster\u002Fcogitum\u002Fdata\u002Fskills\u002Fyuanbao\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M731AWAHBZQ4JG5HBRXSTEWP","tg-moderator","Telegram chat moderator\u002Fcompanion mode. No tools, conversational only.","https:\u002F\u002Fgithub.com\u002FStarryCod\u002Fcogitum\u002Fblob\u002Fmaster\u002Fcogitum\u002Fdata\u002Fskills\u002Ftg-moderator\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M731AS9N89S2E50MSW2Y9QYY","writing-plans","Write implementation plans: bite-sized tasks, paths, code.","https:\u002F\u002Fgithub.com\u002FStarryCod\u002Fcogitum\u002Fblob\u002Fmaster\u002Fcogitum\u002Fdata\u002Fskills\u002Fsoftware-development\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M731ANESTYGBFV3XSAT0AS8Q","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002FStarryCod\u002Fcogitum\u002Fblob\u002Fmaster\u002Fcogitum\u002Fdata\u002Fskills\u002Fsoftware-development\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"01M731AG1KE7ZHM0P1R890ZVB0","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002FStarryCod\u002Fcogitum\u002Fblob\u002Fmaster\u002Fcogitum\u002Fdata\u002Fskills\u002Fsoftware-development\u002Fsystematic-debugging\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":19},"01M731ABWQ3DTCBY8E6WTYSBTT","subagent-driven-development","Execute plans via delegate_task subagents (2-stage review).","https:\u002F\u002Fgithub.com\u002FStarryCod\u002Fcogitum\u002Fblob\u002Fmaster\u002Fcogitum\u002Fdata\u002Fskills\u002Fsoftware-development\u002Fsubagent-driven-development\u002FSKILL.md",[],[]]