Review a WordPress Design System interface

Start shallow

1. Define the changed user-facing behaviour, affected users, runtime document, target versions, and dependency deployment boundary.
2. Scan the complete diff once for semantics and accessibility, interaction and focus, styling and tokens, integration, tests, and compatibility. Account for every changed file before deep research; finding one defect does not end this pass.
3. Choose the narrowest review path:
   • Lightweight: copy-only or supported-prop changes with no interaction, styling, or setup change.
   • Standard: component, custom UI, styling, or interaction changes.
   • Deep: migrations, public-contract risk, or separate documents and overlays.