[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EMT0PSF6AX5XG2CJQCC36R":3,"skill-same:01M7EMT0PSF6AX5XG2CJQCC36R":47},{"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":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7EMT0PSF6AX5XG2CJQCC36R","design-systems",null,"Build and govern scalable design systems with tokens, components, documentation, and adoption strategy.","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-design-systems\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: design-systems\ndescription: Build and govern scalable design systems with tokens, components, documentation, and adoption strategy.\ncategory: creative-design\n---\n\n## Overview\n\nA design system is a product serving products: a shared language of tokens, components, and patterns\nthat lets teams ship consistent interfaces faster. But most design systems fail not on craft but on\nadoption — they're built as monuments instead of tools. This skill covers building systems people\nactually use: tokens, component architecture, documentation, and governance.\n\n## When to use\n\n- Starting a design system for a product or organization\n\n- Auditing and consolidating inconsistent UI across products\n\n- Defining design tokens (color, spacing, typography, elevation)\n\n- Writing component documentation and usage guidelines\n\n- Planning design system governance and adoption\n\n## Core concepts\n\n- - **Tokens are the contract.** Design tokens (color, spacing, type, radius, shadow) in a\n  tool-agnostic format are the single source of truth that design tools and code both consume. Name\n  semantically (action\u002Fprimary\u002Fhover), not literally (blue-500).\n- - **Components: build for the 80%.** A component should solve the common case beautifully and\n  offer escape hatches (slots, props) for the rest. Over-abstracted components that try to cover\n  everything become unusable.\n- - **Documentation is the product.** A component without usage guidance, do\u002Fdon't examples, and\n  accessibility notes won't be adopted correctly. Write docs for the consumer (product\n  designer\u002Fdev), not for yourself.\n- - **Adoption beats completeness.** A system with 15 well-adopted components beats one with 80\n  nobody uses. Ship the highest-traffic components first; expand based on real demand.\n- - **Governance prevents entropy.** Who can add components? What's the contribution process? How\n  are breaking changes handled? Without answers, the system forks into team-specific variants within\n  a year.\n- - **Measure what matters.** Adoption rate (% of screens using system components), contribution\n  velocity, time-to-design\u002Fship, and design-dev consistency issues. Report these to leadership —\n  systems need ongoing investment.\n\n## Practical workflow\n\n1. 1. **Audit the current state.** Inventory existing UI: screenshot common patterns, catalog\n   inconsistencies, count button variants in the wild. The audit justifies the investment and scopes\n   the work.\n2. 2. **Define tokens first.** Color (semantic roles + scales), spacing (4\u002F8pt base scale),\n   typography (scale + roles), radius, elevation, motion. Document naming conventions before\n   building anything.\n3. 3. **Prioritize the component backlog.** Rank by usage frequency × inconsistency pain. Buttons,\n   inputs, and navigation almost always come first. Build in small, shippable batches.\n4. 4. **Build components properly.** Each gets: all states (default, hover, focus, disabled, error,\n   loading), sizes, theming via tokens, accessibility baked in (focus rings, ARIA roles, contrast),\n   and responsive behavior.\n5. 5. **Write the docs.** For each component: when to use \u002F when not to, anatomy, variants, content\n   guidelines, accessibility notes, and code + design usage. Include live examples, not just\n   pictures.\n6. 6. **Set up governance.** Contribution model (who proposes, who reviews, who approves),\n   versioning and changelog discipline, deprecation policy, and a regular system review cadence.\n7. 7. **Drive adoption.** Migrate high-traffic surfaces first, provide codemods or migration guides,\n   run office hours, celebrate contributors. Track adoption metrics and report wins.\n\n## Common pitfalls\n\n- - **Building the cathedral.** Spending a year perfecting 100 components before anyone uses them.\n  Ship early, iterate with consumers.\n- - **No dedicated ownership.** A design system as everyone's side project becomes nobody's\n  priority. It needs named owners with real time allocated.\n- - **Pixel-perfect, adoption-zero.** Craft without distribution. If designers find it easier to\n  draw custom buttons, the system has failed regardless of its quality.\n- - **Breaking changes without migration paths.** Renaming tokens or restructuring components\n  without codemods and warnings destroys trust. Version carefully; deprecate gracefully.\n- - **Documentation as an afterthought.** Undocumented components get misused, which erodes the\n  consistency the system exists to create.\n- - **One system to rule them all (prematurely).** Forcing a single system across wildly different\n  products (marketing site + complex app) creates components that serve nobody well. Sometimes two\n  systems with shared tokens is right.\n","## Overview\n\nA design system is a product serving products: a shared language of tokens, components, and patterns\nthat lets teams ship consistent interfaces faster. But most design systems fail not on craft but on\nadoption — they're built as monuments instead of tools. This skill covers building systems people\nactually use: tokens, component architecture, documentation, and governance.\n\n## When to use\n\n- Starting a design system for a product or organization\n\n- Auditing and consolidating inconsistent UI across products\n\n- Defining design tokens (color, spacing, typography, elevation)\n\n- Writing component documentation and usage guidelines\n\n- Planning design system governance and adoption\n\n## Core concepts\n\n- - **Tokens are the contract.** Design tokens (color, spacing, type, radius, shadow) in a\n  tool-agnostic format are the single source of truth that design tools and code both consume. Name\n  semantically (action\u002Fprimary\u002Fhover), not literally (blue-500).\n- - **Components: build for the 80%.** A component should solve the common case beautifully and\n  offer escape hatches (slots, props) for the rest. Over-abstracted components that try to cover\n  everything become unusable.\n- - **Documentation is the product.** A component without usage guidance, do\u002Fdon't examples, and\n  accessibility notes won't be adopted correctly. Write docs for the consumer (product\n  designer\u002Fdev), not for yourself.\n- - **Adoption beats completeness.** A system with 15 well-adopted components beats one with 80\n  nobody uses. Ship the highest-traffic components first; expand based on real demand.\n- - **Governance prevents entropy.** Who can add components? What's the contribution process? How\n  are breaking changes handled? Without answers, the system forks into team-specific variants within\n  a year.\n- - **Measure what matters.** Adoption rate (% of screens using system components), contribution\n  velocity, time-to-design\u002Fship, and design-dev consistency issues. Report these to leadership —\n  systems need ongoing investment.\n\n## Practical workflow\n\n1. 1. **Audit the current state.** Inventory existing UI: screenshot common patterns, catalog\n   inconsistencies, count button variants in the wild. The audit justifies the investment and scopes\n   the work.\n2. 2. **Define tokens first.** Color (semantic roles + scales), spacing (4\u002F8pt base scale),\n   typography (scale + roles), radius, elevation, motion. Document naming conventions before\n   building anything.\n3. 3. **Prioritize the component backlog.** Rank by usage frequency × inconsistency pain. Buttons,\n   inputs, and navigation almost always come first. Build in small, shippable batches.\n4. 4. **Build components properly.** Each gets: all states (default, hover, focus, disabled, error,\n   loading), sizes, theming via tokens, accessibility baked in (focus rings, ARIA roles, contrast),\n   and responsive behavior.\n5. 5. **Write the docs.** For each component: when to use \u002F when not to, anatomy, variants, content\n   guidelines, accessibility notes, and code + design usage. Include live examples, not just\n   pictures.\n6. 6. **Set up governance.** Contribution model (who proposes, who reviews, who approves),\n   versioning and changelog discipline, deprecation policy, and a regular system review cadence.\n7. 7. **Drive adoption.** Migrate high-traffic surfaces first, provide codemods or migration guides,\n   run office hours, celebrate contributors. Track adoption metrics and report wins.\n\n## Common pitfalls\n\n- - **Building the cathedral.** Spending a year perfecting 100 components before anyone uses them.\n  Ship early, iterate with consumers.\n- - **No dedicated ownership.** A design system as everyone's side project becomes nobody's\n  priority. It needs named owners with real time allocated.\n- - **Pixel-perfect, adoption-zero.** Craft without distribution. If designers find it easier to\n  draw custom buttons, the system has failed regardless of its quality.\n- - **Breaking changes without migration paths.** Renaming tokens or restructuring components\n  without codemods and warnings destroys trust. Version carefully; deprecate gracefully.\n- - **Documentation as an afterthought.** Undocumented components get misused, which erodes the\n  consistency the system exists to create.\n- - **One system to rule them all (prematurely).** Forcing a single system across wildly different\n  products (marketing site + complex app) creates components that serve nobody well. Sometimes two\n  systems with shared tokens is right.\n",{"name":5,"category":24,"description":7},"creative-design","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-design-systems",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill design-systems",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill design-systems",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill design-systems","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-design-systems\u002FSKILL.md",true,[],[48,55,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]