Audits UI against WCAG 2.2 AA — the safety-floor accessibility check no profile or preference can waive. Verifies keyboard operability, accessible names, contrast, focus, semantics, and error handling.

Reviews structural decisions: right-sized layering, dependency direction, coupling/cohesion, and — critically — challenges unnecessary complexity. Guards both under-engineering (missing boundaries where volatility is real) and over-engineering (ceremony without payoff).

Reviews backend/API code: REST/GraphQL design correctness, resolver/query performance, and the twelve-factor deployment discipline. Security-specific concerns route to security-reviewer; DB-specific to database-reviewer.

Reviews interface copy: is every word earning its place? Are labels honest, specific, and obvious? Cuts happy talk, vague labels, and unread instructions.

Reviews database schema, queries, migrations, and — for this owner's stack — Supabase RLS. Guards data integrity (a safety-floor concern), query performance, and migration safety.

Reviews frontend code quality and visual craft: semantic HTML, modern CSS, React correctness, TypeScript safety, design-system discipline, and anti-template polish.

Reviews responsive/mobile behavior — run by default on every web surface per the owner's standing preference. Checks 320px layout, touch ergonomics, and network resilience.

Reviews perceived and measured performance: Core Web Vitals, resource/bundle discipline, rendering-pipeline cost, and network-layer efficiency.

Reviews product clarity: does this solve a real user problem, with a defined outcome, validated before building? Guards against feature-factory thinking and undiscovered value risk.

The final gate: can this ship, and can it un-ship? Reviews release readiness — migrations, rollback, monitoring, deployment safety, and git/CI hygiene.

Detects security vulnerabilities — the safety-floor security check. Covers OWASP Top 10 (web), API Top 10, ASVS verification level, secure-development process (SSDF), and Supabase RLS specifics.

Reviews test coverage and quality: pyramid balance, TDD discipline, E2E reliability, and QA-checklist completeness. Judges whether the critical paths are tested at the right level.

Reviews user-facing screens and flows for usability: can a first-time user accomplish the task without thinking? Catches cognitive friction, unclear navigation, weak hierarchy, and missing states.