Neon Postgres Egress Optimizer

This walks Claude through finding and fixing the query patterns that cause surprise Neon bills. It starts by running pg_stat_statements to identify which queries transfer the most data, then analyzes your codebase for common culprits like SELECT *, missing pagination, and JOINs that duplicate parent rows across children. The fixes are practical: select only needed columns, add LIMIT clauses, cache high-frequency queries, push aggregations into SQL instead of fetching raw data. Most egress problems come from application code fetching way more data than it actually uses, and this gives Claude a step-by-step diagnostic workflow to catch those issues before they show up on your invoice.