Design Systems
Build the shared foundations that help your team move faster with more consistency and less rework.
Build the shared foundations that help your team move faster with more consistency and less rework.

A good design system isn't a deliverable. It's a working agreement between design and engineering. I help teams build systems that match the size and pace of their product, not someone else's.
Most teams don't need a Material-scale system. They need a clear set of components, tokens and rules they'll actually reach for. I'd help you build that, not the fantasy version.
I work in Figma and React (often Tailwind), so the system stays in sync between design files and the codebase. Components match. Tokens match. Naming matches.
A system only works if the team uses it. I focus as much on documentation, examples and migration as I do on the components themselves, so the system actually sticks.
The best design systems disappear into the work. Designers reach for the right component without thinking; engineers ship without guessing. That's the goal.