Design systems for small teams

Design systems have a reputation for being heavy. For a small team, the goal is not exhaustive documentation, it is a shared language that lets everyone make consistent decisions quickly.

Tokens before components

We start with color, spacing, and type tokens. Once those are named and theme aware, components almost design themselves and dark mode becomes a switch rather than a project.

• Name colors by role, not by value, so themes are trivial to swap.
• Keep one spacing scale and use it everywhere.
• Document intent, not pixels.

Consistency is a feature. Users feel it even when they cannot name it.