72 tools
The token, spec, and handoff system itself. Working with a design system is not this shelf.
Storybook-like docs for Vue
OSS shared libraries & tokens in Penpot
DTCG-native design-token build system (CSS, Tailwind v4, Swift, Kotlin outputs)
Framework-agnostic runtime theming + design-token engine with Figma sync ambitions
Enterprise multi-brand token system layered on Style Dictionary + Figma Variables
Local Figma MCP with semantic design graph, web import, and verification loop (no REST quotas)
Local MCP that compresses Figma Desktop context into token-efficient JSX handoffs for LLMs
Brand / design-system hub for guidelines, assets, and governance
Mac color-system app: WCAG/APCA + export tokens to Figma/SCSS/SwiftUI
Design skills, UI prompts, brand kits, and MCP design systems so Codex, Claude, and Cursor keep typography, color, and
Toolkit by Tailwind/Refactoring UI authors for non-embarrassing agent UI
Screenshot loved UI → AI taste profile for coding assistants
Showing 25–36 of 72
Design systems fail in the gap between the file and the repo. This shelf is tokens, specs, documentation, converters, and handoff utilities that keep design and engineering looking at the same values. If you are still pasting hex codes into Slack, you want something here.
Converters and file-handoff utilities are a filter because they are a different job from a token pipeline. Use that filter when you need to move a file between tools. Stay on the parent view when you want sources of truth, docs sites, and spec tooling.
Featured picks are the ones we would install before a system grows past a dozen components. The grid includes smaller converters that only matter once a quarter and still save a miserable afternoon. Read why-notable; a lot of these products look similar on a landing page.
This is not a component library shelf. If you need a Button to install, go to UI kits. If you need Figma-to-React, go to design-to-code. If you need the contract between those worlds, stay here.