Building a design system that scales with the team.

The temptation with any design system is to add. A new variant here, an extra spacing step there, one more shade of grey because this particular screen needed it. Each addition feels harmless in isolation, and collectively they are how a system dies — not from neglect, but from generosity.

The systems that last are ruthless about their primitives. A small set of spacing steps, a tight type scale, a handful of radii, two surfaces and one ink. Constraints at the token level mean the work above them stays coherent without anyone having to police it.

Defaults do the work

When the defaults are good, the easy path and the correct path are the same path. People reach for the token because it is closer to hand than the hard-coded value, and consistency becomes a side effect of convenience rather than a rule that has to be enforced in review.

That is the real test of a system: not how much it can express, but how rarely anyone needs to step outside it.