home / skills / nickcrew / claude-cortex / design-system-architecture

design-system-architecture skill

/skills/design-system-architecture

This skill helps you design scalable design systems by outlining token architecture, component APIs, and documentation strategies for modern libraries.

npx playbooks add skill nickcrew/claude-cortex --skill design-system-architecture

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

Files (1)
SKILL.md
5.8 KB
---
name: design-system-architecture
description: Build scalable design systems with design tokens, component APIs, and documentation. Use when creating or evolving component libraries.
keywords:
  - design system
  - design tokens
  - component library
  - ui components
  - theming
triggers:
  - design system
  - component library
  - design tokens
  - theme architecture
  - ui kit
---

# Design System Architecture

Comprehensive guide to building scalable design systems with proper token architecture, component APIs, and documentation strategies.

## When to Use This Skill

- Creating a new design system from scratch
- Evolving an existing component library
- Defining token architecture
- Establishing component API patterns
- Setting up design system documentation

## Token Architecture

### Three-Tier Token System

```
┌─────────────────────────────────────┐
│       Component Tokens              │  → button-primary-bg
│     (Specific to components)        │
├─────────────────────────────────────┤
│       Semantic Tokens               │  → color-action-primary
│     (Purpose-based naming)          │
├─────────────────────────────────────┤
│       Primitive Tokens              │  → blue-500
│     (Raw values)                    │
└─────────────────────────────────────┘
```

### Token Categories

```css
/* Primitive Tokens */
--color-blue-500: #3b82f6;
--spacing-4: 1rem;
--font-size-base: 16px;
--radius-md: 8px;

/* Semantic Tokens */
--color-action-primary: var(--color-blue-500);
--color-text-primary: var(--color-gray-900);
--spacing-component-gap: var(--spacing-4);

/* Component Tokens */
--button-bg: var(--color-action-primary);
--button-padding-x: var(--spacing-4);
--card-radius: var(--radius-md);
```

### Theme Support

```typescript
// tokens/themes.ts
export const lightTheme = {
  'color-bg-primary': 'var(--color-white)',
  'color-text-primary': 'var(--color-gray-900)',
  'color-border': 'var(--color-gray-200)',
}

export const darkTheme = {
  'color-bg-primary': 'var(--color-gray-900)',
  'color-text-primary': 'var(--color-gray-100)',
  'color-border': 'var(--color-gray-700)',
}
```

## Component API Patterns

### Prop API Design

```typescript
// ✅ Good: Clear, typed, with sensible defaults
interface ButtonProps {
  variant?: 'primary' | 'secondary' | 'ghost';
  size?: 'sm' | 'md' | 'lg';
  isLoading?: boolean;
  isDisabled?: boolean;
  leftIcon?: React.ReactNode;
  children: React.ReactNode;
  onClick?: () => void;
}

// ✅ With defaults
const Button = ({
  variant = 'primary',
  size = 'md',
  isLoading = false,
  isDisabled = false,
  ...props
}: ButtonProps) => { ... }
```

### Compound Component Pattern

```typescript
// Compound components for complex UIs
const Tabs = ({ children, defaultValue }) => { ... }
Tabs.List = ({ children }) => { ... }
Tabs.Tab = ({ value, children }) => { ... }
Tabs.Panel = ({ value, children }) => { ... }

// Usage
<Tabs defaultValue="tab1">
  <Tabs.List>
    <Tabs.Tab value="tab1">First</Tabs.Tab>
    <Tabs.Tab value="tab2">Second</Tabs.Tab>
  </Tabs.List>
  <Tabs.Panel value="tab1">Content 1</Tabs.Panel>
  <Tabs.Panel value="tab2">Content 2</Tabs.Panel>
</Tabs>
```

### Polymorphic Components

```typescript
// Component that can render as different elements
interface BoxProps<C extends React.ElementType> {
  as?: C;
  children?: React.ReactNode;
}

type PolymorphicProps<C extends React.ElementType> =
  BoxProps<C> & Omit<React.ComponentPropsWithoutRef<C>, keyof BoxProps<C>>;

const Box = <C extends React.ElementType = 'div'>({
  as,
  ...props
}: PolymorphicProps<C>) => {
  const Component = as || 'div';
  return <Component {...props} />;
};

// Usage
<Box as="section" className="...">Content</Box>
<Box as="button" onClick={...}>Click me</Box>
```

## Component Categories (Atomic Design)

### Atoms (Primitives)
- Button, Input, Label, Icon
- Typography (Text, Heading)
- Box, Flex, Grid (layout primitives)

### Molecules (Compositions)
- FormField (Label + Input + Error)
- SearchInput (Input + Icon + Button)
- Card (Box + padding + border)

### Organisms (Features)
- Header (Logo + Nav + UserMenu)
- DataTable (Table + Pagination + Filters)
- Modal (Overlay + Card + Actions)

## Documentation Strategy

### Component Documentation

```markdown
# Button

Buttons trigger actions or navigate users.

## Usage

\`\`\`jsx
import { Button } from '@/components/ui'

<Button variant="primary" size="md">
  Click me
</Button>
\`\`\`

## Props

| Prop | Type | Default | Description |
|------|------|---------|-------------|
| variant | 'primary' \| 'secondary' \| 'ghost' | 'primary' | Visual style |
| size | 'sm' \| 'md' \| 'lg' | 'md' | Size preset |

## Examples

### Variants
[Interactive examples]

### With Icons
[Interactive examples]

## Accessibility

- Uses `<button>` element by default
- Supports keyboard activation
- Loading state announced to screen readers
```

## Best Practices

### Design Principles
1. **Composition over configuration**: Small, composable pieces
2. **Sensible defaults**: Works out of the box
3. **Accessible by default**: a11y is not optional
4. **Type-safe APIs**: TypeScript guides usage
5. **Minimal API surface**: Only expose what's needed

### Maintenance
- Semantic versioning for breaking changes
- Deprecation warnings before removal
- Migration guides for major versions
- Automated visual regression testing

## Resources

- [Radix UI Primitives](https://www.radix-ui.com/)
- [Chakra UI Component Patterns](https://chakra-ui.com/)
- [Design Tokens Community Group](https://www.w3.org/community/design-tokens/)

Overview

This skill helps teams design and evolve scalable design systems focused on tokens, component APIs, and clear documentation. It distills a three-tier token model, component patterns (prop APIs, compound and polymorphic components), and documentation strategies to deliver consistent UI at scale. Use it to reduce visual drift, simplify theming, and create predictable developer ergonomics.

How this skill works

The skill inspects and prescribes a token architecture separated into primitives, semantic tokens, and component tokens so values can be themed and reused. It defines component API patterns—typed prop APIs, sensible defaults, compound components, and polymorphic primitives—to keep APIs minimal and flexible. Finally, it outlines documentation templates, accessibility guidance, and maintenance workflows like versioning and migration guidance.

When to use it

  • Creating a new design system from scratch
  • Evolving or refactoring an existing component library
  • Defining a token hierarchy and theme support
  • Establishing consistent component API patterns
  • Setting up component documentation and accessibility guidance

Best practices

  • Adopt a three-tier token system: primitives → semantic → component to enable theme swaps and easy overrides
  • Prefer composition over large configuration objects; build small, testable primitives
  • Provide sensible defaults and type-safe props to guide correct usage
  • Make accessibility the default: semantic elements, keyboard support, and ARIA where needed
  • Keep APIs minimal; expose only what consumers need and document edge cases
  • Use semantic versioning, deprecation warnings, and migration guides for breaking changes

Example use cases

  • Define tokens and themes for a multi-brand product with light/dark variants
  • Create a Button component with typed props, default variants, and loading/disabled states
  • Build a Tabs compound component with List/Tab/Panel subcomponents for complex UIs
  • Introduce a polymorphic Box primitive to reduce duplicate components while keeping semantics
  • Document components with usage examples, props tables, accessibility notes, and interactive demos

FAQ

What are the three token tiers and why use them?

Primitive tokens hold raw values (colors, spacing). Semantic tokens map intent to primitives (action, text). Component tokens map semantic tokens to component-specific variables. This separation makes theming and cross-product consistency easier.

When should I use a polymorphic component?

Use polymorphic components for layout primitives or small building blocks where consumers need different underlying HTML elements without duplicating component logic.