←
Work/Floret Design System

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

The issue

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.

Architecture

Three tiers, and nothing skips one

Components are the surface. Tokens are the spine. Nothing was drawn until this graph was locked.

Tier 01

Primitives

Raw values — hex codes, px steps, font sizes. Never referenced directly by components.

blue-100blue-500blue-900indigo-500teal-500space-4 · 4pxspace-16 · 16pxradius-md · 8pxfont-size-b16 · 16px
Tier 02

Semantic

Role-based — describes intent, not appearance. Swappable across Light & Dark modes.

color.action.primarycolor.text.defaultcolor.surface.mutedcolor.status.dangerspace.inset.mdradius.controltype.body.md
Tier 03

Component

The binding — each component consumes only component tokens, never reaches past them.

button.primary.bgbutton.primary.textbutton.primary.radiusinput.border.restinput.border.focuscard.surfacecard.shadow
Every reference points exactly one tier up. A component that reaches past its own layer to a raw hex is the bug — it looks fine until the first dark mode or rebrand.
Components

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.

Button · intent × state
Save changesprimary · rest
Cancelsecondary · rest
View moreghost · rest
Deletedanger · rest
Submitprimary · disabled
Saving…primary · loading
A designer picks one Button and flips three properties — intent, size, state. Not one of these is a separate component.
Inventory

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.

AccordionAction Tool BarAlertsApp HeaderAttributesAuto CompleteAvatarBadgeBreadcrumbButtonButton GroupsButton DropdownCalendarCardsCheckbox / RadioChipClipboardCode EditorColor PickerCombo BoxCommentContainerContent MenuData GridData VisualizationDialogDrag ItemDropdown ListDropdown TreeExecutive SummaryFile UploaderFormInput MaskInput SearchKey Value PairLabelLinksList BoxList ViewLoadersMenu BarMulti SelectNumber InputPaginationPhone Number InputProgress BarRange SliderRich Text EditorSchedulerSide BarSkeletonSpinnerStatus BadgeStatus IndicatorStepperTabsTagsText AreaText ContentTicketsTileTime InputTimelineToastToggleTool Bar
Every one documented with its variants, properties, the tokens it consumes and its accessibility notes. Five squads pull from this one library — a brand change ripples through all of it.
Handoff

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.

Outcome

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.”

Jagadeesh SJ · Design Head, Light & Wonder

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?