Design Principle
A design system needs to record why components are added, how they are reused, and when they are deprecated, not just list components.
Principle
A design system needs to record why components are added, how they are reused, and when they are deprecated, not just list components.
Design action
New components submit problem, existing alternatives, state coverage, token dependencies, accessibility checks, and version impact.
Examples
Positive example: Teams maintain component libraries, design tokens, templates, and pattern libraries. Counterexample: Each project creates a similar button or card component.
Apply when
Teams maintain component libraries, design tokens, templates, and pattern libraries. Users need to judge state, scope, risk, or next action quickly.
Source notes
Source note: Synthesized from GOV.UK, Carbon, Polaris, Atlassian, Design.Systems, Design Systems Repo, and product-pattern libraries. GOV.UK Design System Patterns: https://design-system.service.gov.uk/patterns/ Carbon Patterns: https://carbondesignsystem.com/patterns/ Shopify Polaris: https://polaris-react.shopify.com/ Atlassian Design System: https://atlassian.design/ Design Systems Repo: https://designsystemsrepo.com/
Agent Directive
New components submit problem, existing alternatives, state coverage, token dependencies, accessibility checks, and version impact.