Design System Do's and Don'ts

Do's and Don'ts Overview

Do's and Don'ts 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 do's and don'ts focused and predictable. Start from the minimal example here, then layer in only the complexity your feature actually needs.

/* A design system pairs shared tokens with reusable components */
:root {
  --color-brand-500: #2563eb;
  --space-4: 16px;
  --radius-md: 8px;
}

.button-primary {
  background: var(--color-brand-500);
  padding: var(--space-4);
  border-radius: var(--radius-md);
}

A design system connects tokens, components, and documentation into one shared language.

Do's and Don'ts Example

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

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

Design System Cheatsheet

Quick reference for do's and don'ts within a modern design system.

How Do's and Don'ts Fits into a Design System

Do's and Don'ts 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.

A design system connects tokens, components, and documentation into one shared language.

• 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 Do's and Don'ts

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

Key Takeaways

• Do's and Don'ts is a core part of working effectively with design systems.
• Start small and keep do's and don'ts focused on a single responsibility.
• Apply consistent patterns so do's and don'ts scales across your project.
• Test and document do's and don'ts to keep it maintainable over time.