You don't need a 400-component library. The twelve pieces that cover most screens, and how to name them so they last.

Why twelve

A small team does not need a library of hundreds. A dozen well-made components cover most screens, and they are small enough to keep consistent.

The twelve

Button, text field, select, checkbox and radio, card, list row, tabs, modal, toast, table, navigation bar and empty state. Add icons and a type scale and you can draw almost anything.

Build tokens first

Before any component, define colour, type size, spacing and radius as named values. Changing the brand later then means editing a few tokens instead of every screen.

Grow it from real work

Add a component only when a second screen needs it. A system that follows the product stays small and honest, and designers keep using it.