Design Principle
Token editors need to make design decisions, references, and impact scope visible.
Principle
Token editors need to make design decisions, references, and impact scope visible.
Design action
Group by color, type, spacing, radius, and shadow; show alias/semantic relationships, preview, diff, and affected components.
Examples
Positive example: Design system admin, theme editors, multi-brand systems, and component library management. Counterexample: Only hex inputs exist with no semantic name or preview.
Apply when
Design system admin, theme editors, multi-brand systems, and component library management. 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
Group by color, type, spacing, radius, and shadow; show alias/semantic relationships, preview, diff, and affected components.