Docs / The Mold
How every part is made, and the checks it has to pass before it exists.
Kata — 型 — is the Japanese discipline of the form: the pattern from which things are cast, and the practice that keeps the casting true. Every KATA part is built to one production standard: same file layout, same tokens, same class grammar, same accessibility contract. The consistency is not a style guide people try to remember; it is a checklist a program enforces.
Two parts built months apart should look like they were built on the same day, by the same hand. The mold is how a library with one author keeps that promise.
Before a part ships, a checker reads its files the way a casting inspector reads a mold. Required files present. Metadata complete. No raw color anywhere — tokens only, because a hard-coded hex is a part that will not survive a theme. Every class used in the preview actually defined. Icons drawn on the 24-grid at stroke 2, from three shapes: circle, 45-degree line, rounded corner. A part that fails does not ship; the count on the homepage only ever counts parts that passed.
The checker is in the repository (check.py) and the standard is written down (KATA.md), so the mold is inspectable, not vibes.
One color is reserved: a vermillion core, #EB471F, that appears only at the center of active controls — the dot inside a checked radio, the core of an on switch, the end point of a line chart, the heart of the logo. Never on a surface, never as text, never changed by a theme. It is how you can tell a KATA part at a glance, and how the parts tell you where the action is.
Getting Started · Theming · Dark Mode · Accessibility · Installation · JavaScript · Guide: Building a Dashboard · Guide: Building a Settings Page · Guide: Building a Pricing Page · Guide: Sign-in & Account Pages · Why Vanilla · Anatomy of a Part · Coming from Tailwind · FAQ · Changelog