Every card is a system's own out-of-the-box settings: the colour its buttons ship in, the typeface it names, the corners it cuts. Pick one and you begin where that system begins. Nothing is fixed: every value is a knob you can move a second later.
Nothing on this screen is our taste: every value was read out of the kit's own package, and the card's last line says what you get.
Saved kits
Colours, two typefaces, and how solid you want the edges. Nothing here is final, so shuffle as often as you like. The strip along the bottom is really your kit rendering, not a picture of one.
One colour is all you say. The rest is read out of what your stack publishes. Click a card to change it.
Two faces is plenty. Every one of them is a real family your stack can load, and the size below is the one everything else is measured against.
Corners, weight and the room between things. This is where a kit stops being a palette and starts having a personality.
Your app, in these values
<head>:
localhost works from here.Every value you turn lands in your app as the kit's own variables, the same way it lands in the screens. The line does nothing else: no network, no storage, and it is inert when the page is not framed by this tool. Your app runs on none of the nine? Then nothing will move here, and that is exactly what the export's skill is for.