Why "Optimize Your Images" Is Bad Advice

I think a lot of founders hear "optimize your images" and still do not know what that means in practice. Usually it is some mix of wrong format, wrong dimensions, duplicate exports, hero image too heavy. Not bad code, just bad file decisions that nobody thought about at launch. I kept hitting the same cleanup on different projects. The steps were always the same: find the bloated images, figure out which ones are safe to convert, which ones need manual review, and which ones you should not touch at all. So I turned it into a Claude Code skill. What Image Audit does The skill runs two audits. Repo audit. It walks through your codebase looking for PNG, JPG, and other image files. For each one, it checks file size, format, and how it is referenced in your code. It flags anything over 500KB and identifies images that could safely be converted to WebP. Supabase audit. If you have a Supabase storage bucket, it scans that too. Same checks: format, size, duplicates, and whether the image is ac