Design System Colors

Colors Overview

At its core, colors is about doing one thing well inside your design systems project. Once you understand the pattern, you can apply it consistently across features and teams.

Good colors pays off across the whole codebase: fewer surprises, easier testing, and smoother onboarding. The snippet below is a solid starting point.

:root {
  --color-brand-500: #2563eb;
  --color-text: #0f172a;
  --color-surface: #ffffff;
}

[data-theme="dark"] {
  --color-text: #e2e8f0;
  --color-surface: #0f172a;
}

Semantic color variables let components stay theme-agnostic while dark mode swaps the underlying values.

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 Colors example and grow it only as needed.
• Keep configuration explicit so Colors behaves the same in every environment.
• Name things clearly so teammates understand your Colors at a glance.
• Add tests around Colors early to lock in expected behaviour.

Design System Cheatsheet

Quick reference for colors within a modern design system.

How Colors Fits into a Design System

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.

Semantic color variables let components stay theme-agnostic while dark mode swaps the underlying values.

• 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 Colors

Adoption is where design systems succeed or stall. Make 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 colors.
• Leaving colors untested, so regressions slip into production.
• Over-engineering colors before you actually need the extra flexibility.
• Ignoring documentation, which makes colors hard for the next developer to change.

Key Takeaways

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