Tokens: the smallest layer

{
  "color-brand": "#1c6e63",
  "space-unit": "8px",
  "radius-default": "4px"
}

Tokens are the raw values - colour, spacing, radius, type scale - kept in one place so a rebrand or a theme change is a data update, not a search-and-replace across hundreds of files.

Components: built from tokens, not hardcoded values

.button {
  background: var(--color-brand);
  padding: var(--space-unit) calc(var(--space-unit) * 2);
  border-radius: var(--radius-default);
}

Documentation is part of the system, not an afterthought

A component nobody can find gets rebuilt from scratch by the next developer who needs something similar. A living style guide page per component - states, variants, usage notes - is what actually stops that duplication from happening.

Tokens are the vocabulary, components are the sentences

A design token is a named, single-purpose value - color.brand.primary, space.md, radius.card - that stands in for a raw hex code or pixel value everywhere it's used. Components then reference tokens rather than hardcoded values, so a single token change (rebranding a color, adjusting a spacing scale) propagates everywhere automatically instead of requiring a find-and-replace across every component file.

{
  "color": { "brand": { "primary": "#c9862c" } },
  "space": { "sm": "8px", "md": "16px", "lg": "32px" }
}

Documentation is the part teams skip and later regret

A component with no documented props, states, and usage guidance gets reinvented slightly differently by the next person who needs something similar, which is exactly how design systems fragment back into inconsistent one-off components within a year. The docs site isn't a nice-to-have on top of the system - for a team of more than two or three people, it's the mechanism that makes the system actually get reused instead of reinvented.