Semantic Colors

Semantic Colors Overview

Semantic Colors lets you structure design systems work so it stays readable, testable, and easy to scale. Instead of ad-hoc code, you follow a clear pattern that other developers can recognise immediately.

The key is to keep semantic colors focused and predictable. Start from the minimal example here, then layer in only the complexity your feature actually needs.

// tokens.json (design tokens)
{
  "color": {
    "brand": { "500": { "value": "#2563eb" } },
    "text":  { "default": { "value": "{color.brand.500}" } }
  },
  "space": {
    "sm": { "value": "8px" },
    "md": { "value": "16px" }
  }
}

Design tokens store design decisions as data so they can be shared across platforms and themes.

Semantic Colors Example

/* Tokens flow into components, which flow into products */
:root { --color-brand-500: #2563eb; }
.button { background: var(--color-brand-500); }

• Start from a minimal Semantic Colors example and grow it only as needed.
• Keep configuration explicit so Semantic Colors behaves the same in every environment.
• Name things clearly so teammates understand your Semantic Colors at a glance.
• Add tests around Semantic Colors early to lock in expected behaviour.

Design System Cheatsheet

Quick reference for semantic colors within a modern design system.

How Semantic Colors Fits into a Design System

Semantic Colors connects the design decisions in your system to the code teams actually ship. When it is defined once and reused, products stay consistent and updates roll out everywhere.

Design tokens store design decisions as data so they can be shared across platforms and themes.

• Define it once as a token or shared component.
• Document intended usage with clear examples.
• Make it themeable and accessible by default.
• Version and release changes so consumers can upgrade safely.

Getting Teams to Adopt Semantic Colors

Adoption is where design systems succeed or stall. Make semantic colors the easiest option: great docs, sensible defaults, and clear migration paths beat mandates every time.

Common Mistakes

• Skipping error handling and edge cases when wiring up semantic colors.
• Leaving semantic colors untested, so regressions slip into production.
• Over-engineering semantic colors before you actually need the extra flexibility.
• Ignoring documentation, which makes semantic colors hard for the next developer to change.

Key Takeaways

• Semantic Colors is a core part of working effectively with design systems.
• Start small and keep semantic colors focused on a single responsibility.
• Apply consistent patterns so semantic colors scales across your project.
• Test and document semantic colors to keep it maintainable over time.