Design System Toolkit
brianamazzio/design-system-toolkit
Integre design systems ao Claude Code automaticamente
Ver no GitHubDois skills para Claude Code que permitem importar ou gerar um design system completo. O gerador cria um sistema a partir de uma entrevista de marca; o importador traduz um design system existente do Figma em especificação, tokens de código e guia visual sincronizado.
Instalação
npx convez-ai brianamazzio/design-system-toolkit1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Gerar design system do zero baseado em preferências de marca
- Importar design system do Figma como spec + tokens + visual guide
- Manter design system sincronizado entre Figma e código
Veredito

Ferramenta sólida e bem documentada que reduz fricção entre design e código. Recomendado para times que usam Figma ou querem padronizar componentes de UI em projetos Claude Code.
README
A tradução para o português deste README ainda está na fila.
Design System Toolkit
Two Claude Code skills for getting a design system into Claude Code — so it applies your tokens, type, and components automatically on every UI task.
| Skill | Use it when… | What it produces |
|---|---|---|
design-system-generator | You're starting from scratch and want a system created from your taste. | A brand interview → a markdown spec (docs/design-system.md) + an HTML visual style guide, and a CLAUDE.md reference. |
design-system-importer | You already have a design system (usually in Figma) and just need it translated into code + a spec Claude can read. | Extracts colors, type, spacing, radius, shadows, icons & components from Figma → markdown spec + synced code tokens + an HTML visual guide. Figma stays the source of truth. |
Rule of thumb: no system yet → generator. System already designed in Figma → importer.
Install
Three ways to install. Methods 1 and 3 let you grab one or both skills (you're copying folders, so you choose). Method 2 (marketplace) installs the whole plugin — easiest, but all-or-nothing.
A skill folder can live in ~/.claude/skills/ (available in every project) or your-project/.claude/skills/ (just that one project). The commands below use the global path — swap it for the project path if you prefer. After any manual copy, restart Claude Code so the skill appears.
Which one should I use?
- Just want it working, fine with both skills → Method 2 (marketplace)
- Comfortable in a terminal, want to choose one skill → Method 1 (git clone)
- Don't use git / want to look at the files first → Method 3 (ZIP)
1. From the command line (git clone) — pick one or both
# Get the repo
git clone https://github.com/brianamazzio/design-system-toolkit.git
# Copy the skill(s) you want into your personal skills folder:
cp -R design-system-toolkit/skills/design-system-importer ~/.claude/skills/ # the Figma importer
cp -R design-system-toolkit/skills/design-system-generator ~/.claude/skills/ # the from-scratch generator
Want just one? Run only that one cp line. Then restart Claude Code — the skill appears as /design-system-importer or /design-system-generator.
2. Inside Claude Code (marketplace) — easiest, installs both
/plugin marketplace add brianamazzio/design-system-toolkit
/plugin install design-system-toolkit
This installs the bundled plugin (both skills). Invoke them with /design-system-importer or /design-system-generator. To remove later: /plugin uninstall design-system-toolkit.
⚠️ The marketplace route can't cherry-pick a single skill — if you want only one, use method 1 or 3.
3. From a downloaded ZIP — pick one or both, no git needed
Download: on this repo, click the green Code button → Download ZIP. Or in a terminal:
curl -L https://github.com/brianamazzio/design-system-toolkit/archive/refs/heads/main.zip -o design-system-toolkit.zip
unzip design-system-toolkit.zip
Then copy the skill folder(s) from the unzipped design-system-toolkit-main/skills/ into ~/.claude/skills/:
cp -R design-system-toolkit-main/skills/design-system-importer ~/.claude/skills/
cp -R design-system-toolkit-main/skills/design-system-generator ~/.claude/skills/
Copy only the folder(s) you want, then restart Claude Code.
What each skill does
design-system-generator
Runs a structured brand interview (personality, colors, type, density, references, constraints), then generates:
design-system-visual.html— a browser-reviewable style guide showing every token.docs/design-system.md— the precise spec Claude reads each session.- A reference entry in
CLAUDE.md.
Best run before building screens, to lock the visual foundation.
design-system-importer
For systems that already exist in Figma. It:
- Pulls variables, styles, components, and icons from Figma (live via the Figma MCP, or from a token export / screenshots when offline).
- Treats Figma as canonical — when the code and Figma disagree, it fixes the code.
- Writes
docs/design-system.md, syncs your real code tokens (e.g. a Tailwind@themeblock or CSS variables) to match Figma, and rendersdesign-system-visual.html. - Keeps the markdown spec and the HTML guide in lock-step (it never updates one without the other).
Requirements
- Claude Code.
- For
design-system-importeragainst a live Figma file: the Figma MCP connected to the account that owns the file. (It can also work from a token JSON export or screenshots if you can't connect live.)
Repository layout
design-system-toolkit/
├── .claude-plugin/
│ ├── plugin.json # plugin manifest
│ └── marketplace.json # lets `/plugin marketplace add` find the plugin
├── skills/
│ ├── design-system-generator/SKILL.md
│ └── design-system-importer/SKILL.md
├── README.md
└── LICENSE
License
MIT — see LICENSE.