Integrations
How the library fits the rest of a stack. Only things with a real path are listed, and each one says how real that path is — nothing is marked official unless it is shipped and exercised here.
11 integrations
What the statuses mean
- Official
- Shipped and exercised in this repository.
- Supported
- Works by design, with a written path; not run against it here.
- Community
- Maintained outside this project.
- Coming soon
- Planned. Nothing to set up yet.
Frameworks
React
Every component is a React component. React and React DOM are peer dependencies, so the app brings its own.
2 setup steps
Next.js
Works with the App Router and React Server Components. Modules that need the client already carry 'use client'; the rest stay on the server.
3 setup steps
Vite
ESM only, one module per component with sideEffects declared, so Vite drops everything you do not import.
3 setup steps
Styling
Tailwind CSS
Optional. Without Tailwind, use the prebuilt stylesheet. With Tailwind v4, import the preset so the utilities are generated into your build instead of shipped twice.
2 setup steps
CSS variables
Every colour, radius and shadow is a custom property. One call derives four accent values from a single colour and writes them to the document.
2 setup steps
Design Tokens (W3C)
The token set as W3C Design Tokens data, for Figma plugins, Style Dictionary or anything else that reads the format. Dark mode ships as a $modes entry.
1 setup step
Icons
AI tooling
MCP server
A coding agent reads the real props, tokens, blocks and source over the Model Context Protocol instead of guessing them.
2 setup steps
Agent Skill
The same guidance as the MCP server, for harnesses that load skills: which component to reach for, the theming API and the house rules.
1 setup step