mcpbeat

Design System Generator

onewave-ai/design-system-generator

Create design systems with tokens, components, and documentation. Use when building design systems, creating component libraries, or establishing design tokens.

3k tokens
context cost
the whole folder, loaded on every use
4
files
instructions only
0
copies elsewhere
how many repositories repackaged it
235
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/OneWave-AI/claude-skills --skill design-system-generator

The instruction itself

3 sections, as written by the author

Design System Generator

Generate a token-driven design system: tokens, base components, build config, and documentation.

Contents

  • references/design-tokens.md — color, typography, spacing, shadow, and radius token files plus CSS variable setup.
  • references/components.md — Button, Input, Card implementations and the component barrel index.
  • references/config-and-utilities.md — Tailwind config and the cn class-merge helper.

Workflow

  • Define design tokens. Create tokens/ with colors, typography, spacing, and effects (shadows, radii) per references/design-tokens.md. Replace the reference values with the project brand palette.
  • Add CSS variables. Set up :root and .dark custom properties in globals.css using the variable block in references/design-tokens.md.
  • Wire the build. Add the cn helper and extend the Tailwind theme from the token files following references/config-and-utilities.md.
  • Build base components. Implement Button, Input, and Card from references/components.md, then extend the set as the product requires.
  • Export a barrel. Re-export every shipped component from components/ui/index.ts (see references/components.md).
  • Document usage and variants. For each component, note its variants, sizes, props, and accessibility behavior so consumers apply it consistently.

How to use it

Copy the folder

Take onewave-ai/design-system-generator from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.