2 definitions in this file:
What happens during this step — the system's response, visual changes, state transitions, and user-facing feedback. CommonMark supported.
What starts this interaction step — a user action, system event, or condition (e.g., 'User submits the form by activating the submit button', 'API returns a 422 response'). When omitted, the step continues the previous step's flow without a new trigger.
Names of the components involved in this step. Each name MUST match the `name` of a component documented elsewhere in the system. Creates a cross-reference between the pattern's interaction flow and individual component docs.
Visual or interactive examples for this step — screenshots of the resulting state, screen recordings of the transition, or code snippets showing the implementation.
References:
richText, example
Identifies this guideline as an interactions spec.
The interaction steps in chronological order. Each item documents a single step with its trigger, description, involved components, and optional examples. Ordering is significant — tools SHOULD preserve and display steps in this order to represent the temporal sequence.
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:
interactionEntry, agents
Design System Documentation Standard (DSDS) 0.1 — Draft Specification
GitHub