Build a Font Identifier with Claude Code

Build a Font Identifier web app. People search for "font identifier" about 170,000 times a month, plus related searches like "what font is this", "font finder tool", "identify font from image". The goal is a tool that ranks for those searches and makes money.

What it should do:
Build a font identifier web app. Create a homepage with a large upload zone saying 'Upload image to identify fonts'. When users upload an image, highlight detected text areas and let them select specific words. Show font matches with confidence scores, preview text samples, and download/purchase links. Add filters for font style (serif, sans-serif, script) and usage (web, print, logo). Include a 'Try this font' feature with editable text preview. Use a typography-focused design with elegant fonts and clean layout. Focus on the image upload and font detection 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 WhatTheFont, Font Squirrel Matcherator, Adobe Fonts do it and make ours simpler and faster.
3. Make it rank. Use "font identifier" 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: /identify-[font-type]-fonts, /font-finder-for-[design-project], /what-font-is-this-[style].
4. Monetisation: Freemium: 5 free identifications/day, $6/mo unlimited + font suggestions. 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.