agentleFS
OneWave-AIOneWave-AI/claude-skills/design-system-generator/SKILL.md

design-system-generator

Skill378 starsChanged 56 days agoMITView on GitHub

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

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Add CSS variables. Set up :root and .dark custom properties in globals.css using the variable block in references/design-tokens.md.

    line 19
  2. Distinctive:

    Document usage and variants.

    line 23

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. 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.
  2. Add CSS variables. Set up :root and .dark custom properties in globals.css using the variable block in references/design-tokens.md.
  3. Wire the build. Add the cn helper and extend the Tailwind theme from the token files following references/config-and-utilities.md.
  4. Build base components. Implement Button, Input, and Card from references/components.md, then extend the set as the product requires.
  5. Export a barrel. Re-export every shipped component from components/ui/index.ts (see references/components.md).
  6. Document usage and variants. For each component, note its variants, sizes, props, and accessibility behavior so consumers apply it consistently.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.