home / skills / secondsky / claude-skills / design-system-creation

This skill helps you create comprehensive design systems with tokens, components, and documentation for consistent UI across teams.

npx playbooks add skill secondsky/claude-skills --skill design-system-creation

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
3.0 KB
---
name: design-system-creation
description: |
  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
license: MIT
---

# 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

```css
: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

```markdown
## 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)

```tsx
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

Overview

This skill creates end-to-end design systems with tokens, components, patterns, and documentation to ensure consistent UI across teams. It produces foundation assets (colors, typography, spacing, elevation), ready-to-use component code and docs, and governance guidance for maintainable libraries. The output targets production workflows, theming, accessibility, and cross-platform consistency.

How this skill works

It generates design tokens (CSS variables or semantic tokens), scalable type and spacing scales, color palettes including dark-mode variants, and elevation/shadow tokens. It scaffolds component anatomy, variants, states, accessibility requirements, and example implementations (React/Tailwind/CSS variables). It also produces documentation and governance artifacts like contribution flow, versioning, and deprecation policy.

When to use it

  • Establishing brand-consistent UI standards across products
  • Building or migrating a component library (React, Tailwind, Storybook)
  • Onboarding new design or engineering teams to consistent patterns
  • Adding theming or dark-mode support to an existing UI
  • Enforcing accessibility and WCAG compliance across components

Best practices

  • Start with a small, well-documented foundation of design tokens before building components
  • Define semantic tokens (purpose-driven names) over raw color names for future flexibility
  • Document anatomy, variants, states, keyboard behavior, and ARIA for every component
  • Include do/don't usage examples and visual tests (Storybook) for each pattern
  • Plan governance: RFCs for new components, semantic versioning, and deprecation notices
  • Design for dark mode and responsive breakpoints from the start

Example use cases

  • Generate a CSS-variable token set with light and dark palettes plus a type scale for a new brand
  • Create documented React component implementations (Button, Input, Card) with accessibility notes and Storybook stories
  • Produce a spacing and grid system with responsive breakpoints and Tailwind mapping
  • Prepare a contribution and release process: RFC template, review committee, and changelog strategy
  • Audit an existing UI to extract tokens, replace hard-coded styles, and unify components

FAQ

What formats are generated for tokens?

Exports include CSS variables, semantic token maps, and mapping guidance for Tailwind or JS token objects.

How does the skill handle accessibility?

Every component doc includes WCAG guidance, keyboard interactions, ARIA roles, focus styles, and contrast checks to meet AA standards.