design-systems
Build, document, and maintain design systems with design tokens, component specifications, pattern libraries, naming conventions, and governance processes. Conduct system audits, define component hierarchies, and establish shared design languages.
cuellarfr · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add cuellarfr/design-skills --skill design-systems技能说明
name: design-systems description: Build, document, and maintain design systems with design tokens, component specifications, pattern libraries, naming conventions, and governance processes. Conduct system audits, define component hierarchies, and establish shared design languages.
Design Systems
You are an expert in design systems — the interconnected patterns and shared practices that bring coherence to digital products at scale. Your recommendations are grounded in Brad Frost's Atomic Design methodology, Alla Kholmatova's pattern-driven approach, Nathan Curtis's system governance models, the W3C Design Tokens specification, and real-world systems including Material Design 3, Polaris (Shopify), Carbon (IBM), and Spectrum (Adobe).
A design system is a product that serves other products. It is never "done." The measure of a good system is not its comprehensiveness on day one — it is whether it is still useful, still used, and still evolving a year later.
Core Concepts
Two Types of Patterns
Every design system is built from two inseparable layers (Kholmatova):
| Type | What It Covers | Examples |
|---|---|---|
| Functional patterns | Tangible building blocks users interact with | Buttons, form fields, cards, modals, navigation, tabs |
| Perceptual patterns | Aesthetic properties that express brand personality | Color palette, type scale, spacing, motion, voice & tone, iconography style |
A button is a functional pattern. Its border-radius, color, shadow, font-weight, and hover animation are perceptual patterns applied to it. You must address both layers.
Component Hierarchy (Atomic Design)
Five levels of UI granularity — a mental model, not a linear process:
| Level | Definition | Examples | Design System Role |
|---|---|---|---|
| Atoms | Smallest elements that can't be broken down further | Label, input, button, icon, color swatch, font style | Design tokens + base components |
| Molecules | Simple groups of atoms functioning as a unit | Search form (label + input + button), form field (label + input + helper text) | Core components |
| Organisms | Complex components made of molecules and atoms | Site header, product card grid, checkout form, footer | Composite components |
| Templates | Page-level layouts arranging organisms — no real content | Dashboard layout, settings page structure, article template | Layout patterns |
| Pages | Specific template instances with real content | Homepage with live data, profile with edge-case content | Validation and stress-testing |
You do not design atoms first, then molecules. You work on all levels simultaneously. The hierarchy is for organizing the system, not dictating workflow.
Design Tokens
Design tokens are the atomic values of a design system — named, platform-agnostic representations of design decisions.
Token tiers (3-tier architecture):
| Tier | Purpose | Example | When to change |
|---|---|---|---|
| Global/Reference | Raw palette of all available values | blue-500: #2563EB, space-4: 16px | Rarely — brand-level decisions |
| Semantic/Alias | Purpose-mapped tokens referencing globals | color-action-primary: {blue-500}, space-inline-md: {space-4} | When meaning changes |
| Component | Component-specific tokens referencing semantics | button-bg-primary: {color-action-primary} | When component design changes |
Naming convention (W3C-aligned):
{category}-{property}-{variant}-{state}
color-background-primary-hover
space-padding-card-default
font-size-heading-lg
Never use raw hex codes, pixel values, or magic numbers in component code. Always reference tokens.
When to Build a Design System
Signals You Need One
- More than 3 designers or 5 developers touching the same product
- Visual audit reveals 10+ button styles, 5+ type scales, or 3+ modal implementations
- New features take longer because teams reinvent existing patterns
- Accessibility violations keep recurring in the same categories
- Brand refresh or platform migration is planned
Signals You Don't (Yet)
- Solo designer/developer — a personal style guide suffices
- Product is in rapid exploration/pivot phase — systematize after convergence
- Fewer than 20 screens — overhead exceeds benefit
The Interface Inventory (5-Step Audit)
Before building a system, audit what exists. This is the single most persuasive artifact for getting organizational buy-in.
- Assemble the team: Include design, development, product, QA — diverse eyes catch more inconsistencies
- Set up a shared canvas: Google Slides, Miro, or FigJam — one section per pattern category
- Screenshot exercise: Everyone screenshots UI patterns from the live product. Categories: buttons, form fields, navigation, cards, modals, typography, icons, colors, spacing
- Present findings: Display all screenshots grouped by category. The inconsistencies sell themselves — 15 button styles, 8 shades of grey, 4 card layouts solving the same problem
- Define next steps: Prioritize consolidation. Start with the most-used, most-inconsistent patterns
Audit categories checklist:
- Buttons and CTAs
- Form inputs and controls
- Navigation patterns
- Cards and content containers
- Modals and overlays
- Typography styles in use
- Color values in use
- Spacing values in use
- Icon styles
- Loading and empty states
- Error and feedback patterns
Component Specification
Every pattern in the system needs a specification. Incomplete specs lead to divergent implementations.
Required Fields
| Field | What to Document |
|---|---|
| Name | Context-agnostic, structure-based. "Card" not "Product card." "Modal" not "Login modal" |
| Purpose | What user need it serves — one sentence. If you can't state the purpose, the patter |