superpowers-sage:reviewing

To audit Sage and Acorn projects for convention drift, review PHP service providers, ACF blocks, Blade templates, routes, and Tailwind usage. This process flags structural violations and layout drift across changed files before merging.

Reviewing Blade templates and ACF block patterns in Roots Sage involves checking template responsibilities and validating field usage against established conventions. This identifies critical violations and maps line-specific issues for immediate correction.

Yes, you can verify implemented Tailwind components against design specs by reading plan asset specs and dispatching visual verification. This reports MATCH, DRIFT, MISSING, or FAIL_ARBITRARY_VALUES statuses for frontend alignment before merge.

Yes, the code review process flags hardcoded and invalid arbitrary value patterns in Tailwind CSS. It enforces block-view guardrails to prevent component reuse issues and layout drift in Sage/Acorn frontend implementations.

Checking Service Provider structure and route patterns in an Acorn codebase requires auditing PHP controllers against architectural rules. This validation ensures backend conventions are maintained and surfaces categorized findings for improvements.