Skills · Design & UI

Design System Patterns

Unverified30/40

Build scalable design systems with design tokens, theming infrastructure, and component architecture patterns. Use when creating design tokens, implementing theme switching, building component libraries, or establishing design system foundations.

Originally by wshobson · MIT

Claude CodePartialHas SKILL.md but declares no allowed-tools — Claude Code will ask for permission each time
CursorPartialPlain prose you can paste in — but no Cursor rules file
CodexPartialPlain prose you can paste in — but no AGENTS.md
Gemini CLIPartialPlain prose you can paste in
CopilotPartialPlain prose you can paste in — but no Copilot instructions file
npx agentalley add design-system-patterns

This command does not work yet — the CLI is still being built. Until then, use Raw in the reader below to take the file.

Who is stuck, and on what

Build scalable design systems with design tokens, theming infrastructure, and component architecture patterns. Use when creating design tokens, implementing theme switching, building component libraries, or establishing design system foundations.

The whole source

No sign-in, no blur, nothing truncated
design-system-patterns/SKILL.md116 lines3.9 KBRawView on GitHub
Frontmatter — 2 properties
namedesign-system-patterns
descriptionBuild scalable design systems with design tokens, theming infrastructure, and component architecture patterns. Use when creating design tokens, implementing theme switching, building component libraries, or establishing design system foundations.
1---
2name: design-system-patterns
3description: Build scalable design systems with design tokens, theming infrastructure, and component architecture patterns. Use when creating design tokens, implementing theme switching, building component libraries, or establishing design system foundations.
4---A5No allowed-tools declared — no way to tell what this skill may touch
5 
6# Design System Patterns
7 
8Master design system architecture to create consistent, maintainable, and scalable UI foundations across web and mobile applications.
9 
10## When to Use This Skill
11 
12- Creating design tokens for colors, typography, spacing, and shadows
13- Implementing light/dark theme switching with CSS custom properties
14- Building multi-brand theming systems
15- Architecting component libraries with consistent APIs
16- Establishing design-to-code workflows with Figma tokens
17- Creating semantic token hierarchies (primitive, semantic, component)
18- Setting up design system documentation and guidelines
19 
20## Core Capabilities
21 
22### 1. Design Tokens
23 
24- Primitive tokens (raw values: colors, sizes, fonts)
25- Semantic tokens (contextual meaning: text-primary, surface-elevated)
26- Component tokens (specific usage: button-bg, card-border)
27- Token naming conventions and organization
28- Multi-platform token generation (CSS, iOS, Android)
29 
30### 2. Theming Infrastructure
31 
32- CSS custom properties architecture
33- Theme context providers in React
34- Dynamic theme switching
35- System preference detection (prefers-color-scheme)
36- Persistent theme storage
37- Reduced motion and high contrast modes
38 
39### 3. Component Architecture
40 
41- Compound component patterns
42- Polymorphic components (as prop)
43- Variant and size systems
44- Slot-based composition
45- Headless UI patterns
46- Style props and responsive variants
47 
48### 4. Token Pipeline
49 
50- Figma to code synchronization
51- Style Dictionary configuration
52- Token transformation and formatting
53- CI/CD integration for token updates
54 
55## Quick Start
56 
57```typescript
58// Design tokens with CSS custom properties
59const tokens = {
60 colors: {
61 // Primitive tokens
62 gray: {
63 50: "#fafafa",
64 100: "#f5f5f5",
65 900: "#171717",
66 },
67 blue: {
68 500: "#3b82f6",
69 600: "#2563eb",
70 },
71 },
72 // Semantic tokens (reference primitives)
73 semantic: {
74 light: {
75 "text-primary": "var(--color-gray-900)",
76 "text-secondary": "var(--color-gray-600)",
77 "surface-default": "var(--color-white)",
78 "surface-elevated": "var(--color-gray-50)",
79 "border-default": "var(--color-gray-200)",
80 "interactive-primary": "var(--color-blue-500)",
81 },
82 dark: {
83 "text-primary": "var(--color-gray-50)",
84 "text-secondary": "var(--color-gray-400)",
85 "surface-default": "var(--color-gray-900)",
86 "surface-elevated": "var(--color-gray-800)",
87 "border-default": "var(--color-gray-700)",
88 "interactive-primary": "var(--color-blue-400)",
89 },
90 },
91};
92```
93 
94## Detailed patterns and worked examples
95 
96Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient.
97 
98## Best Practices
99 
1001. **Name Tokens by Purpose**: Use semantic names (text-primary) not visual descriptions (dark-gray)
1012. **Maintain Token Hierarchy**: Primitives > Semantic > Component tokens
1023. **Document Token Usage**: Include usage guidelines with token definitions
1034. **Version Tokens**: Treat token changes as API changes with semver
1045. **Test Theme Combinations**: Verify all themes work with all components
1056. **Automate Token Pipeline**: CI/CD for Figma-to-code synchronization
1067. **Provide Migration Paths**: Deprecate tokens gradually with clear alternatives
107 
108## Common Issues
109 
110- **Token Sprawl**: Too many tokens without clear hierarchy
111- **Inconsistent Naming**: Mixed conventions (camelCase vs kebab-case)
112- **Missing Dark Mode**: Tokens that don't adapt to theme changes
113- **Hardcoded Values**: Using raw values instead of tokens
114- **Circular References**: Tokens referencing each other in loops
115- **Platform Gaps**: Tokens missing for some platforms (web but not mobile)
116 

Reviews

Installed this one?Write the first review and take the Trailblazer badge.

Reviews only open after a real install, so this is empty — and we leave it empty rather than invent one.

Alternatives

Also in Design & UI