code-standardslisted

# Purpose Reviews code against the project's per-repository coding standards (see the project's `CLAUDE.md` and `.claude/project.json`) and produces a violation report with `file:line` citations, severity levels, and before/after fix examples. Covers type safety (including `any`-type detection), naming conventions, Next.js 15 patterns, Python async patterns, service-config hygiene, and 12-factor build-once/deploy-anywhere rules. This skill owns **convention-level** checks: `any` types, missing type annotations, naming style, `force-dynamic` presence, `getDb()` pattern, `NEXT_PUBLIC_*` build-arg prohibition, and npm run build. It does NOT own function length, cyclomatic complexity, nesting depth, or code smell detection -- those belong to `code-quality`. # When to use / When NOT to use **Use when:** - Code has been written or modified in the main web app and needs a standards review before merge - Code has been written or modified in the device/edge repo and needs type hint / async pattern verification - A service config in the infrastructure repo has been modified and needs lint, version bump, and defensive template verification - A Dockerfile or CI pipeline change needs 12-factor compliance verification **Do NOT use when:** - Measuring function length, cyclomatic complexity, nesting depth, or code smells (use `code-quality`) - Verifying field alignment between Prisma schema, Zod, and route handlers (use `api-contract`) - Navigating the codebase to find files (use `code-