design-systems
Build and govern scalable design systems with tokens, components, documentation, and adoption strategy.
- License 许可
- MIT
- 最近更新
- 2026-11-07
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- design-systems
- category
- creative-design
- description
- Build and govern scalable design systems with tokens, components, documentation, and adoption strategy.
03 SKILL.md 正文
Overview
A design system is a product serving products: a shared language of tokens, components, and patterns that lets teams ship consistent interfaces faster. But most design systems fail not on craft but on adoption — they're built as monuments instead of tools. This skill covers building systems people actually use: tokens, component architecture, documentation, and governance.
When to use
-
Starting a design system for a product or organization
-
Auditing and consolidating inconsistent UI across products
-
Defining design tokens (color, spacing, typography, elevation)
-
Writing component documentation and usage guidelines
-
Planning design system governance and adoption
Core concepts
-
- Tokens are the contract. Design tokens (color, spacing, type, radius, shadow) in a tool-agnostic format are the single source of truth that design tools and code both consume. Name semantically (action/primary/hover), not literally (blue-500).
-
- Components: build for the 80%. A component should solve the common case beautifully and offer escape hatches (slots, props) for the rest. Over-abstracted components that try to cover everything become unusable.
-
- Documentation is the product. A component without usage guidance, do/don't examples, and accessibility notes won't be adopted correctly. Write docs for the consumer (product designer/dev), not for yourself.
-
- Adoption beats completeness. A system with 15 well-adopted components beats one with 80 nobody uses. Ship the highest-traffic components first; expand based on real demand.
-
- Governance prevents entropy. Who can add components? What's the contribution process? How are breaking changes handled? Without answers, the system forks into team-specific variants within a year.
-
- Measure what matters. Adoption rate (% of screens using system components), contribution velocity, time-to-design/ship, and design-dev consistency issues. Report these to leadership — systems need ongoing investment.
Practical workflow
-
- Audit the current state. Inventory existing UI: screenshot common patterns, catalog inconsistencies, count button variants in the wild. The audit justifies the investment and scopes the work.
-
- Define tokens first. Color (semantic roles + scales), spacing (4/8pt base scale), typography (scale + roles), radius, elevation, motion. Document naming conventions before building anything.
-
- Prioritize the component backlog. Rank by usage frequency × inconsistency pain. Buttons, inputs, and navigation almost always come first. Build in small, shippable batches.
-
- Build components properly. Each gets: all states (default, hover, focus, disabled, error, loading), sizes, theming via tokens, accessibility baked in (focus rings, ARIA roles, contrast), and responsive behavior.
-
- Write the docs. For each component: when to use / when not to, anatomy, variants, content guidelines, accessibility notes, and code + design usage. Include live examples, not just pictures.
-
- Set up governance. Contribution model (who proposes, who reviews, who approves), versioning and changelog discipline, deprecation policy, and a regular system review cadence.
-
- Drive adoption. Migrate high-traffic surfaces first, provide codemods or migration guides, run office hours, celebrate contributors. Track adoption metrics and report wins.
Common pitfalls
-
- Building the cathedral. Spending a year perfecting 100 components before anyone uses them. Ship early, iterate with consumers.
-
- No dedicated ownership. A design system as everyone's side project becomes nobody's priority. It needs named owners with real time allocated.
-
- Pixel-perfect, adoption-zero. Craft without distribution. If designers find it easier to draw custom buttons, the system has failed regardless of its quality.
-
- Breaking changes without migration paths. Renaming tokens or restructuring components without codemods and warnings destroys trust. Version carefully; deprecate gracefully.
-
- Documentation as an afterthought. Undocumented components get misused, which erodes the consistency the system exists to create.
-
- One system to rule them all (prematurely). Forcing a single system across wildly different products (marketing site + complex app) creates components that serve nobody well. Sometimes two systems with shared tokens is right.
04 同仓库更多 Skills
web-scrape
Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open/fetch fails on JS-heavy pages, or when you need clean markdown/structured extraction from a site. Requires FIRECRAWL_API_KEY.
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/CSS, 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.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
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).