The input / text example highlights a different part of the process: error state. Document behaviour beside appearance. Link a component to its tokens and record a rationale when the pattern changes. Compare it with dialog / modal before assuming that both items require the same response.
Work through the specimen
A screenshot shows a component at one moment. It does not explain its states, accessibility requirements or limits.
Example: Input / text
The illustrative record contains error state. Its state is documented. Ask what evidence supports that state, which detail is still uncertain and whether the next person could understand it without reading a separate message thread.
Questions for a working review
- Check the current condition against the stated context. For input / text, use “Error state” as the starting context.
- Identify which role can verify the information. For input / text, use “Error state” as the starting context.
- Record the exception as well as the expected path. For input / text, use “Error state” as the starting context.
A small exercise
Take one recent design system management example from your own process. Write its context without using a status label, then add the label separately. If the two contradict each other, investigate the source before updating the record. Compare the result with “Dialog / modal” in the demonstration to see which distinctions your process needs.
These are planning notes. The specimen is illustrative, and the preview does not process live work.
More resources →