Most teams build a UI kit. Then the product grows, new features get added, newMost teams build a UI kit. Then the product grows, new features get added, new
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Most teams build a UI kit. Then the product grows, new features get added, new designers join, and every screen starts looking slightly different. Not broken, just inconsistent. Death by a thousand exceptions.
When I joined a B2B product environment, there was a basic UI kit, but no tokens, naming convention, or rules for how components should behave across contexts. Design debt was building quietly.
I didn’t start by redesigning screens. I started by defining the foundation: color tokens, spacing scale, typography, component states, and naming conventions. Only after that did screens get revisited.
The result: faster feature design, one reference point for developers, and less inconsistency compounding over time. The system is now used in production across multiple products by 1,000+ daily users.
I’m a design engineer: I design the interface and write the code that ships it, so nothing gets lost in handoff. Brand identity, SaaS landing pages, product UI for AI tools, or design and build end to end.
35+ founders since 2021. Recent work includes Tessel, Flywl, Slate and Sift.