Skip to main content
skill CX Codex

design-system-creator — Claude Code skill: features and setup

The design-system-creator skill builds design systems with tokens, CSS structure, component docs, and style guides. Use it when a project needs a shared UI foundation.

MIT 250 installs ★ 274 updated 2026-10-30

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add curiositech/some_claude_skills --skill design-system-creator -a claude-code
Open on GitHub

What design-system-creator does

design-system-creator helps define color, spacing, and type tokens, then connects them through CSS custom properties and naming rules. It can structure a component library with anatomy, variants, states, responsive behavior, accessibility notes, and code examples. The output can include a design bible and style guide.

Its workflow moves from reviewing existing patterns to defining the system, documenting it, and checking accessibility and responsiveness. The skill can read and edit project files and includes integrations for 21st.dev, stability-ai, and firecrawl. Color tokens are expected in OKLCH; hands-on component implementation belongs to other skills.

What it helps with

  • define color, spacing, and type tokens
  • organize CSS into ITCSS layers
  • document component variants and states
  • extract a design system from existing CSS
  • build a design bible with usage examples

Example prompts for the agent

  • Create a design system for this project with tokens, components, and CSS naming rules.
  • Audit the current styles and extract a practical token structure.
  • Write a design bible covering component states, accessibility, and responsive behavior.

How to install design-system-creator

1Skills CLI (Vercel)

npx skills add curiositech/some_claude_skills --skill design-system-creator -a claude-code

2Manually: put the files in place

~/.claude/skills/design-system-creator/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/design-system-creator/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about design-system-creator

How do I install design-system-creator in Claude Code?

Run npx skills add curiositech/some_claude_skills --skill design-system-creator -a claude-code. The skill file will be available at ~/.claude/skills/design-system-creator/SKILL.md.

What does design-system-creator do?

It defines design tokens, CSS architecture, component documentation, and a design bible. It can also review existing styles and organize themes.

Which color format does design-system-creator use?

The skill uses OKLCH for color tokens instead of hex or HSL. It does not handle the actual implementation of UI components.

Source text

SKILL.md · MIT
---
name: design-system-creator
description: Builds comprehensive design systems and design bibles with production-ready CSS. Expert in design tokens, component libraries, CSS architecture. Use for design system creation, token architecture,
  component documentation, style guide generation. Activate on "design system", "design tokens", "CSS architecture", "component library", "style guide", "design bible". NOT for typography deep-dives (use
  typography-expert), color theory mathematics (use color-theory-palette-harmony-expert), brand identity strategy (use web-design-expert), or actual UI implementation (use web-design-expert or native-app-designer).
allowed-tools: Read,Write,Edit,Glob,mcp__magic__21st_magic_component_builder,mcp__magic__21st_magic_component_refiner,mcp__stability-ai__stability-ai-generate-image,mcp__firecrawl__firecrawl_search
metadata:
  category: Design & Creative
  pairs-with:
  - skill: typography-expert
    reason: Typography decisions for the system
  - skill: color-theory-palette-harmony-expert
    reason: Color token architecture
  tags:
  - design-system
  - tokens
  - components
  - css
  - style-guide
---

# Design System Creator

Design systems architect and CSS expert specializing in creating comprehensive, scalable design bibles.

## When to Use This Skill

✅ **Use for:**
- Creating design tokens from scratch (colors, spacing, typography scales)
- Building CSS custom property architectures
- Documenting component libraries with usage guidelines
- Creating design bibles and style guides
- Establishing naming conventions (BEM, OOCSS, SMACSS)
- Auditing existing CSS for design system extraction
- Theming and dark mode token systems
- Multi-brand/white-label token structures

❌ **Do NOT use for:**
- Typography selection and pairing → **typography-expert**
- Color theory and palette generation → **color-theory-palette-harmony-expert**
- Brand identity and visual direction → **web-design-expert**
- Actual component implementation → **web-design-expert** or **native-app-designer**
- Icon design → **web-design-expert**
- Motion design principles → **native-app-designer**

## Three-Tier Token Architecture

The foundation of scalable design systems:

```css
:root {
  /* 1. PRIMITIVE - Raw values (ALWAYS use OKLCH for colors) */
  --color-blue-500: oklch(62.8% 0.195 252.5);
  --space-4: 1rem;

  /* 2. SEMANTIC - Purpose-driven */
  --color-primary: var(--color-blue-500);
  --space-component-padding: var(--space-4);

  /* 3. COMPONENT - Specific usage */
  --button-bg: var(--color-primary);
  --button-padding: var(--space-component-padding);
}
```

→ See `references/token-architecture.md` for dark mode, multi-brand, and complete examples.

## OKLCH: The Modern Color Standard

**⚠️ CRITICAL: Always use OKLCH for color tokens, not hex or HSL.**

OKLCH is perceptually uniform - equal L values mean equal perceived lightness. This is essential for:
- Generating harmonious color scales
- Ensuring accessibility (L=50% is true middle gray)
- Theming (adjust L for dark mode, C for brand intensity)

```css
:root {
  /* OKLCH format: oklch(Lightness% Chroma Hue) */

  /* Primary scale - same hue, varying lightness */
  --color-primary-100: oklch(95% 0.05 252);
  --color-primary-500: oklch(62% 0.19 252);
  --color-primary-900: oklch(30% 0.15 252);

  /* Dark mode: reduce L uniformly */
  --color-bg-light: oklch(98% 0.01 252);
  --color-bg-dark: oklch(15% 0.02 252);
}
```

**Essential OKLCH Resources:**
| Resource | Purpose |
|----------|---------|
| [oklch.com](https://oklch.com/) | Interactive OKLCH color picker |
| [Evil Martians: Why Quit RGB/HSL](https://evilmartians.com/chronicles/oklch-in-css-why-quit-rgb-hsl) | Why OKLCH is the new standard |
| [Harmonizer](https://harmonizer.evilmartians.com/) | Generate harmonious palettes in OKLCH |

**OKLCH Benefits for Design Systems:**
- **Perceptual uniformity**: L=70% always looks 70% light
- **Better contrast**: APCA-ready lightness calculations
- **Easier scaling**: Math operations work predictably
- **Native CSS**: `oklch()` works in all modern browsers (2023+)

## Design Bible Structure

### 1. Foundation
- Brand Identity, Design Principles
- Color System, Typography Scale
- Spacing Scale, Grid System

### 2. Components
For each component document:
- Purpose, Anatomy, Variants
- States (default, hover, active, disabled, focus)
- Responsive behavior
- Accessibility (ARIA, keyboard, screen readers)
- Code examples

### 3. Patterns
- Page Layouts, Navigation
- Forms, Data Display
- Feedback (alerts, toasts, modals)

### 4. Guidelines
- Writing (voice, tone)
- Imagery, Motion, Accessibility

→ See `references/component-documentation.md` for templates.

## CSS Organization (ITCSS)

```
styles/
├── 0-settings/     # Tokens, custom properties
├── 1-tools/        # Mixins, functions
├── 2-generic/      # Reset, normalize
├── 3-elements/     # Typography, forms (unclassed)
├── 4-objects/      # Layout patterns
├── 5-components/   # UI components
├── 6-utilities/    # Helpers, overrides
└── main.css        # Import all
```

→ See `references/css-organization.md` for BEM naming and full structure.

## Anti-Patterns to Avoid

### 1. Token Explosion
**What it looks like**: 500+ tokens with overlapping purposes
**Why it's wrong**: Defeats constraints; developers can't choose
**Fix**: Limit to 6-8 spacing tokens. If you need more, fix the scale.

### 2. Missing Semantic Layer
**What it looks like**: Components reference primitives directly
**Why it's wrong**: Can't theme, can't change brand without touching every component
**Fix**: Three-tier tokens: Primitive → Semantic → Component

### 3. Documentation Drift
**What it looks like**: Design bible says one thing, CSS does another
**Why it's wrong**: Developers stop trusting documentation
**Fix**: Generate docs from CSS comments, or use Storybook

### 4. Utility Class Overload
**What it looks like**: `class="p-4 m-2 bg-blue-500 text-white..."`
**Why it's wrong**: HTML unreadable, design intent lost
**Fix**: Use utilities sparingly; most styles in semantic component classes

### 5. Breaking the Scale
**What it looks like**: `padding: 13px;` (why 13?)
**Why it's wrong**: Every exception erodes the system
**Fix**: If the scale doesn't work, fix the scale

### 6. No Version Control
**What it looks like**: "Which button is correct?"
**Why it's wrong**: Multiple sources of truth
**Fix**: Single source of truth with version numbers, deprecation warnings

## Working Process

1. **Audit**: Review existing patterns and inconsistencies
2. **Define**: Establish tokens and foundational system
3. **Build**: Create component library with documentation
4. **Document**: Write comprehensive design bible
5. **Test**: Validate accessibility and responsiveness
6. **Deliver**: Package with examples and starter templates

## MCP Integrations

| MCP | Purpose |
|-----|---------|
| **21st.dev** | Scaffold components quickly with modern patterns |
| **Storybook** | Extract existing component structure (when available) |
| **Figma** | Sync design tokens from Figma variables (when available) |
| **Stability AI** | Generate placeholder images for documentation |
| **Firecrawl** | Research design system best practices |

## Output Deliverables

- **Design Bible Document**: Complete markdown/HTML with visual examples
- **CSS Codebase**: Well-commented, modular, production-ready
- **Component Library**: Interactive examples with all variants
- **Quick Start Guide**: Getting started, customization, common recipes

## References

→ `references/token-architecture.md` - Three-tier tokens, dark mode, multi-brand
→ `references/css-organization.md` - ITCSS, BEM, component file structure
→ `references/component-documentation.md` - Doc templates, quick reference cards

## Integrates With

- **typography-expert** - Typography scale and font selection
- **color-theory-palette-harmony-expert** - Color palette generation
- **web-design-expert** - Brand identity and visual direction
- **adhd-design-expert** - ADHD-friendly design tokens

---

*Remember: A design system is a living product that serves products.*

© curiositech · MIT · curiositech/some_claude_skills

Similar skills

All skills for Design →

From the same set180

The whole set →
tech-entrepreneur-coach-adhd tech-entrepreneur-coach-adhd is a Claude Code skill for ADHD founders moving from big tech into independent app development. It activates on startup, MVP, monetization, and side-project requests. CX Codex +1 260installs refactoring-surgeon The refactoring-surgeon skill guides small code-structure changes while keeping behavior intact. Use it to tackle code smells, duplication, or legacy code. CX Codex +1 260installs drone-cv-expert drone-cv-expert — a skill for autonomous drones and computer vision: flight control, SLAM, object detection, path planning. Activates on drone, UAV, SLAM and related terms. CX Codex +1 259installs project-management-guru-adhd project-management-guru-adhd is a Claude Code skill that helps ADHD engineers manage multiple projects, protecting hyperfocus and reducing context switches. CX Codex +1 253installs fullstack-debugger fullstack-debugger troubleshoots Next.js 15, Cloudflare Workers, and Supabase apps layer by layer. Fixes auth errors, broken RLS policies, CORS, and build failures. CX Codex +1 244installs security-auditor security-auditor runs dependency checks, finds hardcoded secrets, and flags injection or XSS risks in source code. Useful before shipping or when reviewing a pull request. CX Codex +1 243installs native-app-designer native-app-designer — a skill for iOS, Mac and web app design that skips the generic AI look. It steers the agent toward spring physics, motion timing and details that make an interface feel human. CX Codex +1 241installs large-scale-map-visualization large-scale-map-visualization — a skill for web maps carrying tens of thousands of markers. It picks clustering libraries, viewport loading, and rendering tricks that keep the browser responsive. CX Codex +1 240installs

Project sponsors

Companies that keep this analytics open