Use for governed software work that needs source-of-truth checks, routing, token/context governance, branch/PR discipline, validation honesty, and release readiness. Do not use as approval for writes, installs, migrations, broad plugin use, external tool activation, or global config changes.
Use for React, TypeScript, hooks, tests, build quality, maintainability, AI-generated code risk, and safe quality-gate routing. Do not use to add dependencies, change package managers, reformat broadly, duplicate Superpowers, or rewrite architecture for scanner output.
Use for PR readiness, branch hygiene, checks, review feedback, release gates, publish readiness, and post-merge handoff. Do not push to main, merge with pending required checks, or mark release ready without evidence.
Use for UI/UX authority, visual polish, responsive behavior, accessibility, design-system consistency, workflow clarity, and browser-visible quality. Do not use for backend-only, security-only, release-only, package/config, external design activation, or frontend implementation by default.
Use for auth, authorization, tenant isolation, public/private payloads, secrets, supply-chain, source safety, and security review. Do not run production-impacting scans, read secrets unnecessarily, weaken controls, auto-configure tools, or mark metadata-only scanners as approved.