04 · SleekFlow · 2022 — 2025
Design System.
A system isn't a library — it's an agreement. I focused on the agreement.
Client
SleekFlow
Role
Systems lead
Year
2022 — 2025
Focus
Systems thinkingTokensGovernance
Context
Multiple squads, multiple platforms, one brand. Components drifted, contributions stalled, naming was ad hoc.
Problem
No shared language between design and engineering. No path for contribution. No way to measure adoption.
Approach
- 01
Introduced semantic tokens and a small, stable primitive layer.
- 02
Wrote contribution and deprecation rituals that engineering co-owned.
- 03
Built a living docs site that mirrored the codebase 1:1.
Outcome
Shipping velocity improved as squads stopped rebuilding the same patterns. Read the deeper write-up →