design-system-creation

secondsky's avatarfrom secondsky

Creates comprehensive design systems with typography, colors, components, and documentation for consistent UI development. Use when establishing design standards, building component libraries, or ensuring cross-team consistency.Keywords: design-tokens, typography, spacing, color-palette, components, patterns, variables, dark-mode, theming, CSS-variables, accessibility, WCAG, responsive, grid-system, breakpoints, design-scale, semantic-tokens, component-library, style-guide, documentation, Figma, Storybook, brand-consistency, design-principles

⭐9stars🔀0forks📁View on GitHub🕐Updated Jan 1, 2026

When & Why to Use This Skill

This Claude skill automates the creation of comprehensive design systems, bridging the gap between design and development. It generates foundational design tokens, reusable UI components, and detailed documentation to ensure visual consistency, scalability, and WCAG-compliant accessibility across digital products. By providing standardized CSS variables and React component structures, it streamlines the handoff process and maintains brand integrity across multiple teams.

Use Cases

  • Establishing a new brand's digital identity with standardized design tokens for colors, typography, and spacing.
  • Building a scalable and accessible React component library with built-in support for dark mode and responsive layouts.
  • Creating centralized style guides and governance documentation to ensure UI consistency across cross-functional product teams.
  • Rapidly prototyping design-to-code workflows using semantic tokens and predefined UI patterns like forms and navigation.
namedesign-system-creation
description|
Keywordsdesign-tokens, typography, spacing, color-palette, components, patterns, variables, dark-mode, theming, CSS-variables, accessibility, WCAG, responsive, grid-system, breakpoints, design-scale, semantic-tokens, component-library, style-guide, documentation, Figma, Storybook, brand-consistency, design-principles
licenseMIT

Design System Creation

Build comprehensive design systems for consistent UI development across teams.

Design System Layers

  1. Foundation: Colors, typography, spacing, elevation
  2. Components: Buttons, inputs, cards, navigation
  3. Patterns: Forms, layouts, empty states

Foundation - Design Tokens

:root {
  /* Colors */
  --color-primary-50: #eff6ff;
  --color-primary-500: #3b82f6;
  --color-primary-900: #1e3a8a;

  /* Semantic colors */
  --color-success: #22c55e;
  --color-warning: #f59e0b;
  --color-error: #ef4444;

  /* Typography */
  --font-sans: 'Inter', system-ui, sans-serif;
  --font-mono: 'Fira Code', monospace;

  /* Type scale */
  --text-xs: 0.75rem;
  --text-sm: 0.875rem;
  --text-base: 1rem;
  --text-lg: 1.125rem;
  --text-xl: 1.25rem;
  --text-2xl: 1.5rem;

  /* Spacing (4px base) */
  --space-1: 0.25rem;
  --space-2: 0.5rem;
  --space-4: 1rem;
  --space-8: 2rem;

  /* Elevation */
  --shadow-sm: 0 1px 2px rgba(0,0,0,0.05);
  --shadow-md: 0 4px 6px rgba(0,0,0,0.1);
  --shadow-lg: 0 10px 15px rgba(0,0,0,0.1);
}

Component Documentation

## Button

### Anatomy
- Container (padding, background)
- Label (text)
- Icon (optional)

### Variants
- Primary: Main actions
- Secondary: Alternative actions
- Ghost: Subtle actions

### States
- Default, Hover, Active, Disabled, Loading

### Accessibility
- Role: button
- Keyboard: Enter/Space to activate
- Focus: Visible focus ring

Component Example (React)

interface ButtonProps {
  variant?: 'primary' | 'secondary' | 'ghost';
  size?: 'sm' | 'md' | 'lg';
  loading?: boolean;
  disabled?: boolean;
  children: React.ReactNode;
}

function Button({ variant = 'primary', size = 'md', loading, disabled, children }: ButtonProps) {
  return (
    <button
      className={`btn btn-${variant} btn-${size}`}
      disabled={disabled || loading}
      aria-busy={loading}
    >
      {loading ? <Spinner /> : children}
    </button>
  );
}

Governance

  • Review Committee: Approves new components
  • Contribution Process: RFC → Review → Implementation
  • Versioning: Semantic versioning for releases
  • Deprecation: 3-month notice with migration guide

Best Practices

  • Start with foundational tokens
  • Document every component thoroughly
  • Ensure WCAG 2.1 AA compliance
  • Support dark mode from the start
  • Include usage guidelines with do/don't examples