I turned the design-token spec into an arcade game.

Design tokens are one of those topics that everyone agrees matter and almost nobody enjoys learning. The W3C format is precise, which is exactly what makes it dry: $value, $type, aliases, composite types. Read straight through, it's a reference, not a journey.

A game fixes the part documentation can't. It gives the material stakes and a sequence: a sector you haven't cleared yet, a rank you're working toward, a score that tells you you're getting it. The arcade framing isn't decoration over a quiz. It's the mechanism that turns “I read about aliases” into “I used an alias to clear the wave,” which is the difference between recognizing the spec and actually knowing it.

The eight sectors are a real curriculum wearing a star chart. They're sequenced the way the spec actually has to be learned: you can't reason about aliases until you can name a single token, and you can't audit a broken library until you understand the types it's supposed to honor. Each sector earns the next one.

The arc runs from why tokens exist at all (escaping the hardcoded hellscape) all the way to wiring a tokens.json into CSS custom properties and auditing a library for spec violations: the exact decisions a real design-system engineer makes.

An educational game lives or dies on whether it feels like a real game or a worksheet in a costume. So I sweated the arcade itself: the pixel cabinet, the pilot dossier, the high score, the “insert coin” voice that carries the whole thing. The fiction has to hold, or the learning underneath it never lands.

And it's a true companion to Rudiment UI. Rudiment is the field guide to building a token-driven component library; Token Adventure is where you learn the spec those tokens are written in. Same obsession with design tokens, two very different surfaces, both built for the fun of getting the last ten percent right.