Start with button / primary. The entry pairs “Focus state” with “Specified”. That pairing is useful only when it is clear why the context supports the state. A screenshot shows a component at one moment. It does not explain its states, accessibility requirements or limits.
Begin with the constraint
Document behaviour beside appearance. Link a component to its tokens and record a rationale when the pattern changes.
Example: Button / primary
The illustrative record contains focus state. Its state is specified. 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
- Define the decision the reader needs to make. For button / primary, use “Focus state” as the starting context.
- Find the source behind the example record. For button / primary, use “Focus state” as the starting context.
- Write down the open question before choosing a state. For button / primary, use “Focus 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 “Input / text” 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 →