---
id: kb_design_systems_tokens_components_consistency
title: Design tokens and component consistency
category: design-systems
appliesToAppTypes: [generic]
appliesToLenses: [visual-hierarchy]
steps: [evaluate]
tags: [design-systems, tokens, components, consistency]
citation:
  source: "U.S. Web Design System: Design tokens"
  url: "https://designsystem.digital.gov/design-tokens/"
  retrievedAt: "2026-06-01T00:00:00.000Z"
freshness:
  volatility: evolving
  lastReviewed: "2026-06-01T00:00:00.000Z"
---

## Summary

Reusable tokens and components should make repeated interface decisions consistent while still
allowing intentional exceptions.

## Deep Guidance

Compare repeated colors, spacing, typography, buttons, form controls, and state treatments for
unexplained variation. A design-system finding is strongest when it identifies a repeated pattern
that has drifted from the apparent token/component set, not when it merely dislikes a style.
Recommend consolidating to an existing token or component, documenting an intentional exception,
or introducing a named reusable decision when the same local override appears in multiple places.
