Design systems
A design system is only worth building if it gets used, so each one was built to be adopted, not just delivered.
Why it mattered
Every client arrived with the same symptom: designers picking hex codes by eye, developers hard-coding them, dark mode and mobile treated as afterthoughts, and every screen slightly different from the last.
Who we designed for
The designer
Wants the right variable in seconds, a way to flip a frame to dark mode, and components with states already drawn.
The developer
Needs a one-to-one mapping from design variable to CSS token, padding values per component and a place to raise mismatches.
The brand owner
Needs to know what is allowed, what is not, and why, on a page they can hand to a vendor.
Where it got stuck
Sixty-plus near-identical colors in one product.
Dark mode failing contrast because it was derived by inversion.
Components that looked finished but had no hover, disabled or error state.
Guidelines nobody read because they were long and unreasoned.
The decisions
Name tokens by purpose
“primary-button-hover” survives a rebrand; “indigo-600” does not.
Derive dark mode, don’t invert it
The dark ramp was built from a documented recipe so surfaces read cool and accents keep contrast.
Ration the exceptions
Gradients are allowed on the logo and promotional buttons only.
QA is part of the system
Gaps between design and build are treated as system content. Fixes go into the library, not one screen.
Brand is a system too
Brand words, palettes, type, logo options with reasoning, and website IA live in one document.
Write the “why”
Every rule carries a reason. People follow rules they understand and know are current.