Frontend & design systems
For interfaces that grew one exception at a time. I turn scattered screens into a system: tokens, components and documentation that hold up when the team changes.
Design tokens
Color, type, spacing as one source of truth — from Figma to production.
Component libraries
Web components or framework-native, built to survive team turnover.
UI architecture
State, styling, composition: structure that scales past the third screen.
Documentation & adoption
A system nobody uses is a folder. Docs, examples, contribution rules.
on-site IT / DE
framework-agnostic by design
agreed at intake, no surprises
PROCEDURE — FIG. 2
INTAKE
30-minute call, free. You state the problem.
INVENTORY
Audit of the existing UI: what exists, what repeats, what drifts.
BUILD
Tokens first, then components — shipped incrementally, never big-bang.
HANDOVER
Docs and contribution rules. The team owns it, not me.