Skip to main content
skill CX Codex

design-system · oakoss — Claude Code skill: what it does, how to install

This skill structures design systems around tokens, themes, and component APIs. Use it for dark mode, CVA variants, accessibility checks, and Storybook docs.

MIT 160 installs ★ 29 updated 2026-08-17

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

What design-system does

The skill organizes a design system into primitive, semantic, and component token tiers. It covers semantic token swaps for dark mode, runtime CSS custom properties for brand themes, and component variants built with cva() and VariantProps. Compound components use sub-parts and shared context instead of putting every option into one configuration object.

Its reference material also covers Radix primitives with Tailwind classes, Tailwind v4’s @theme block, Style Dictionary output, Storybook autodocs, and accessibility work. Focus indicators, prefers-reduced-motion, WCAG contrast, SSR theme-flash prevention, and versioning rules are included. Hardcoded hex or px values inside component files are treated as a mistake because visual values should come from semantic or component tokens.

The skill maps larger tasks to agents: Explore for finding hardcoded values, Task for migrations and accessibility review, and Plan for multi-brand architecture. Tools such as Storybook or Style Dictionary are relevant when those workflows are part of the project.

What it helps with

  • separate primitive, semantic, and component design tokens
  • build dark mode and multi-brand themes with CSS custom properties
  • define typed component variants with cva() and VariantProps
  • audit focus, contrast, and reduced-motion behavior
  • document components in Storybook and version their APIs

Example prompts for the agent

  • Split the current colors and spacing into primitive, semantic, and component token layers.
  • Design a dark-mode and multi-brand theme using data-theme and CSS custom properties.
  • Review these components for keyboard focus, WCAG contrast, and prefers-reduced-motion support.

How to install design-system

1Skills CLI (Vercel)

npx skills add oakoss/agent-skills --skill design-system -a claude-code

2Manually: put the files in place

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

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

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

Questions about design-system

How do I install design-system in Claude Code?

Run npx skills add oakoss/agent-skills --skill design-system -a claude-code, then check ~/.claude/skills/design-system/SKILL.md.

What does design-system do?

It helps plan token hierarchies, theming, component APIs, accessibility foundations, and documentation workflows using tools such as cva(), Radix, and Storybook.

How should the token layers be ordered?

Keep the flow primitive → semantic → component. Components should consume semantic tokens so themes can change without embedding raw visual values in component code.

Source text

SKILL.md · MIT
---
name: design-system
description: 'Builds scalable design systems with tokens, theming, and component architecture. Use when creating design token hierarchies, theming systems, component variant patterns, or accessibility foundations. Use for design tokens, CVA variants, dark mode, multi-brand theming, Radix headless UI, Storybook documentation, and governance.'
license: MIT
metadata:
  author: oakoss
  version: '1.0'
  source: 'https://designtokens.org'
user-invocable: false
---

# Design System

## Overview

Single source of truth for visual consistency at scale — a shared language between design and engineering. Covers token architecture, theming infrastructure, component API patterns, accessibility compliance, and governance workflows.

Design systems are not component libraries alone. They unify tokens, patterns, documentation, and contribution processes so teams build once and maintain once.

## Quick Reference

| Area                | Pattern                                 | Key Points                                                           |
| ------------------- | --------------------------------------- | -------------------------------------------------------------------- |
| Token hierarchy     | Primitive > Semantic > Component        | Never reference primitives in components; semantic layer is themable |
| Dark mode           | Swap semantic tokens via `data-theme`   | Use off-white/dark-gray, not pure white/black                        |
| Multi-brand theming | Override semantic tokens per brand      | Apply via CSS custom properties at runtime                           |
| Tailwind v4         | `@theme` block in CSS (no config file)  | CSS-first configuration replaces `tailwind.config.js`                |
| CVA variants        | `cva()` for variant + size combinations | Type-safe with `VariantProps`; pair with `cn()` utility              |
| Compound components | `Modal.Header`, `Modal.Body` sub-parts  | Composition over configuration; shared context for implicit state    |
| Headless UI         | Radix primitives + Tailwind classes     | Accessibility built-in; bring your own styles                        |
| Focus management    | `focus-visible:ring-2` on all controls  | 2px solid outline with offset; visible on keyboard only              |
| Reduced motion      | `prefers-reduced-motion` media query    | Near-zero duration for all transitions and animations                |
| Style Dictionary    | JSON tokens to CSS/iOS/Android          | `outputReferences: true` preserves token chain                       |
| Storybook           | Stories + autodocs + a11y addon         | Visual documentation with accessibility audit built in               |
| Governance          | Semver for tokens and components        | Breaking = removed props/tokens; minor = new additions               |

## Common Mistakes

| Mistake                                       | Correct Pattern                                                          |
| --------------------------------------------- | ------------------------------------------------------------------------ |
| Primitive tokens in components (`blue-500`)   | Reference semantic tokens (`interactive-primary`) that map to primitives |
| Skipping focus states on interactive elements | Add `focus-visible:ring-2` on every button, link, and input              |
| Body text set to `gray-400`                   | Use `gray-600` or darker to meet 4.5:1 WCAG AA contrast                  |
| Circular token references between layers      | Tokens flow one direction: primitive > semantic > component              |
| Ignoring `prefers-reduced-motion`             | Wrap all animations in a reduced-motion media query                      |
| Using `scale()` transforms for hover          | Use `translateY(-1px)` and shadow changes to avoid layout shift          |
| Hardcoded hex/px values in component files    | All visual values come from semantic or component tokens                 |
| Deep CSS nesting for theme overrides          | Override CSS custom properties at the semantic layer                     |
| Theme flash on page load (FOUC)               | Inject synchronous theme script in `<head>` before body renders          |
| Flat token list without layers                | Organize into primitive, semantic, and component tiers                   |

## Delegation

- **Audit codebase for hardcoded values that should be tokens**: Use `Explore` agent
- **Migrate a component library to a token-based design system**: Use `Task` agent
- **Plan a multi-brand theming architecture**: Use `Plan` agent
- **Review accessibility compliance across components**: Use `Task` agent

> If the `motion` skill is available, delegate animation token integration and motion design patterns to it.

## References

- [Design Tokens](references/design-tokens.md) — three-layer hierarchy, CSS custom properties, TypeScript definitions, naming conventions
- [Theming](references/theming.md) — dark mode, theme provider, multi-brand, Tailwind v4, SSR flash prevention
- [Color and Typography](references/color-and-typography.md) — 60-30-10 rule, contrast requirements, type scale, fluid typography
- [Component Architecture](references/component-architecture.md) — CVA variants, compound components, headless UI, polymorphic rendering
- [Accessibility](references/accessibility.md) — WCAG compliance, keyboard navigation, ARIA patterns, screen reader testing
- [Motion and Layout](references/motion-and-layout.md) — animation tokens, reduced motion, spacing grid, elevation system
- [Tooling](references/tooling.md) — Style Dictionary, Storybook, component testing, visual regression
- [Governance](references/governance.md) — versioning, deprecation, contribution workflow, component lifecycle
- [Troubleshooting](references/troubleshooting.md) — common issues, dark mode fixes, token sprawl, pre-delivery checklist

© oakoss · MIT · oakoss/agent-skills

Similar skills

All skills for Frontend and UI →

design-system by other authors comes first.

design-system claudekit The design-system skill builds design tokens, component specs, and presentation slides. Use it when an interface and its slides need to follow one visual system. CX Codex +1 54,500installs design-system affaan-m Builds a design system out of the styles already in your repo, or audits them: tokens, a ten-point UI score, and a check for generic AI styling. CX Codex +1 6,800installs design-system official anthropics A skill for Claude Code, Cursor, Codex, and three other platforms that audits design systems for inconsistencies, generates component docs, and drafts new patterns. Triggered with /design-system audit, document, or extend. CX Codex +1 4,700installs design-system Donchitos design-system walks one game system through every required GDD section and cross-references its dependencies. Useful when a design doc grows faster than you can keep it straight. CX Codex +1 731installs design-system daveebbelaar The design-system Claude Code skill organizes a macOS app’s accent color and design tokens. It activates for requests about themes, shared screen styles, or a style guide. CX Codex +1 1,000installs design-system-patterns Seth Hobson The design-system-patterns skill for Claude Code covers token architecture, theming, and component patterns. It activates for token creation, theme switching, and component-library foundations. CX Codex +1 15,953installs design-system-documenter curiositech design-system-documenter converts raw token files into developer documentation featuring reference tables, implementation code, and WCAG contrast checks. CX Codex +1 165installs design-system-engineer josstei design-system-engineer architects design token hierarchies, writes component API contracts, and wires theme switching pipelines without hardcoded styling values. CX Codex ★ 489repo stars design-systems Mindrally design-systems walks your agent through design tokens, a component library and accessibility rules in one project. CX Codex +1 956installs Design System taste f Design System taste — a prompt for ChatGPT that enforces pragmatic design system standards, tokens, accessibility, and component architecture. GP ChatGPT ★ 178,201repo stars design-system-creation secondsky design-system-creation — a skill that walks the agent through building a design system: tokens, typography, components and their docs. Useful when UI standards need to be settled before code. CX Codex +1 512installs

From the same set106

The whole set →

Project sponsors

Companies that keep this analytics open