I build the foundation that keeps a product consistent as it grows - proper components, sensible token naming, and documentation your team will actually use instead of ignore. Whether you're starting clean or untangling a file that's become a mess, design systems bring order.

How I work:

🧠 Auditing what you've got. I go through your existing screens to find the inconsistencies, the eight slightly-different buttons, and the patterns worth keeping. We start from reality, not a blank slate.

🎨 Tokens that scale. A clear color, type, and spacing foundation built on primitive and semantic layers, so a single change ripples through the whole product instead of breaking it.

🧱 Components that hold up. Reusable, variant-driven components with proper states, built the way developers will actually implement them.

📐 Naming people can follow. A naming convention for layers, tokens, and components that's logical for designers and engineers.

📖 Documentation that gets read. Usage notes, do's and don'ts, and guidelines that make the system understandable.

Startups outgrowing their first Figma file

Products heading into a redesign

Cleaning up inconsistent legacy files

Setting up Code Connect for dev handoff