This is part 1 of the design systems series: what a design system is. A design system is the shared product language behind interface, code, content, accessibility, and decision rules.
It is not only a Figma file. It is not only a component library. It is the set of reusable parts and rules that help teams build product surfaces without starting from zero every time.
Contents
Design system definition
A design system is a living set of foundations, components, patterns, content rules, code, and governance. It helps teams make the same kind of product decision in the same way, unless there is a clear reason to do something different.
| Part | What it does |
|---|
| Foundations | Color roles, type, spacing, grid, radius, icon rules, motion, elevation. |
| Components | Reusable interface parts such as buttons, inputs, tabs, modals, tables, cards, and navigation. |
| Patterns | Reusable solutions for common product moments such as onboarding, filtering, empty states, errors, and permissions. |
| Content rules | Labels, helper text, error messages, confirmation copy, and voice rules. |
| Code | Production-ready implementation, tokens, package rules, and component behavior. |
| Governance | How patterns are added, reviewed, maintained, deprecated, and adopted. |
Foundations
- What it does
- Color roles, type, spacing, grid, radius, icon rules, motion, elevation.
Components
- What it does
- Reusable interface parts such as buttons, inputs, tabs, modals, tables, cards, and navigation.
Patterns
- What it does
- Reusable solutions for common product moments such as onboarding, filtering, empty states, errors, and permissions.
Content rules
- What it does
- Labels, helper text, error messages, confirmation copy, and voice rules.
Code
- What it does
- Production-ready implementation, tokens, package rules, and component behavior.
Governance
- What it does
- How patterns are added, reviewed, maintained, deprecated, and adopted.
What a design system includes
The system should cover the decisions that repeat. If a product has complex dashboards, the system needs table, filter, chart, and alert rules. If it has onboarding risk, it needs permission, error, help, and progress rules.
| Layer | Example |
|---|
| Visual foundations | Type scale, color roles, spacing, layout, icons. |
| Interaction behavior | Hover, focus, disabled, loading, success, error, and empty states. |
| Accessibility | Keyboard behavior, contrast, target size, focus, labels, status messages. |
| Product patterns | Forms, dashboards, settings, billing, onboarding, search, filters. |
| Documentation | Usage, anatomy, do/don’t notes, examples, exceptions. |
| Contribution model | Who can add, change, approve, or retire a pattern. |
Visual foundations
- Example
- Type scale, color roles, spacing, layout, icons.
Interaction behavior
- Example
- Hover, focus, disabled, loading, success, error, and empty states.
Accessibility
- Example
- Keyboard behavior, contrast, target size, focus, labels, status messages.
Product patterns
- Example
- Forms, dashboards, settings, billing, onboarding, search, filters.
Documentation
- Example
- Usage, anatomy, do/don’t notes, examples, exceptions.
Contribution model
- Example
- Who can add, change, approve, or retire a pattern.
Design system vs UI kit vs style guide
| Term | What it is | Limit |
|---|
| UI kit | A set of interface components, often in Figma. | Useful, but incomplete without behavior, code, content, and governance. |
| Style guide | Visual and brand rules for how things should look and sound. | Does not always define product interaction or reusable implementation. |
| Component library | Reusable coded components. | Can become technical inventory without design rationale or product patterns. |
| Design system | A connected set of rules, components, patterns, code, and governance. | Only works if teams adopt and maintain it. |
UI kit
- What it is
- A set of interface components, often in Figma.
- Limit
- Useful, but incomplete without behavior, code, content, and governance.
Style guide
- What it is
- Visual and brand rules for how things should look and sound.
- Limit
- Does not always define product interaction or reusable implementation.
Component library
- What it is
- Reusable coded components.
- Limit
- Can become technical inventory without design rationale or product patterns.
Design system
- What it is
- A connected set of rules, components, patterns, code, and governance.
- Limit
- Only works if teams adopt and maintain it.
How design systems work in product teams
A design system works when it sits inside daily product work. Designers use it in critique. Engineers use it in implementation. Product managers use it to reduce scope debates. Content and support use it to keep language clear.
| Team | How they use it |
|---|
| Design | Reuse patterns, define exceptions, improve quality without redrawing every surface. |
| Engineering | Build with stable components, states, tokens, and accessibility rules. |
| Product | Use the system to reduce repeated decisions and clarify scope. |
| Content | Keep labels, errors, help, and empty states consistent. |
| Support | Feed repeated user confusion back into product patterns. |
Design
- How they use it
- Reuse patterns, define exceptions, improve quality without redrawing every surface.
Engineering
- How they use it
- Build with stable components, states, tokens, and accessibility rules.
Product
- How they use it
- Use the system to reduce repeated decisions and clarify scope.
Content
- How they use it
- Keep labels, errors, help, and empty states consistent.
Support
- How they use it
- Feed repeated user confusion back into product patterns.
Connect the series