Floret Design System
Five squads, six libraries, seven different blues. I built the token architecture that pulled them into one voice.
Light & Wonder · in-house
Seven blues and no source of truth
Light & Wonder had grown by acquisition, every squad inheriting its own Figma file. The audit found 14 button variants, 9 input styles and 7 distinct blues across six libraries.
One designer maintaining it, five teams adopting it, and it had to survive being handed over.
Three tiers, and nothing skips one
Components are the surface. Tokens are the spine. Nothing was drawn until this graph was locked.
Primitives
Raw values — hex codes, px steps, font sizes. Never referenced directly by components.
Semantic
Role-based — describes intent, not appearance. Swappable across Light & Dark modes.
Component
The binding — each component consumes only component tokens, never reaches past them.
One button, not thirty
State and intent are variants; size and layout are properties. The alternative — Button_Primary_Large_Hover as its own component — is thirty files.
90+ components. One naming convention. Zero drift.
Accordion to Toolbar, all built from three parts: a Variable for the value, a Variant for state, a Property for intent.
The token file is the spec
The graph exports as JSON in Style Dictionary format, so engineering consumes the source designers edit. No redlines, no drift.
Six libraries became one
90+ components, 180+ primitive variables, light and dark from day one. Spec annotation disappeared; handoff went roughly twice as fast (team estimate, not instrumented).
“[He] built the foundation of our design system. The structure has held up well enough that we're standardising our upcoming products on it.”
Engineering signed off on the naming convention in writing before anything published — renaming a token later would have broken the map already in the codebase.
Want the reasoning behind each decision, and what I turned down?