Clean Claude-Vercel-Supabase Codebase

My GitHub repo mixes Claude integration, a Vercel front-end, and a Supabase back-end, but the structure has grown messy. I want the whole stack tidied so a new contributor can clone, run `npm install`, and deploy without surprises.

Here is what matters:
• Code structure – reorganise folders and modules so Claude hooks, Vercel pages, and Supabase helpers each live in a clear, predictable place.
• Documentation – rewrite the README and any inline comments so setup, env variables, and deployment steps are obvious.
• Dependency management – audit `package.json`, lockfile, and Supabase extensions, remove anything unused, pin versions that should not drift, and add notes on why each package stays.

Special focus areas include:
• Claude integration: confirm the current API wrapper follows best practices and expose a clean interface for prompts and responses.
• Vercel deployment: set up environment variables, build script, and automatic preview deployments so a push to `main` is production-ready.
• Supabase configuration: check table schemas, RLS policies, and service roles, then document the SQL migrations that recreate the database from scratch.

Industry-standard linting, formatting, and commit conventions are fine; feel free to introduce Prettier, ESLint, or Husky if they simplify future work.

Acceptance criteria
• One streamlined GitHub branch ready to merge into `main`.
• A single command to run the project locally and another to deploy on Vercel, both verified in your PR.
• Updated README covering setup, scripts, Claude keys, Supabase URL/anon key, and troubleshooting tips.
• CI check or badge confirming build passes with the cleaned dependencies.

Once everything is merged, I will test a fresh clone myself; payment is released when the repo starts, deploys, and the docs answer every step without additional guidance.