The playbook
Design Systems: Template and Field Guide
This design systems template turns a broad task into a record another person can use. It captures component, variant, state, then connects that information to a decision. Copy the table into your working document or system and create a separate record for each item in scope.
Put the task in context
Document a button's default, hover, focus, disabled, and loading states along with its label rules. Reuse the component where the behavior is the same. Add a new variant only when it represents a meaningful difference in hierarchy or interaction.
Copyable worksheet
| Field | Entry instructions |
|---|---|
| component | Record the component associated with this page or interaction record. Use a stable reference so later updates can be matched. |
| variant | Record the variant associated with this page or interaction record. Keep the value specific enough for another owner to interpret. |
| state | Record the state associated with this page or interaction record. Keep the value specific enough for another owner to interpret. |
| usage rule | Record the usage rule associated with this page or interaction record. Keep the value specific enough for another owner to interpret. |
| Decision field | Entry instructions |
|---|---|
| Observed problem | Describe the actual condition and where it was observed. |
| Recommended action | State the smallest action that resolves the documented problem. |
| Evidence | Link to the record, observation, or test supporting the action. |
| Owner and next review | Name the accountable person and when the decision should be revisited. |
How to complete the worksheet
Begin with component. Use the same reference throughout the record so notes are not attached to the wrong item. Then define shared typography spacing colors and components. This establishes the information required before the worksheet becomes a request for action.
Next, document component states and accessibility behavior. Use the observed problem and evidence fields to explain why that step is needed. A useful entry describes an actual condition, such as building many nearly identical components with unclear purposes, rather than a broad instruction to “improve performance.”
Finally, review exceptions before adding new variants. Put consolidate variants around real interaction differences in the action field only when it addresses the observed condition. If the problem is different, change the action. The template is a structure for judgment, not a reason to apply the same fix everywhere.
Illustrative completed decision
| Part | Illustrative entry |
|---|---|
| Problem | Building many nearly identical components with unclear purposes |
| Action | Consolidate variants around real interaction differences |
| First check | Define shared typography spacing colors and components |
| Follow-up check | Review exceptions before adding new variants |
| Outcome to define | unnecessary component variants |
Adapt the fields without losing meaning
You can add fields required by your team, but each should change a decision or preserve necessary context. Keep factual observations separate from recommendations. If variant changes, record the new value and its effective date instead of silently rewriting the context of an earlier decision.
Use the record in a handoff
Ask the receiving owner to explain the next action using only the worksheet. Missing context becomes visible quickly during that exercise. Repair the record before applying the structure to a larger batch. Keep unnecessary component variants connected to the item so the team can later assess whether the action was useful.
Verify the actual visitor journey on a narrow screen and with a keyboard. A design can look complete while hiding an unreachable control or a missing confirmation. Record the task attempted and what happened at the end.
Skip the manual steps. Let AgentixHUB run this for every client.
Start now