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.
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.
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.
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.
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.
Billing
Your plan renews on May 4.
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.
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.
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.