Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
wshobson avatar

Design System Patterns

  • 12.3k installs
  • 38.4k repo stars
  • Updated July 22, 2026
  • wshobson/agents

design-system-patterns is an agent skill for design tokens, theming infrastructure, component architecture, and Figma-to-code pipelines in scalable UI systems.

About

design-system-patterns is a wshobson agents skill for building maintainable design systems across web and mobile. It covers primitive, semantic, and component token layers with naming by purpose, multi-platform generation, and CSS custom property theming including light/dark, system prefers-color-scheme, persistence, reduced motion, and high contrast. Component architecture sections span compound components, polymorphic as props, variant and size systems, slot composition, headless UI, and responsive style props. The token pipeline addresses Figma synchronization, Style Dictionary configuration, transforms, and CI/CD token updates. A quick-start TypeScript example shows gray and blue primitives mapped to semantic light and dark surfaces, borders, and interactive colors. Best practices warn against token sprawl, inconsistent naming, missing dark mode, hardcoded values, circular references, and platform gaps. Detailed worked examples live in references/details.md when the overview is insufficient. Use it when creating tokens, theme switching, multi-brand theming, or design-to-code foundations.

  • Token hierarchy: primitive, semantic, and component layers with purpose-based naming.
  • Theming via CSS variables, React providers, system preference detection, and persistent theme storage.
  • Component patterns: compound, polymorphic, variants, slots, headless UI, and responsive style props.
  • Figma-to-code pipeline with Style Dictionary transforms and CI/CD token update automation.
  • Best-practice guardrails against token sprawl, hardcoded values, and missing dark-mode coverage.

Design System Patterns by the numbers

  • 12,315 all-time installs (skills.sh)
  • +270 installs in the week ending Jul 29, 2026 (Skillselion tracking)
  • Ranked #51 of 1,888 Design & UI/UX skills by installs in the Skillselion catalog
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Jul 31, 2026 (Skillselion catalog sync)
At a glance

design-system-patterns capabilities & compatibility

Capabilities
three layer design token modeling · light and dark theme infrastructure · compound and polymorphic component patterns · style dictionary and figma synchronization guida · accessibility oriented theme modes (reduced moti
Works with
figma
Use cases
ui design · frontend
From the docs

What design-system-patterns says it does

Creating design tokens for colors, typography, spacing, and shadows
SKILL.md
Detailed pattern documentation lives in `references/details.md`.
SKILL.md
npx skills add https://github.com/wshobson/agents --skill design-system-patterns

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs12.3k
repo stars38.4k
Security audit3 / 3 scanners passed
Last updatedJuly 22, 2026
Repositorywshobson/agents

How do I structure design tokens, theme switching, and component patterns for a multi-platform design system?

Design scalable design systems with tokens, theming, component architecture, and Figma-to-code token pipelines.

Who is it for?

Frontend developers and designers establishing or refactoring a token-driven component library with dark mode support.

Skip if: Skip when you only need a single-page style tweak without a system-wide token or theming model.

When should I use this skill?

User asks for design tokens, theme switching, Figma token sync, compound components, or semantic color naming.

What you get

Documented token hierarchy, theming setup, component conventions, and token pipeline practices ready to implement.

  • Design token hierarchy
  • Theme configuration patterns
  • Component architecture blueprint

Files

SKILL.mdMarkdownGitHub ↗

Design System Patterns

Master design system architecture to create consistent, maintainable, and scalable UI foundations across web and mobile applications.

When to Use This Skill

  • Creating design tokens for colors, typography, spacing, and shadows
  • Implementing light/dark theme switching with CSS custom properties
  • Building multi-brand theming systems
  • Architecting component libraries with consistent APIs
  • Establishing design-to-code workflows with Figma tokens
  • Creating semantic token hierarchies (primitive, semantic, component)
  • Setting up design system documentation and guidelines

Core Capabilities

1. Design Tokens

  • Primitive tokens (raw values: colors, sizes, fonts)
  • Semantic tokens (contextual meaning: text-primary, surface-elevated)
  • Component tokens (specific usage: button-bg, card-border)
  • Token naming conventions and organization
  • Multi-platform token generation (CSS, iOS, Android)

2. Theming Infrastructure

  • CSS custom properties architecture
  • Theme context providers in React
  • Dynamic theme switching
  • System preference detection (prefers-color-scheme)
  • Persistent theme storage
  • Reduced motion and high contrast modes

3. Component Architecture

  • Compound component patterns
  • Polymorphic components (as prop)
  • Variant and size systems
  • Slot-based composition
  • Headless UI patterns
  • Style props and responsive variants

4. Token Pipeline

  • Figma to code synchronization
  • Style Dictionary configuration
  • Token transformation and formatting
  • CI/CD integration for token updates

Quick Start

// Design tokens with CSS custom properties
const tokens = {
  colors: {
    // Primitive tokens
    gray: {
      50: "#fafafa",
      100: "#f5f5f5",
      900: "#171717",
    },
    blue: {
      500: "#3b82f6",
      600: "#2563eb",
    },
  },
  // Semantic tokens (reference primitives)
  semantic: {
    light: {
      "text-primary": "var(--color-gray-900)",
      "text-secondary": "var(--color-gray-600)",
      "surface-default": "var(--color-white)",
      "surface-elevated": "var(--color-gray-50)",
      "border-default": "var(--color-gray-200)",
      "interactive-primary": "var(--color-blue-500)",
    },
    dark: {
      "text-primary": "var(--color-gray-50)",
      "text-secondary": "var(--color-gray-400)",
      "surface-default": "var(--color-gray-900)",
      "surface-elevated": "var(--color-gray-800)",
      "border-default": "var(--color-gray-700)",
      "interactive-primary": "var(--color-blue-400)",
    },
  },
};

Detailed patterns and worked examples

Detailed pattern documentation lives in references/details.md. Read that file when the navigation tier above is insufficient.

Best Practices

1. Name Tokens by Purpose: Use semantic names (text-primary) not visual descriptions (dark-gray) 2. Maintain Token Hierarchy: Primitives > Semantic > Component tokens 3. Document Token Usage: Include usage guidelines with token definitions 4. Version Tokens: Treat token changes as API changes with semver 5. Test Theme Combinations: Verify all themes work with all components 6. Automate Token Pipeline: CI/CD for Figma-to-code synchronization 7. Provide Migration Paths: Deprecate tokens gradually with clear alternatives

Common Issues

  • Token Sprawl: Too many tokens without clear hierarchy
  • Inconsistent Naming: Mixed conventions (camelCase vs kebab-case)
  • Missing Dark Mode: Tokens that don't adapt to theme changes
  • Hardcoded Values: Using raw values instead of tokens
  • Circular References: Tokens referencing each other in loops
  • Platform Gaps: Tokens missing for some platforms (web but not mobile)

Related skills

How it compares

Pick design-system-patterns over generic frontend skills when the goal is token hierarchies and theming infrastructure rather than individual component styling.

FAQ

Who is design-system-patterns for?

Developers building or scaling design systems with tokens, themes, and component libraries on web or mobile.

When should I use design-system-patterns?

When defining primitive-to-semantic token layers, dark mode theming, or Figma/Style Dictionary pipelines.

Is design-system-patterns safe to install?

Review the Security Audits panel on this page before installing in production.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.