[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F0H8BEQJWNMYSD0PPD61WT":3,"skill-same:01M7F0H8BEQJWNMYSD0PPD61WT":73},{"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},"01M7F0H8BEQJWNMYSD0PPD61WT","design-systems-architecture",null,"Design system architecture: W3C design tokens, Style Dictionary pipelines, component library structure, theming, multi-brand token tiers, governance, versioning, and maturity models. Use when starting or scaling a design system, generating tokens, or setting up design-to-code distribution.","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-systems-architecture\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: design-systems-architecture\ndescription: \"Design system architecture: W3C design tokens, Style Dictionary pipelines, component library structure, theming, multi-brand token tiers, governance, versioning, and maturity models. Use when starting or scaling a design system, generating tokens, or setting up design-to-code distribution.\"\nallowed-tools: Read, Grep, Glob\n---\n\n# Design Systems Architecture\n\n\"A design system is not a project. It is a product serving products.\" — Nathan Curtis\n\nThe system is the single source of truth for how a product family looks, behaves, and communicates: opinionated enough for coherence, flexible enough for diverse products.\n\n## Core Principles\n\n1. **Systematic over stylistic** — define rules and relationships, not just visual recipes\n2. **Tokens are the foundation** — design decisions encoded as data, not hardcoded values\n3. **Composition over inheritance** — build complex components from simple, composable primitives\n4. **Document the why** — every decision needs rationale to prevent future erosion\n5. **Adopt, then adapt** — products adopt the system by default, request exceptions with justification\n\n## Token Architecture\n\nThree tiers; each tier references only the tier below:\n\n| Tier | Purpose | Example |\n|---|---|---|\n| 1 Global \u002F primitive | The full value palette | `color.blue.500 = #3b82f6` |\n| 2 Semantic \u002F alias | Design intent | `color.action.primary = {color.blue.500}` |\n| 3 Component | Where a value is used | `button.primary.bg = {color.action.primary}` |\n\nFollow the W3C DTCG format: `$value`, `$type` (color, dimension, fontFamily, fontWeight, duration, cubicBezier, shadow), `$description`, `{}` references, `.tokens.json` files. Categories: color, spacing, typography, radius, elevation, duration, easing, sizing, opacity, z-index.\n\n## Components\n\n- **Anatomy:** props\u002FAPI, variants, states (default, hover, active, focused, disabled, loading, error), slots, token bindings, accessibility, documentation.\n- **Maturity:** Defined → Implemented → Tested → Documented → Governed.\n- **API rules:** consistent prop names, enums over booleans, composition over configuration, sensible defaults, full TypeScript types, forwarded refs, polymorphic `as`.\n\n## Theming\n\nCSS custom properties are the runtime mechanism: swap values at the root, honor `prefers-color-scheme`, allow a persisted manual override. Component tokens reference semantic tokens, which resolve per theme. Multi-brand: shared behavior and accessibility, per-brand token sets, a component override layer only when tokens are not enough, and a Brand x Mode theme matrix.\n\n## Governance\n\nHybrid contribution is the default: the core team owns primitives (Button, Input, Card) and governance; domain teams contribute domain components (DataGrid, FileUploader) under core review. Changes go RFC → design, code, and accessibility review → build with tests → document → release. Version with SemVer (MAJOR = breaking API or visual change); keep deprecations for 2 major versions with warnings and migration guidance.\n\n## Design-to-Code\n\nFigma component names match code names exactly, and variants map to props. Tokens flow Figma → `tokens.json` → code through CI (Style Dictionary) into CSS variables, Swift, Android XML, React Native, and TypeScript types. Run visual regression against the Figma source.\n\n## Routing\n\n| Question | Read |\n|---|---|\n| Three-tier model with JSON examples, DTCG naming, token categories, the 2025 spec update | `references\u002Fdesign-token-architecture.md` |\n| DTCG spec detail, full `$type` reference, Style Dictionary config, Token Studio, token CI\u002FCD, the October 2025 stable release | `references\u002Ftoken-specification-guide.md` |\n| Aliasing, multi-theme tokens, transformation pipeline, platform outputs, token docs, versioning, testing | `references\u002Fdesign-token-implementation.md` |\n| Component anatomy, maturity levels, API principles, theme JSON, multi-brand layering, Figma-to-code sync | `references\u002Fcomponent-library-theming.md` |\n| Team models, contribution workflow, RFC and proposal templates, lifecycle, versioning, docs, adoption metrics | `references\u002Fgovernance-scaling.md` |\n| Five-level maturity model, assessment rubric, multi-brand tokens, white-label, migration, ROI, `$extensions` | `references\u002Fmaturity-model-multi-brand.md` |\n\n## Cross-Referencing\n\n- Visual design principles: `visual-design-mastery`\n- Accessibility component requirements: `accessibility-inclusive-design`\n- Motion tokens and animation: `interaction-motion-design`\n- Mobile component adaptations: `mobile-ux-design`\n- Figma MCP design-to-code flywheel: `figma-design-tool-workflows`\n- CSS `@layer` cascade for token architecture: `component-patterns-code`\n\n## Key Sources\n\n- Curtis, N. \"Design Systems\" and Modular Web Design\n- W3C Design Tokens Community Group specification\n- Figma design systems documentation\n- Material Design component guidelines\n- Brad Frost \"Atomic Design\" methodology\n","# Design Systems Architecture\n\n\"A design system is not a project. It is a product serving products.\" — Nathan Curtis\n\nThe system is the single source of truth for how a product family looks, behaves, and communicates: opinionated enough for coherence, flexible enough for diverse products.\n\n## Core Principles\n\n1. **Systematic over stylistic** — define rules and relationships, not just visual recipes\n2. **Tokens are the foundation** — design decisions encoded as data, not hardcoded values\n3. **Composition over inheritance** — build complex components from simple, composable primitives\n4. **Document the why** — every decision needs rationale to prevent future erosion\n5. **Adopt, then adapt** — products adopt the system by default, request exceptions with justification\n\n## Token Architecture\n\nThree tiers; each tier references only the tier below:\n\n| Tier | Purpose | Example |\n|---|---|---|\n| 1 Global \u002F primitive | The full value palette | `color.blue.500 = #3b82f6` |\n| 2 Semantic \u002F alias | Design intent | `color.action.primary = {color.blue.500}` |\n| 3 Component | Where a value is used | `button.primary.bg = {color.action.primary}` |\n\nFollow the W3C DTCG format: `$value`, `$type` (color, dimension, fontFamily, fontWeight, duration, cubicBezier, shadow), `$description`, `{}` references, `.tokens.json` files. Categories: color, spacing, typography, radius, elevation, duration, easing, sizing, opacity, z-index.\n\n## Components\n\n- **Anatomy:** props\u002FAPI, variants, states (default, hover, active, focused, disabled, loading, error), slots, token bindings, accessibility, documentation.\n- **Maturity:** Defined → Implemented → Tested → Documented → Governed.\n- **API rules:** consistent prop names, enums over booleans, composition over configuration, sensible defaults, full TypeScript types, forwarded refs, polymorphic `as`.\n\n## Theming\n\nCSS custom properties are the runtime mechanism: swap values at the root, honor `prefers-color-scheme`, allow a persisted manual override. Component tokens reference semantic tokens, which resolve per theme. Multi-brand: shared behavior and accessibility, per-brand token sets, a component override layer only when tokens are not enough, and a Brand x Mode theme matrix.\n\n## Governance\n\nHybrid contribution is the default: the core team owns primitives (Button, Input, Card) and governance; domain teams contribute domain components (DataGrid, FileUploader) under core review. Changes go RFC → design, code, and accessibility review → build with tests → document → release. Version with SemVer (MAJOR = breaking API or visual change); keep deprecations for 2 major versions with warnings and migration guidance.\n\n## Design-to-Code\n\nFigma component names match code names exactly, and variants map to props. Tokens flow Figma → `tokens.json` → code through CI (Style Dictionary) into CSS variables, Swift, Android XML, React Native, and TypeScript types. Run visual regression against the Figma source.\n\n## Routing\n\n| Question | Read |\n|---|---|\n| Three-tier model with JSON examples, DTCG naming, token categories, the 2025 spec update | `references\u002Fdesign-token-architecture.md` |\n| DTCG spec detail, full `$type` reference, Style Dictionary config, Token Studio, token CI\u002FCD, the October 2025 stable release | `references\u002Ftoken-specification-guide.md` |\n| Aliasing, multi-theme tokens, transformation pipeline, platform outputs, token docs, versioning, testing | `references\u002Fdesign-token-implementation.md` |\n| Component anatomy, maturity levels, API principles, theme JSON, multi-brand layering, Figma-to-code sync | `references\u002Fcomponent-library-theming.md` |\n| Team models, contribution workflow, RFC and proposal templates, lifecycle, versioning, docs, adoption metrics | `references\u002Fgovernance-scaling.md` |\n| Five-level maturity model, assessment rubric, multi-brand tokens, white-label, migration, ROI, `$extensions` | `references\u002Fmaturity-model-multi-brand.md` |\n\n## Cross-Referencing\n\n- Visual design principles: `visual-design-mastery`\n- Accessibility component requirements: `accessibility-inclusive-design`\n- Motion tokens and animation: `interaction-motion-design`\n- Mobile component adaptations: `mobile-ux-design`\n- Figma MCP design-to-code flywheel: `figma-design-tool-workflows`\n- CSS `@layer` cascade for token architecture: `component-patterns-code`\n\n## Key Sources\n\n- Curtis, N. \"Design Systems\" and Modular Web Design\n- W3C Design Tokens Community Group specification\n- Figma design systems documentation\n- Material Design component guidelines\n- Brad Frost \"Atomic Design\" methodology\n",{"name":5,"description":7,"allowed-tools":24},"Read, Grep, Glob","main","f846d9a97082ff30d613b55a085cef425d822473","plugins\u002Fdesign-ops\u002Fskills\u002Fdesign-systems-architecture","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-systems-architecture",{"tool":39,"command":40},"bunx","bunx skills add shotcowboystyle\u002Fag-skills --skill design-systems-architecture",{"tool":42,"command":43},"pnpm","pnpm dlx skills add shotcowboystyle\u002Fag-skills --skill design-systems-architecture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fdesign-systems-architecture\u002FSKILL.md",true,[47,53,57,61,65,69],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fcomponent-library-theming.md","REFERENCE","参考文档",4063,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fdesign-systems-architecture\u002Freferences\u002Fcomponent-library-theming.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fdesign-token-architecture.md",10251,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fdesign-systems-architecture\u002Freferences\u002Fdesign-token-architecture.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fdesign-token-implementation.md",30827,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fdesign-systems-architecture\u002Freferences\u002Fdesign-token-implementation.md",{"path":62,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fgovernance-scaling.md",38475,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fdesign-systems-architecture\u002Freferences\u002Fgovernance-scaling.md",{"path":66,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fmaturity-model-multi-brand.md",26770,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fdesign-systems-architecture\u002Freferences\u002Fmaturity-model-multi-brand.md",{"path":70,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Ftoken-specification-guide.md",35921,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fdesign-systems-architecture\u002Freferences\u002Ftoken-specification-guide.md",[74,80,87,94,101,108],{"skillNo":75,"name":76,"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":77,"categories":78,"keywords":79,"publishedAt":19},"01M7F1YRY5S5QRJ1V0BJS130QX","no-description","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fno-description\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"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":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"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":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"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":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"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":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"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",[],[]]