Get Ready to Deploy

The tools below aren’t random — they’re one pipeline. Here’s the path your code takes from your laptop to live on the internet.

What the script installs

Prefer to read them first? Grab the raw scripts: mac.sh · windows.ps1

Get the starter repo

This is the repo everything below assumes you have. It’s a working Next.js 16 + Supabase + Vercel app with Claude Code already wired in — it ships a CLAUDE.md, an .env.example, tests, Supabase migrations, and the /done, /commit and /lint-fix skills in .claude/skills/. Run the setup command above first (it installs git), then clone:

git clone https://github.com/fotoflo/aimhuge-training-starter.git
cd aimhuge-training-starter
pnpm install

See the deployed result first: starter.aimhuge.com · browse the code on GitHub. Everything from here runs inside this folder.

Get your keys into .env.local

The script installs the tools; these keys connect your app to the services it talks to. Create a few free accounts, copy one value from each, and paste them into a file called .env.local in your project root. It’s gitignored — it never gets committed.

Start from the example file:

cp .env.example .env.local

1. 1
   GitHub — hosts your code and is how you sign into Vercel and Supabase. You already have this if you cloned the repo. For in-app “Sign in with GitHub”, create an OAuth app (Settings → Developer settings → OAuth Apps) and paste its Client ID + Secret into Supabase → Authentication → Providers — those live in Supabase, not .env.local.
2. 2
   Vercel — sign up with your GitHub account, then authenticate the CLI with vercel login (same as claude and supabase login). There’s no Vercel key in .env.local — but when you deploy, add the four keys below under Project → Settings → Environment Variables.
3. 3
   Supabase — create a project, then open Project Settings → API and copy three values:

   • NEXT_PUBLIC_SUPABASE_URL ← “Project URL”
   • NEXT_PUBLIC_SUPABASE_ANON_KEY ← the “anon / public” key
   • SUPABASE_SERVICE_ROLE_KEY ← the “service_role” key (secret — server only)
4. 4
   Resend — sign up, go to API Keys → Create API Key, and copy it once (it’s only shown one time) into RESEND_API_KEY.
5. 5
   Spaceship — only if you still need a domain. Cheap domains, and it has a DNS API so you (or Claude) can automate the records. Buy the domain, then in the API Manager create a key → SPACESHIP_API_KEY + SPACESHIP_API_SECRET. Then point its nameservers at Vercel and add Resend’s DNS records.

Your finished .env.local looks like this:

# Supabase -> Project Settings -> API
NEXT_PUBLIC_SUPABASE_URL=https://YOUR-PROJECT.supabase.co
NEXT_PUBLIC_SUPABASE_ANON_KEY=eyJhbGci...          # "anon / public" key
SUPABASE_SERVICE_ROLE_KEY=eyJhbGci...              # "service_role" - server only, keep secret

# Resend -> API Keys
RESEND_API_KEY=re_xxxxxxxxxxxxxxxx

# Spaceship (optional) - only if you bought your domain there + want DNS automation
SPACESHIP_API_KEY=xxxxxxxxxxxxxxxx
SPACESHIP_API_SECRET=xxxxxxxxxxxxxxxx

Restart pnpm dev after editing so it picks up the new values. Never commit .env.local — and in production, set the same keys in Vercel’s Environment Variables.

Run it locally, then ship it

With the tools installed and your keys in place, start the dev server:

pnpm dev

Open the URL it prints (usually http://localhost:3000). If the page loads, your whole stack works — that’s your smoke test.

Now put it on the internet. Log in once, then deploy from the project folder:

vercel

Follow the prompts — Vercel links the repo, builds it, and hands you a live URL. That’s a “deploy”: your app, on the internet, for anyone to visit. Add the same .env.local values under Project → Settings → Environment Variables so production has them too, then vercel --prod when you’re ready to ship for real.

If something breaks

Open a fresh terminal so all PATH changes load, then run:

claude doctor

It checks the install and PATH and tells you exactly what’s wrong. If claude still isn’t on your PATH, reinstall it straight from npm:

npm install -g @anthropic-ai/claude-code

Now make Claude Code yours

The stack is installed — here’s how we tune Claude Code itself. Each of these is a small, public add-on you can drop in today.