Engineering
Design tokens for teams of three
You do not need a platform team to keep design and code in step. You need one file, forty names and some discipline.
Priya Nandakumar 6 minute read
Design tokens have a reputation for needing a committee. Most of our clients have two engineers and a designer who also does the marketing. Here is the version that works for them.
One file
Every color, size and space lives in one file that both the design tool and the code read. Not a pipeline, not a build step with a logo. A file.
:root {
--color-paper: #f5f2ea;
--color-ink: #161512;
--space-4: 1rem;
--radius-card: 0.75rem;
}
Name the job, not the look
A token called blue-500 tells you nothing when the brand changes. A token called accent survives a rebrand. We keep two layers: a short list of raw values, and a longer list of jobs that point at them.
Forty names is plenty
Greyfield's whole check-in product runs on thirty-eight tokens. When a list grows past fifty, people stop reading it and start inventing their own. Fewer names, used everywhere, beats a complete system used nowhere.
Make the wrong thing awkward
We lint for raw color values in components. It takes ten minutes to set up and removes a whole category of review comment. Nobody needs to be told off, the build just says no.
What you get
When Greyfield added a dark theme for night-shift staff, it took an afternoon. That is the entire argument for tokens: the second theme, the rebrand and the accessibility fix all become a change in one file.