Build an AI YouTube Title Generator with Claude Code

Build an AI YouTube Title Generator web app. People search for "youtube title generator" about 19,000 times a month, plus related searches like "youtube title ideas", "viral youtube titles", "youtube seo titles". The goal is a tool that ranks for those searches and makes money.

What it should do:
Build a YouTube title generator web app. Create a clean homepage with a large text area labeled 'Describe your video topic' and a prominent 'Generate Titles' button. When users click generate, show 8-10 different title variations in a scrollable list. Each title should have a copy button and a 'regenerate' option. Add tabs for different title styles: Viral, Educational, How-To, Listicle. Include a character counter showing optimal length (60 chars). Use bright, YouTube-inspired colors (red accent, clean white/gray). Focus on the core title generation 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 TubeBuddy, VidIQ, CoSchedule Headline Analyzer do it and make ours simpler and faster.
3. Make it rank. Use "youtube title generator" 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: /youtube-title-generator-for-[niche], /[topic]-video-title-ideas, /youtube-seo-title-checker.
4. Monetisation: Freemium: 10 free titles/day, $7/mo unlimited + trend analysis. 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.