[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73BPCNDYT4DATQ8XZGAEVVB":3,"skill-same:01M73BPCNDYT4DATQ8XZGAEVVB":69},{"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":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":6,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M73BPCNDYT4DATQ8XZGAEVVB","design-foundation",null,"Style-neutral procedure for deriving a project's own design system. Walks a project from domain evidence to design principles, recorded design decisions, and a 3-layer token architecture (Primitive → Semantic ← [data-theme] → Component). Use when: establishing design principles for a new project, creating a project design guide (docs\u002Fdesign.md), setting up a design token system, or reviewing a project's design foundation completeness. Does NOT prescribe colors, fonts, spacing, or trends — those are project decisions.","5throck\u002Fai-workspace-standards","5throck","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10958964?v=4","01M73BFEH0V0VS483TW4JD49JW","01M73BFEJ5VQZJHJSFTVPAZGDM",25,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdesign-foundation\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: design-foundation\ndescription: >\n  Style-neutral procedure for deriving a project's own design system. Walks a\n  project from domain evidence to design principles, recorded design decisions,\n  and a 3-layer token architecture (Primitive → Semantic ← [data-theme] →\n  Component). Use when: establishing design principles for a new project,\n  creating a project design guide (docs\u002Fdesign.md), setting up a design token\n  system, or reviewing a project's design foundation completeness. Does NOT\n  prescribe colors, fonts, spacing, or trends — those are project decisions.\nversion: 1.1.1\nlast_reviewed: 2026-11-12\nstatus: active\nscope: common\nowner: design-system-lead\nprerequisites: none\nrelates_to:\n  - skill: ui-ux-design-intelligence\n    type: enables\n  - skill: token-usage-lint\n    type: composes_with\n  - skill: accessibility-audit\n    type: composes_with\nmetadata:\n  type: process\n  triggers:\n    - design foundation\n    - design principles\n    - design guide\n    - design tokens setup\n    - design decision record\n---\n\n# 🎨 Skill: design-foundation\n\n## Purpose\n\nDerive a **project-specific design system** through a traceable procedure. This skill is the\n*Procedure* layer of the Design Foundation framework:\n\n| Layer | Artifact |\n|-------|----------|\n| Specification (what to define) | `docs\u002Fdesign-foundation.md` (shipped inside a generated variant project's `docs\u002F`; does not exist at workspace root) |\n| Scaffold (how tokens are expressed) | `docs\u002Fdesign-tokens.template.css` |\n| **Procedure (this skill)** | How to derive and apply |\n| Project SSOT (what was chosen) | Project `docs\u002Fdesign.md` + token implementation |\n\n> **Foundation ≠ Design System.** Never copy values from another project (e.g. an existing\n> design system) unless the project explicitly decides to — and then record that as a decision\n> with rationale.\n\n## Procedure\n\n### Stage 1 — Domain Evidence\n\nRead the project's PRD\u002FSRS\u002Fcontext docs and user profiles. Produce an evidence list:\n\n- Information density needs (expert console vs consumer app)\n- Data criticality: are numbers\u002Ffigures core? Do they need provenance?\n- Audience and accessibility constraints (regulatory, language)\n- Workflow shape: freeform vs staged processes\n- Baseline viewport \u002F device context\n\n### Stage 2 — Design Principles\n\nFrom the evidence, derive **3–6 numbered principles**, each with its rationale\n(e.g. \"Expert Density — the domain requires dense but legible consoles\").\nOptionally add operating rules (P1–P6 style) for machine-checkable constraints.\n\n### Stage 3 — Design Decision Record\n\nCreate `docs\u002Fdesign.md` containing the `design_decisions` YAML block\n(see `docs\u002Fdesign-foundation.md` §4). Every selection — philosophy, color system,\ntypography (body\u002Fheading\u002Fnumeric, each value carrying the fallback stack contract),\nspacing, radius, motion, iconography (backed by a registered vocabulary) — MUST carry\na `rationale` tracing back to a principle. No arbitrary aesthetic choices.\n\nProvenance chain to preserve:\n\n```\nDomain Evidence → Design Principle → Design Decision → Token → Component\n```\n\n### Stage 4 — Token Architecture\n\nCopy `docs\u002Fdesign-tokens.template.css` into the project (e.g. `styles\u002Fdesign-tokens.css`) and fill\nevery `\u003Cvalue>` placeholder according to the decisions. Enforce the architecture:\n\n- Primitive (`--color-*`, fonts, spacing) — theme-neutral\n- Semantic (`--background`, `--border`, status bg\u002Ffg\u002Fborder triplets) — themed via\n  **`[data-theme=\"\u003Cname>\"]`** (default theme on `:root` + at least one alternate, typically dark)\n- Component (`--button-*`, `--card-*`, …) — reference semantics only; no layer bypass\n- If figures are domain-critical: numeric font role with `font-variant-numeric: tabular-nums`\n- If iconography is decided: activate the commented icon tokens\n  (`--icon-size`\u002F`--icon-stroke`\u002F`--icon-color`) and maintain the project's\n  machine-readable icon vocabulary registration\n\n### Stage 5 — Components\n\nBuild UI consuming component tokens only. Multi-encode status signals (color + icon + text);\n`aria-label` on every icon-only control; visible `:focus-visible` state. Reference\ncomponents only from the declared component inventory (`components.template.md`);\nnew components enter via the design-phase gate.\n\n### Stage 6 — Validation\n\nRun the Design Validation Contract (`docs\u002Fdesign-foundation.md` §7):\n\n- **[Required]** design.md with complete `design_decisions`; token implementation; default +\n  alternate theme; bg\u002Ffg\u002Fborder triplets; typography roles; icon library; icon vocabulary\n  declared; component inventory declared; WCAG AA declared; focus state; non-color state\n  encoding\n- **[Consistency]** no semantic-layer bypass; accessible labels on icon-only buttons;\n  tabular numerals in numeric UI; no hard-coded values in governed components;\n  icon tokens, where activated, resolve from the registered icon vocabulary\n\nUse `token-usage-lint` where available for hardcoded-value detection, and `accessibility-audit`\n(axe-core, WCAG 2.1 AA) for accessibility verification.\n\nReport the validation result in the project `docs\u002Fdesign.md` (or a linked validation section)\nbefore the design foundation is considered complete.\n\n## Boundaries\n\n- This skill does NOT select visual values for the project — it structures how the project decides.\n- For component-level design and implementation after tokens exist, hand off to\n  `ui-ux-design-intelligence` (this skill `precedes` it).\n- Projects are autonomous: they may diverge from the reference implementation as long as the\n  architecture (3 layers, `[data-theme]`, decision record) and validation contract hold.\n","# 🎨 Skill: design-foundation\n\n## Purpose\n\nDerive a **project-specific design system** through a traceable procedure. This skill is the\n*Procedure* layer of the Design Foundation framework:\n\n| Layer | Artifact |\n|-------|----------|\n| Specification (what to define) | `docs\u002Fdesign-foundation.md` (shipped inside a generated variant project's `docs\u002F`; does not exist at workspace root) |\n| Scaffold (how tokens are expressed) | `docs\u002Fdesign-tokens.template.css` |\n| **Procedure (this skill)** | How to derive and apply |\n| Project SSOT (what was chosen) | Project `docs\u002Fdesign.md` + token implementation |\n\n> **Foundation ≠ Design System.** Never copy values from another project (e.g. an existing\n> design system) unless the project explicitly decides to — and then record that as a decision\n> with rationale.\n\n## Procedure\n\n### Stage 1 — Domain Evidence\n\nRead the project's PRD\u002FSRS\u002Fcontext docs and user profiles. Produce an evidence list:\n\n- Information density needs (expert console vs consumer app)\n- Data criticality: are numbers\u002Ffigures core? Do they need provenance?\n- Audience and accessibility constraints (regulatory, language)\n- Workflow shape: freeform vs staged processes\n- Baseline viewport \u002F device context\n\n### Stage 2 — Design Principles\n\nFrom the evidence, derive **3–6 numbered principles**, each with its rationale\n(e.g. \"Expert Density — the domain requires dense but legible consoles\").\nOptionally add operating rules (P1–P6 style) for machine-checkable constraints.\n\n### Stage 3 — Design Decision Record\n\nCreate `docs\u002Fdesign.md` containing the `design_decisions` YAML block\n(see `docs\u002Fdesign-foundation.md` §4). Every selection — philosophy, color system,\ntypography (body\u002Fheading\u002Fnumeric, each value carrying the fallback stack contract),\nspacing, radius, motion, iconography (backed by a registered vocabulary) — MUST carry\na `rationale` tracing back to a principle. No arbitrary aesthetic choices.\n\nProvenance chain to preserve:\n\n```\nDomain Evidence → Design Principle → Design Decision → Token → Component\n```\n\n### Stage 4 — Token Architecture\n\nCopy `docs\u002Fdesign-tokens.template.css` into the project (e.g. `styles\u002Fdesign-tokens.css`) and fill\nevery `\u003Cvalue>` placeholder according to the decisions. Enforce the architecture:\n\n- Primitive (`--color-*`, fonts, spacing) — theme-neutral\n- Semantic (`--background`, `--border`, status bg\u002Ffg\u002Fborder triplets) — themed via\n  **`[data-theme=\"\u003Cname>\"]`** (default theme on `:root` + at least one alternate, typically dark)\n- Component (`--button-*`, `--card-*`, …) — reference semantics only; no layer bypass\n- If figures are domain-critical: numeric font role with `font-variant-numeric: tabular-nums`\n- If iconography is decided: activate the commented icon tokens\n  (`--icon-size`\u002F`--icon-stroke`\u002F`--icon-color`) and maintain the project's\n  machine-readable icon vocabulary registration\n\n### Stage 5 — Components\n\nBuild UI consuming component tokens only. Multi-encode status signals (color + icon + text);\n`aria-label` on every icon-only control; visible `:focus-visible` state. Reference\ncomponents only from the declared component inventory (`components.template.md`);\nnew components enter via the design-phase gate.\n\n### Stage 6 — Validation\n\nRun the Design Validation Contract (`docs\u002Fdesign-foundation.md` §7):\n\n- **[Required]** design.md with complete `design_decisions`; token implementation; default +\n  alternate theme; bg\u002Ffg\u002Fborder triplets; typography roles; icon library; icon vocabulary\n  declared; component inventory declared; WCAG AA declared; focus state; non-color state\n  encoding\n- **[Consistency]** no semantic-layer bypass; accessible labels on icon-only buttons;\n  tabular numerals in numeric UI; no hard-coded values in governed components;\n  icon tokens, where activated, resolve from the registered icon vocabulary\n\nUse `token-usage-lint` where available for hardcoded-value detection, and `accessibility-audit`\n(axe-core, WCAG 2.1 AA) for accessibility verification.\n\nReport the validation result in the project `docs\u002Fdesign.md` (or a linked validation section)\nbefore the design foundation is considered complete.\n\n## Boundaries\n\n- This skill does NOT select visual values for the project — it structures how the project decides.\n- For component-level design and implementation after tokens exist, hand off to\n  `ui-ux-design-intelligence` (this skill `precedes` it).\n- Projects are autonomous: they may diverge from the reference implementation as long as the\n  architecture (3 layers, `[data-theme]`, decision record) and validation contract hold.\n",{"name":5,"owner":23,"scope":24,"status":25,"version":26,"metadata":27,"relates_to":35,"description":44,"last_reviewed":45,"prerequisites":46},"design-system-lead","common","active","1.1.1",{"type":28,"triggers":29},"process",[30,31,32,33,34],"design foundation","design principles","design guide","design tokens setup","design decision record",[36,39,42],{"type":37,"skill":38},"enables","ui-ux-design-intelligence",{"type":40,"skill":41},"composes_with","token-usage-lint",{"type":40,"skill":43},"accessibility-audit","Style-neutral procedure for deriving a project's own design system. Walks a project from domain evidence to design principles, recorded design decisions, and a 3-layer token architecture (Primitive → Semantic ← [data-theme] → Component). Use when: establishing design principles for a new project, creating a project design guide (docs\u002Fdesign.md), setting up a design token system, or reviewing a project's design foundation completeness. Does NOT prescribe colors, fonts, spacing, or trends — those are project decisions.\n",1794441600000,"none","main","b57e612781a79b0e3e60878294ce59c86cc68e5d",".claude\u002Fskills\u002Fdesign-foundation",9,"https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards","https:\u002F\u002Fgithub.com\u002F5throck","Experienced in digital transformation, enterprise IT, startup acceleration, and business strategy. Focused on building practical systems that connect technolo","2026-11-14 21:22:34",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add 5throck\u002Fai-workspace-standards --skill design-foundation",{"tool":61,"command":62},"bunx","bunx skills add 5throck\u002Fai-workspace-standards --skill design-foundation",{"tool":64,"command":65},"pnpm","pnpm dlx skills add 5throck\u002Fai-workspace-standards --skill design-foundation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdesign-foundation\u002FSKILL.md",true,[],[70,78,83,88,93,98],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":77},"01M7BBJDYHJMGTJYSC37JVWY8S","i18n-layout","Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL\u002Fbidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF\u002FBOM issues surface.","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":79,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":77},"01M7BBJ9XHAAS1AVGKZZ841VBZ","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.hermes\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":84,"name":72,"nameZh":6,"description":73,"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":77},"01M7BBJ5C3X8TKFKG5R9P9P49W","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.gemini\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":89,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":77},"01M7BBJ1B52X0QMJ2QVBMPJB37","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.codex\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":94,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":77},"01M7BBHX91BW2Q2R276MRX5AW3","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.claude\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":99,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":77},"01M7BBHQWGXPSFRWN1PRC2NMMV","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.agents\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[]]