Build an Image Background Remover with Claude Code

Build an Image Background Remover web app. People search for "image background remover" about 24,000 times a month, plus related searches like "remove background online", "transparent background", "background eraser". The goal is a tool that ranks for those searches and makes money.

What it should do:
Create a modern background removal web app. Start with a clean homepage featuring a large drag-and-drop zone that says 'Drop your image here' with a subtle dashed border. Add a file upload button as fallback. When a user selects an image, show it in a split-screen layout with 'Before' and 'After' labels. For now, just show the original image on both sides with a 'Processing...' state on the right. Add a download button (can be non-functional initially) and a simple navigation header. Use a minimal design with rounded corners, subtle shadows, and clean typography. Focus on getting the UI flow working first - you can integrate actual background removal later.

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 Remove.bg, Canva Background Remover, PhotoRoom do it and make ours simpler and faster.
3. Make it rank. Use "image background remover" 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: /remove-background-from-[item], /background-remover-for-[use-case], /[platform]-photo-editor.
4. Monetisation: Freemium: 3 free/day, $5/mo unlimited. 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.