Skip to main content
skill CX Codex

claude-design-system-architect — Claude Code skill: what it does

claude-design-system-architect is a Claude Code skill that turns a brand brief or existing site into reusable design tokens, component specs, and project files. It defines shared rules for a new product or inconsistent UI.

MIT 172 installs ★ 440 updated 2026-10-20

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

What claude-design-system-architect does

The skill starts by gathering brand cues: the intended personality, audience, existing visual assets, and references to avoid. It then defines color and type tokens, spacing and radius scales, motion rules, and component specs with states and variants.

The handoff includes a tailwind.config extension or @theme setup for Tailwind v4, tokens.css for light and dark themes, and a design-system.md guide. The guide covers contrast and component usage. The system calls for WCAG AA body-text contrast and reduced-motion support. Purple and emoji are excluded by default unless the brand calls for them, so mention those preferences in the brief if they matter.

What it helps with

  • derive design tokens from a brand brief
  • bring an existing site's colors and type into one system
  • define states for buttons, inputs, and modals
  • export Tailwind settings and CSS custom properties
  • document reusable interface rules

Example prompts for the agent

  • Create a design system for this product from the attached brand brief.
  • Review this site and define tokens for its colors, typography, and spacing.
  • Specify the components and export the system as tailwind.config, tokens.css, and design-system.md.

How to install claude-design-system-architect

1Skills CLI (Vercel)

npx skills add OneWave-AI/claude-skills --skill claude-design-system-architect -a claude-code

2Manually: put the files in place

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

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

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

Questions about claude-design-system-architect

How do I install claude-design-system-architect in Claude Code?

Run npx skills add OneWave-AI/claude-skills --skill claude-design-system-architect -a claude-code. The skill file is installed at ~/.claude/skills/claude-design-system-architect/SKILL.md.

What does claude-design-system-architect do?

It turns a brand brief or an existing site into design tokens, component specifications, and project files. Its exports include Tailwind configuration, CSS custom properties, and a usage guide.

Which files does the skill produce?

It creates a tailwind.config extension or @theme setup for Tailwind v4, tokens.css for light and dark themes, and a design-system.md guide.

Source text

SKILL.md · MIT
---
name: claude-design-system-architect
description: Generate a complete, premium design system from a brand brief or an existing site — color tokens, type scale, spacing/radius/elevation, motion language, and component specs — exported as Tailwind config, CSS variables, and a usage doc. Built to look editorial and human-crafted, not template-generated. Use when starting a new product/site, unifying an inconsistent UI, or codifying a brand into reusable tokens.
tools: Read, Write, Bash, Glob, Grep, WebSearch, WebFetch, Agent
model: inherit
---

# Claude Design System Architect

A design system is the difference between a site that looks bespoke and one that looks like every other AI-generated landing page. This skill builds the token layer and component language that makes everything downstream look intentional — then exports it in the formats your stack actually uses.

Pairs with `claude-landing-composer` (which consumes these tokens to build pages) and `claude-design-critic` (which audits against them).

## Step 1 — Establish the brand inputs

From a brief, an existing site (WebFetch / screenshots), or a few reference sites the user likes:
- **Personality** — 3–5 adjectives (e.g. "warm, editorial, confident, calm"). These drive every later decision.
- **Audience & context** — who uses it, on what device, in what mood.
- **Existing equity** — logo, locked colors, fonts already in use.
- **Anti-references** — what it must NOT look like.

### Defaults & house rules
Unless the brand explicitly overrides:
- **No purple** anywhere in the palette.
- **No emoji** in UI — use an icon set (Lucide / Heroicons) and specify it as a token.
- Lean toward **warm / earth tones** (sand, terracotta, clay) and consider a **dark surface** option.
- Motion is part of the system, not an afterthought.

## Step 2 — Build the tokens

Design each layer deliberately and document the *why*:
- **Color** — a real ramp (50–900) per hue, semantic tokens (`surface`, `text`, `muted`, `accent`, `border`, `success`/`warn`/`danger`), and verified contrast (WCAG AA min for body text). Include a dark mode set. No arbitrary hexes scattered later — everything maps to a token.
- **Type** — a font pairing with rationale, a modular scale (not random px), line-heights and tracking per size, and weights. Prefer characterful, legible pairings over the default system stack that screams "AI made this."
- **Space & layout** — a spacing scale, container widths, grid, breakpoints. Generous, asymmetric whitespace reads premium; cramped uniform padding reads generated.
- **Radius / border / elevation** — a small, consistent set. Shadows that match the brand's weight (soft for warm brands, crisp for technical ones).
- **Motion** — duration + easing tokens, named patterns (entrance, emphasis, transition), and a reduced-motion stance. This is what makes it feel alive.

## Step 3 — Specify components

For the core set (button, input, card, nav, section, badge, modal), specify variants, states (hover/focus/active/disabled), sizing, and accessibility notes — all expressed in the tokens above, never one-off values.

## Step 4 — Export

Produce real files, not prose:
- `tailwind.config` extension (or `@theme` for Tailwind v4) wiring every token.
- `tokens.css` — CSS custom properties (light + dark).
- `design-system.md` — the usage doc: palette with hexes + contrast, type scale, spacing, motion, component specs, and **do/don't** examples that call out the AI-tell patterns to avoid.

## Step 5 — Hand off
End with a one-screen summary and the next move: `claude-landing-composer` to build pages on these tokens, or `claude-design-critic` to retrofit an existing UI onto them.

## What separates premium from generated (bake this in)
- Intentional, restrained palette — not 6 competing accent colors.
- A real type scale and characterful fonts — not default sans at 3 sizes.
- Asymmetric, generous whitespace — not uniform padding everywhere.
- Motion with personality — not the same fade-up on every element.
- One confident accent — not rainbow gradients (and never purple-by-default).

## Guardrails recap
Every value is a token, nothing arbitrary · contrast meets AA · dark mode + reduced-motion included · no purple / no emoji unless the brand demands it · export real config files, not descriptions.

© OneWave-AI · MIT · OneWave-AI/claude-skills

Similar skills

All skills for Design →

From the same set185

The whole set →
scout-pro scout-pro scans conversation history, verifies installed tools, and builds multi-skill chains tailored to your current development task. CX Codex +1 244installs hyperframes-ad-director hyperframes-ad-director turns a marketing brief into a finished short-form video ad built in HyperFrames: hook, script, storyboard, HTML composition, captions, and voiceover. CX Codex +1 185installs claude-design-critic The claude-design-critic skill reviews a website or UI for generic design and copy, then ranks concrete fixes. Use it after generating a frontend or when a page feels bland. CX Codex +1 184installs claude-landing-composer claude-landing-composer builds custom Next.js landing pages with Tailwind v4 and Motion animations. Useful when you need ready-to-ship marketing sections without typical AI templates. CX Codex +1 178installs prospect-panel-simulator prospect-panel-simulator is a skill that simulates buyer reactions to sales and marketing materials before they go live, surfacing objections and likely next actions. CX Codex +1 164installs customer-panel-of-experts customer-panel-of-experts assembles a panel of buyer personas to debate product changes, price hikes, or launches before committing resources. CX Codex +1 162installs icp-deep-scanner The icp-deep-scanner skill turns data from connected tools into an Ideal Customer Profile and a persona library. Use it when you need to refresh your ICP or build buyer personas from actual data, not guesses. CX Codex +1 161installs product-launch-war-room product-launch-war-room is a Claude Code skill that tests a launch plan against expert and customer viewpoints, then returns a decision and rollout steps. Run it for a product launch, repricing, or repositioning. CX Codex +1 159installs

Project sponsors

Companies that keep this analytics open