# Design System Health Scorecard

Date: ___________
System: ___________
Scored by: ___________

---

## 1. Token Coverage (1-5): ___

- [ ] Primitive tokens defined
- [ ] Semantic layer aliases to primitives
- [ ] No raw hex values in components
- [ ] Dark mode/theming works via token swap
- [ ] Token naming follows documented convention

## 2. Component Health (1-5): ___

- [ ] Component inventory exists
- [ ] Variants cover all use cases
- [ ] States documented (hover, active, disabled, focus, error)
- [ ] Responsive behavior defined
- [ ] Detached instance count is low (<5%)

## 3. Naming Consistency (1-5): ___

- [ ] Naming convention documented
- [ ] Consistent separator usage
- [ ] Consistent casing
- [ ] Automated validation exists
- [ ] New additions follow convention

## 4. Documentation (1-5): ___

- [ ] Component descriptions exist
- [ ] Usage guidelines (when to use / when not to use)
- [ ] Props/API documented
- [ ] Do/don't examples
- [ ] Accessibility notes per component

## 5. Accessibility (1-5): ___

- [ ] Color contrast meets AA (4.5:1 text, 3:1 UI)
- [ ] Focus indicators visible
- [ ] Keyboard navigation works
- [ ] ARIA attributes correct
- [ ] Screen reader tested

## 6. Design-Code Parity (1-5): ___

- [ ] Token values match between design and code
- [ ] Component structure matches
- [ ] Variant coverage matches
- [ ] Automated drift detection exists
- [ ] Sync pipeline documented

---

## Total: ___ / 30

| Total | Grade | Meaning |
|-------|-------|---------|
| 25-30 | A | AI-ready |
| 19-24 | B | Strong foundation |
| 13-18 | C | Needs investment |
| 7-12  | D | Early stage |
| 6     | F | Starting from scratch |

## Action Plan

1. Lowest dimension: _______________
2. Second lowest: _______________
3. Quick win: _______________

Next review date: ___________