Build an Audio Noise Remover with Claude Code

Build an Audio Noise Remover web app. People search for "audio noise remover" about 700 times a month, plus related searches like "remove background noise", "audio noise reduction", "clean audio recording". The goal is a tool that ranks for those searches and makes money.

What it should do:
Build an audio noise remover web app. Create a homepage with audio upload and noise type selector (background noise, echo, hum, static). When users upload audio, show waveform visualization with noise detection highlighting. Add intensity controls for noise reduction and real-time preview with before/after comparison. Include preset filters for common scenarios (podcast, interview, music). Show processing progress and download options in multiple formats. Use audio-focused design with dark theme and waveform visualizations. Focus on upload and noise removal 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 Adobe Audition, Krisp, Descript do it and make ours simpler and faster.
3. Make it rank. Use "audio noise 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-noise-from-[audio-type], /audio-noise-remover-[use-case], /clean-[recording-type]-audio.
4. Monetisation: Freemium: 10min audio/day, $8/mo unlimited + premium filters. 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.