2 definitions in this file:
Machine-readable state name (e.g., 'default', 'hover', 'focus', 'active', 'disabled', 'loading', 'selected', 'error', 'read-only').
What triggers this state, how appearance and behavior change, and any constraints or side effects.
Human-readable name (e.g., 'Default', 'Hover', 'Focus', 'Active / Pressed', 'Disabled', 'Loading').
Design token overrides applied when this state is active. Keys are token property names scoped to the component (e.g., 'button-background', 'button-border-color'). Values are the token names or resolved values used in this state. Only tokens that change from the default state need to be listed. Note: these token references are descriptive summaries for designers. Authoritative resolved values for each variant × state combination live in the design-specifications guideline's overrides array.
Why this state exists — the user need or design rationale it addresses.
Visual previews showing the component in this state.
References:
richText, purpose, example
Identifies this guideline as a states spec.
The interactive states. Each item documents a single state with its trigger, visual changes, token overrides, and optional previews. Ordering is significant — tools SHOULD display states in this order.
Min items: 1
Agent-optimized context for this document block. Provides structured information for AI/LLM consumption — constraints, disambiguation, anti-patterns, examples, and keywords.
References:
stateEntry, agents
Design System Documentation Standard (DSDS) 0.1 — Draft Specification
GitHub