Checklists#
What a reviewer gates on. Each one cites rules by id rather than restating them, so a checklist can't drift from the rule it enforces.
| Checklist | When |
|---|---|
| component | any new or changed component |
| page | a page is finished |
| seo | per page or template |
| accessibility | per page |
| pre-launch | before going live — executable as the launch skill |
These cover build work, not setup. The earlier phases of an engagement — kickoff, scaffold, design-system intake — are driven by the numbered steps in runbook, which is a procedure to follow rather than a list to verify against. There are deliberately no kickoff or scaffold checklists: a step you either did or didn't do doesn't need a second document confirming it, and anything skipped with a visible consequence surfaces in checklist.pre-launch.