Drift (Design System Drift)

The slow gap that opens between your design system as documented and your product as shipped: hardcoded values, rogue variants, one-off components nobody approved.

All Dictionary

What it is

Drift is the gap between what your design system says and what your product does. A hardcoded #3B82F6 instead of color.action.primary. A button with custom padding because the deadline was Friday. A copy-pasted card component that diverged six months ago. Each one is small; together they are why your system stops being the source of truth.

Why this matters for designers

Drift is invisible until it is expensive: a rebrand that should be a token change becomes a months-long hunt, and AI tools trained on your codebase learn the drifted patterns instead of the documented ones. Drift detection is also the ideal first job for an AI agent: finding mismatches between documented and shipped is exactly the tedious, mechanical comparison agents are good at, and it requires zero write access.

How it works in practice

  1. Drift accumulates wherever shipping pressure meets missing guardrails.
  2. Detection means continuously comparing shipped code against tokens and component docs.
  3. An observer-mode agent can run this audit weekly and report what it finds.
  4. Fixing drift at the source (and adding a rule so it cannot recur) is what turns detection into self-healing.