yBlocks

Colour and elevation tokens, the icon rules, the five feedback tones, the data pipeline, the auth seam. Each is written down once and given a page that demonstrates it — and nothing above this layer is allowed to re-decide any of them.

The unit is the family, not the package: one family, one page, tabs that walk its members. Two engines coexist underneath — CSS shells from shadcn, behaviour from Base UI — behind a single seam, so a page author only ever learns one vocabulary.

Cards replicated from designs in the wild, translated into these tokens, and upgraded wherever the original settled for ordinary. Each one registers exactly once; the gallery and its domain routes derive themselves from that entry.

Every page belongs to a class, and a class gets its law before it gets a page: a kit whose defaults enforce the layout, a spec document, and a living example. Building a page means filling slots — the chrome is not yours to write.

Whole products rather than component demos — a CRM, a task tracker, a grid control room, a wealth dashboard. They are the proof that the layers below actually compose, which is why each one lists the cards it is made of.

Finished knowledge products with shareable URLs: animated diagrams typed by the shape of their data rather than their topic, a ten-lesson curriculum, and the films whose motion was measured frame by frame to build the spring vocabulary.

Where a thing is tried before it is legislated: motion studios, a map lab, generators, a physics toy. An experiment that matures graduates out of here into a law; one that never does stays here, honestly labelled as a toy.