Get the FREE Ultimate OpenClaw Setup Guide →

design-system-management

npx machina-cli add skill anthropics/knowledge-work-plugins/design-system-management --openclaw
Files (1)
SKILL.md
1.4 KB

Design System Management

Help build, maintain, and evolve design systems.

Components of a Design System

Design Tokens

Atomic values that define the visual language:

  • Colors (brand, semantic, neutral)
  • Typography (scale, weights, line heights)
  • Spacing (scale, component padding)
  • Borders (radius, width)
  • Shadows (elevation levels)
  • Motion (durations, easings)

Components

Reusable UI elements with defined:

  • Variants (primary, secondary, ghost)
  • States (default, hover, active, disabled, loading, error)
  • Sizes (sm, md, lg)
  • Behavior (interactions, animations)
  • Accessibility (ARIA, keyboard)

Patterns

Common UI solutions combining components:

  • Forms (input groups, validation, submission)
  • Navigation (sidebar, tabs, breadcrumbs)
  • Data display (tables, cards, lists)
  • Feedback (toasts, modals, inline messages)

Principles

  1. Consistency over creativity — The system exists so teams don't reinvent the wheel
  2. Flexibility within constraints — Components should be composable, not rigid
  3. Document everything — If it's not documented, it doesn't exist
  4. Version and migrate — Breaking changes need migration paths

Source

git clone https://github.com/anthropics/knowledge-work-plugins/blob/main/design/skills/design-system-management/SKILL.mdView on GitHub

Overview

Design System Management helps teams build, maintain, and evolve design systems by organizing tokens, components, and patterns. It emphasizes consistency through a single source of truth, with clear guidelines and migration paths for breaking changes.

How This Skill Works

Tokens define the visual language (colors, typography, spacing, borders, shadows, motion). Components expose reusable UI with variants, states, sizes, and accessibility considerations. Patterns combine components into common solutions and are documented as the living source for design decisions.

When to Use It

  • Starting a new design system or expanding an existing one
  • Maintaining brand consistency across web, mobile, and apps
  • Introducing or updating design tokens, components, or patterns with a migration plan
  • Documenting usage guidelines and accessibility requirements
  • Auditing and governance to prevent divergence and ensure version control

Quick Start

  1. Step 1: Inventory tokens (colors, typography, spacing) and define a design language
  2. Step 2: Create reusable components with variants, states, and accessibility
  3. Step 3: Publish patterns in a living style guide and establish versioning and migration plans

Best Practices

  • Define a single source of truth for tokens
  • Version tokens and components; plan migrations
  • Document every token, component variant, and pattern
  • Design for accessibility (ARIA, contrast) from the start
  • Governance: roles, contributions, and deprecation policy

Example Use Cases

  • Unifying color, typography, and spacing tokens across web and mobile apps
  • Building a component library with primary/secondary/ghost variants and interaction states
  • Documenting patterns for forms, navigation, and data display
  • Publishing a living style guide and pattern library
  • Performing token audits to ensure brand and accessibility compliance

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers