Shipping a design system the whole team builds on

Picking the green, naming the spacing scale, deciding if the corners are 8px or 12px, that's a fun weekend. The hard part is everything after, when the system has to leave your head and live in other people's hands.

A design system isn't a Figma library.

I used to think it was. A library just sits there, beautiful and inert, until someone chooses to care.

Make the right thing the easy thing.

What I wanted was for a teammate at 11pm, shipping a section they're unsure about, to grab the nearest tool and have it already be on-brand. Not because they read the docs, but because they didn't have to.

So I stopped writing the system as a reference and started writing it as a default. Tokens that plug in. Components that come pre-decided. A starter template you copy instead of a guideline you consult. I even packaged the whole thing so an AI could read it, so the first draft already speaks our language before a human touches it.

The measure of a design system isn't how good it looks in the file. It's how rarely anyone has to think about it.

The best compliment wasn't "this is beautiful." It was someone saying they forgot it was there.