Agent skill

Design System Architect Skill for Token Exports

The design-system-architect skill builds a design system from a brand brief or existing site, then exports a Tailwind config, CSS variables and a usage document.

Install
git clone https://github.com/OneWave-AI/claude-skills.git
View on GitHub

Stars, license and last push from GitHub. Install count as reported by the open skills directory.

What is the design system architect skill?

Design-system-architect is a skill in OneWave-AI's skills repository on GitHub. From a brand brief or an existing site it builds color, type, spacing, radius, elevation and motion tokens plus component specs, then writes a Tailwind config extension, a tokens.css file and a design-system.md usage doc.

It is the claude-design-system-architect folder in OneWave-AI's skills repository. Its description says it generates a premium design system from a brand brief or an existing site, aiming for an editorial, human-crafted look rather than a template one.

What it produces

  • Color: a 50 to 900 ramp per hue, semantic tokens such as surface, text, muted, accent and border, and a dark mode set.
  • Type: a font pairing with a reason, a modular scale, and line heights, tracking and weights.
  • Space and layout: a spacing scale, container widths, grid and breakpoints.
  • Radius, border and elevation: a small consistent set.
  • Motion: duration and easing tokens, named patterns and a reduced motion stance.

What it exports

The output is real files: a Tailwind config extension or a theme block for Tailwind v4, a tokens.css file with light and dark custom properties, and a design-system.md with palette contrast values, specs and do and don't examples.

Who the skill is for

Best for

  • Starting a product or site and needing a token layer before building pages.
  • Unifying an inconsistent interface by codifying the brand into reusable tokens.
  • Developers who want contrast checked against WCAG AA for body text.

Not for

  • Brands that need purple, since the default rules avoid it unless the brand overrides.
  • Teams wanting a governance process. It builds tokens and component specs, not ownership rules.
  • Projects that do not use Tailwind or CSS variables.

For the architecture of an existing system see design-system-architecture and for governance see design-system-governance. Use design-system-audit to score what you end up with.