Free No sign-up Nine real kits
Try nine real UI kits on the same screen, in your own colours, and find out which one actually fits before you build on it. Then export the one you kept, or the combination.
One at a time here. In the tool you can put six side by side and click any element to see all six versions of it at once.
You cannot tell which design system fits by reading its homepage.
So try all nine, on one screen, in your own colours.
Read, never guessed
Every frame above is holding the same colour, , and
the same corner, , each in the kit's own name for it. Four bands
make a stack: behaviour, an engine, tokens, components. Pick a row and the preview follows;
the card reads that kit's whole answer out of its package.
| System | Runs in | Takes it as | Fills |
|---|
Five of the nine name no framework at all. That is read from what each package demands of the app around it, not from what its homepage says.
Deriving a theme is how the best teams work: Linear generates its themes from a base colour, over a hundred variables and none picked by hand. Here the same derivation answers in nine vocabularies at once.
Being straight with you
Three things this will never become, and five things it could not do to the values on this page. The second list is generated by the run itself, so it changes when the kits do.
Straight out of a real MANIFEST.md
Every line of that is generated, not written. A package that quietly leaves out a third of a theme is worse than one that says so.
What you get
Not a screenshot and not a palette, but the files each kit expects, plus the one thing nobody else prints.
The brief is in there because agents write more of the code now, and an agent keeps a design system only as well as it is written down. Linear makes the same point about why it rebuilt its styling.
One colour is enough to begin, and the rest comes from whatever you switched on. Nothing to install to find out.
Free and open source. No accounts, no telemetry, no lock-in.