A Figma design system that mirrors the codebase: tokens first, then components, then screens
Most design systems die the same way: Figma says 44 and the code says 42, and nobody notices until someone builds on top of the wrong one. On Acervo, where the code is written by agents at speed, that drift would have been fatal within a week. So the system was set up to make drift expensive to introduce and cheap to catch.
One source, three files, one direction
Tokens is the source: colour, type, spacing, radii, shadows. Components consumes Tokens and publishes the library. Screens consume Components. No file skips a link, and no layer redefines a value from above. When the library was started from a kit, the kit's six colour collections were kept only as a translation table: every variable resolves to a token within two hops, with no literals and no dead ends, and that is measured by a script, not by looking.
The code reads tokens by script
A script exports the token file to CSS variables and writes the token version it exported from into the header of the CSS. Lint runs the same script in check mode: if the exported CSS does not match the current tokens, the build is red. A second check fails on any raw value in a component (a hex, a pixel size that is not a token), and a third measures contrast on the rendered page, not on declared pairs, because a utility that merges class names once dropped a colour silently and the primary button rendered ink on ink while every declared pair passed.
Figma traps that only show in numbers
Everything that went wrong in Figma shared one shape: the component looked right and what rendered was wrong. Fixing a master does not fix instances that were resized by hand; after correcting two components, 192 instances were still off size and pointed at the right master. Cloning a variant drops the property bindings of its layers, so the instance holds the right text and nothing displays it. Binding a colour variable to a paint built in black keeps the literal black. None of these are visible in a screenshot. All are visible by reading a number, so the design agent's mandate is: measure before, change, measure after, and report with node ids.
Who owns the library
A design agent, continuously, with one limit: it corrects, it does not design. If a value can be pointed at (the code, a verified screen), the agent applies it. If a value would have to be invented, it is escalated as a decision with a measurement and a recommendation. That line kept the library honest when a component was built at 56 pixels "because it felt like garage mode" and nobody could say where the 56 came from. The ticket said 44.
What it bought
Twenty six components in the library, every screen built from them, a light and a dark mode from the same tokens, and a brand that an agent cannot drift from by accident. More in the brand chapter of the Acervo case, and the service is UX and product design consulting.
Part of the series: AI agent teams for software development. The checks that make "green" mean something: Why a green check is not proof.
Working on a design problem like this?
Research, flows, interface and design systems are the hands-on part of my work. Discuss a design problem → Or email me.