Mantine theme editor

React components: its variables are public, its class names are build hashes. UISandbox builds Mantine 9.5.2 from its own package and opens it in the editor: seven screens in Mantine's own components and its own defaults. Turn the brand, the type, the spacing and the corners, and every component follows. Nothing to install, nothing uploaded.

Open Mantine in the editor Try it on your own app

Mantine in the UISandbox editor: the knobs on the left, Mantine's own components on the right — Mantine as it ships, in the editor. A real screenshot.

What is read from Mantine

Version: 9.5.2
Licence: MIT
Package: @mantine/core
Runs in: React
Variables: 381 in its light mode, and its own dark mode, read from its package
Brand as it ships: #228be6
Body type: the system stack
Corners: 8px

What you take with you

Export writes Mantine's design system in Mantine's own names, starting from what you see:

theme.css: the variables, in Mantine's own names, as the knobs left them
install.md: where each file goes, step by step
MANIFEST.md: what could not be done, said rather than substituted
DESIGN.md: the design system for people and agents: colours, type, spacing, what each is for
.claude/skills/design-system/SKILL.md: for Claude Code, Cursor or Codex: build the next screen in Mantine's own classes
tokens.json: W3C design tokens, which Tokens Studio and Figma variables import

On your own app

If your app runs on Mantine, the sandbox recognises it from the rendered page and writes the design system in Mantine's names from your app's own values. What you turned on the kit comes with you. The quickest way in is the one where nothing leaves your machine: run npx uisandbox-mcp open in your project, or ask your agent to "open this app in UISandbox". How it works.