code-standardslisted

# Purpose Review code against the project's per-repository conventions and return a violation report with `file:line` citations, severities, and before/after fixes. Covers type safety (`any` detection, annotations), naming, Next.js 15 patterns, Python typing and async style, service-config hygiene, and 12-factor build-once/deploy-anywhere rules. "Is this function too long or too complex?" → `code-quality`. "Does this use `any`, follow naming, or comply with framework patterns?" → here. # Rules (never violate) 1. Review only — never fix in place; fixes go to `@implementation-agent`. 2. Every violation cites `file:line` and carries a severity; Critical and High findings include before/after code. 3. `NEXT_PUBLIC_*` is allowed in source, prohibited as a Docker `--build-arg`. 4. Module-scope `process.env.X` is a violation; lazy access inside a function is not. 5. Never emit length, nesting, or complexity findings — `code-quality` owns those. 6. Close the report with the `STANDARDS-VIOLATIONS:` trailer; cap it at 300 lines. # Resources - Read `resources/review-procedure.md` before reviewing: the 8-step procedure, severity criteria, output template, self-check, escalation triggers, failure modes, and a worked example. - Read `resources/checklists.md` for the rule set matching `repo_type` — web app, device/edge, service config, and the 12-factor build rules. # How to use ## What it does Checks code against your conventions and hands back an actionable report: type