Give your system a point of view.
Start with the decisions people will recognize: color, type, shape, and spacing. Explore the foundations, then try a theme that feels like your product.
You’ll leave withA clear visual direction.
Shape your visual language. Build with it. Give your AI agents the context to do the same.
Your workspace is saved in this browser. Export your tokens to take them with you.Follow the six steps, or start with the part your team needs today.
Start with the decisions people will recognize: color, type, shape, and spacing. Explore the foundations, then try a theme that feels like your product.
You’ll leave withA clear visual direction.
See how global values become meaningful theme roles. Inspect both color modes, copy a value, and export CSS or a structured token file for your project.
You’ll leave withReusable values with meaningful names.
Try component states before you build. Compare the guidance, adjust a playground, and see how components work together in responsive sample pages.
You’ll leave withComponents chosen for real tasks.
Choose the rules that fit your work, explain what the agent can change, and prepare a handoff. Connect an MCP client to the hosted catalog for design-system context.
You’ll leave withAn explicit brief, with review boundaries.
Review keyboard paths, contrast, responsive layouts, and clear feedback. Use the guides to plan checks in your real product; a good-looking preview is only a starting point.
You’ll leave withEvidence for what works and what needs attention.
Explore assistant response patterns, revisit the foundations, and keep implementation decisions close to the code. Use the changelog to see what is available as the library develops.
You’ll leave withA system your team can keep improving.