# Design system review checklist

Flow being reviewed:
Reviewer and date:
Design and implementation links:

## Foundations
- [ ] Tokens describe roles as well as raw values.
- [ ] Type and spacing choices use the agreed scale.
- [ ] Light and dark assignments are documented.
- [ ] Contrast is checked in actual use.

## Components
- [ ] Purpose and supported variants are clear.
- [ ] Default, hover, focus, disabled and loading states are reviewed.
- [ ] Fields have labels, instructions and associated errors.
- [ ] Keyboard navigation and focus order are checked.
- [ ] Long content, missing data and narrow layouts are checked.
- [ ] Reduced motion and alternative cues are considered.

## Adoption
- [ ] The component works in a complete product flow.
- [ ] Design and code describe the same behaviour.
- [ ] Changes have a reviewer and an owner.
- [ ] Breaking changes have a migration path.

| Gap | Affected screen | Evidence | Proposed action | Owner | Review date |
| --- | --- | --- | --- | --- | --- |
| | | | | | |

This checklist supports review and does not certify accessibility conformance.
