CSS-in-JS

CSS-in-JS Overview

CSS-in-JS 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 css-in-js focused and predictable. Start from the minimal example here, then layer in only the complexity your feature actually needs.

/* Button.module.css */
.primary {
  background: var(--color-brand-500);
  color: #fff;
  padding: var(--space-2) var(--space-4);
  border-radius: var(--radius-md);
}

CSS Modules scope styles locally while still reading shared tokens from CSS custom properties.

CSS-in-JS Example

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

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

Design System Cheatsheet

Quick reference for css-in-js within a modern design system.

How CSS-in-JS Fits into a Design System

CSS-in-JS 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.

CSS Modules scope styles locally while still reading shared tokens from CSS custom properties.

• 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 CSS-in-JS

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

Common Mistakes

• Copying css-in-js snippets without understanding what each line does.
• Skipping error handling and edge cases when wiring up css-in-js.
• Leaving css-in-js untested, so regressions slip into production.
• Over-engineering css-in-js before you actually need the extra flexibility.

Key Takeaways

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