performance-auditlisted

# Performance & Resource Usage Audit A structured, evidence-based check of a project's backend, frontend, database, and infrastructure/deployment configuration for performance, scalability, and resource-cost issues — not a benchmark run and not a substitute for an actual profiler, load test, or Lighthouse run. It investigates the codebase and configuration for the patterns that *cause* slowness, excess resource use, or wasted cost, and reports one table the user can act on. Out of scope, by design: application security (SSRF, injection, auth, secrets — use `cybersecurity-check`) and general code correctness/readability/maintainability (use `code-review`). A finding belongs here only if its primary consequence is latency, throughput, memory/CPU usage, or infrastructure cost. ## Ground rules - **Evidence or it didn't happen.** Every row needs a concrete pointer — a `file:line`, a grep match, an actual config value, or a command's real output. Never write "looks fine," "should be fast enough," or "probably scales" — either you found the pattern (good or bad) in the code/config, or you say plainly that you couldn't check it. - **Be explicit about what kind of check each row is.** Most of this skill is static investigation: reading code and config to spot patterns known to cause performance/resource problems (N+1 queries, missing indexes, unbounded caches, missing resource limits). That tells you a problem is *likely*, not its actual magnitude — code review cannot