Design principles

Why the system works the way it does. Each one shows what to do and what not to.

Use the part, never rebuild it

A part already has its focus, disabled and loading states, and every fix reaches every screen. A copy has none of that and drifts. See Examples.

Do
The kit's Button, with its size, corner and focus ring
Don't
Rebuilt by hand: wrong size, no focus ring

A token, never a number

Change one token and every screen follows. A typed value stays behind, so two things that should match drift apart. See Theming.

Pro
Do
Both read the accent token, so they always match
Pro
Don't
Each typed its own blue, and now there are two

Space says what belongs together

Pick a gap by how two things relate, not by what looks right. A label sits close to its field and farther from the next one. See Spacing & Scale.

Do
Each label hugs its own field
Don't
Even gaps: a label floats between two fields

Shape comes from what a thing is

Controls share one corner, cards another, so each kind reads at a glance. Nobody picks a radius for one element. See Spacing & Scale.

Do
Field and button: one height, one corner
Don't
Each picked its own height and corner

Size sets the order, not weight

A bigger step says this matters more. Bold on everything says nothing. See Typography.

Billing

Your plan renews on May 4.

Do
The title is a size up; the line under it is quieter

Billing

Your plan renews on May 4.

Don't
Same size, both bold: nothing leads

Each color has one job

Accent means you can act on it. Spent on titles and labels, it stops telling you what to press. See Colors.

Team members
Do
Only the button is blue
Team members3 seats
Don't
Title, label and button are all blue

Motion is quick, and only where it helps

Each animation takes a role, not a number. Something used all day should barely move. Flip both switches. See Animation & Motion.

Do
Moves on the small role, 150ms
Don't
A typed 700ms: it lags behind the click

Every control works for every hand

Touch first, keyboard always. A control is big enough to tap, has a name a screen reader can say, and shows focus. See Form Patterns.

Do
A real button with a name and room to tap
Don't
A bare icon: too small to tap, no name, no focus