Build a Batch Image Resizer with Claude Code

Build a Batch Image Resizer web app. People search for "batch image resizer" about 1,300 times a month, plus related searches like "bulk image resizer", "resize multiple images", "batch photo resize". The goal is a tool that ranks for those searches and makes money.

What it should do:
Build a batch image resizer web app. Create a homepage with drag-and-drop area for multiple image uploads with progress indicators. Add resize options: specific dimensions, percentage scaling, and preset sizes (thumbnail, social media, web). Include quality settings and format conversion options. Show processing queue with individual image previews and batch progress. Add zip download for all processed images and individual download options. Use efficient design with clear batch processing indicators. Focus on the multi-upload and batch processing flow first.

How to build it:
1. Read this folder first. If it is empty, set up Next.js (App Router, TypeScript, Tailwind). Write a short PLAN.md with the pages, components, any library or API you need, and what you are leaving for later. Then build.
2. Put the tool itself on the homepage so a visitor can use it within seconds, with no sign-up. Do the processing in the browser where you can, so it is fast and cheap to run. Look at how ILoveIMG, TinyPNG, ResizePixel do it and make ours simpler and faster.
3. Make it rank. Use "batch image resizer" in the title tag, H1 and meta description. Under the tool, add a short how-to and an FAQ with FAQPage schema, and add a sitemap and robots.txt. Scaffold these programmatic pages from one template and a data file: /batch-resize-images-to-[dimensions], /bulk-image-resizer-for-[platform], /resize-[image-type]-in-bulk.
4. Monetisation: Freemium: 20 images/batch, $7/mo unlimited + priority processing. Add a pricing page and the free usage limit, and leave Stripe checkout as a clearly marked stub with the environment variables it needs.
5. Run it locally and test the main flow end to end, including edge cases like empty input and very large files. Fix what breaks, then finish with a summary of what works, what is stubbed and how to deploy it to Vercel.

Paste it into Claude Code in an empty folder. It plans first, so read PLAN.md and steer before it starts building.