Claude Code Guide

Ship & fix: the complete guide

From dev to deploy to bug fixes — full-chain how-to with TL;DR and searchable FAQs.

Ship & fix: the complete guide

The full loop from code to a live site to bug fixes — let Claude turn your project into a website real people can visit.

GitHub Vercel Supabase Namecheap Stripe OpenAI / DeepSeek

① First deploy

From zero to a live URL in 5 steps: GitHub → Vercel → domain.

② Daily updates

Edit code → one-line push → site updates in 1–3 minutes.

③ Fix a bug

Describe it → Claude finds the cause → fix auto-redeploys.

④ Rollback

Broke something? One click in Vercel takes you back to the last good build — about 30 seconds.

1 · What platforms do you actually need?

An analogy: think of your site as a real-world shop — your code is the blueprint, GitHub is the safe where blueprints live, Vercel is the construction crew, your domain is the street address, Supabase is the storeroom, and Stripe is the cash register.

Code & deploy

Turn code into a live site

GitHub · free · code hosting + version history for rollback

Vercel · Hobby free / Pro $20·mo · auto-deploy on every push

Domain & traffic

How users find your site

Domain registrar (Namecheap / GoDaddy / Cloudflare) · $10–20·yr · buy yoursite.com, point DNS at Vercel

Data & services

Users, subscriptions, cache

Supabase · free tier is plenty / Pro $25·mo · PostgreSQL plus a visual admin

Stripe · 2.9% + $0.30·transaction, no monthly fee · subscriptions, cards, refunds

AI & third-party

Plug in features through API keys

OpenAI / DeepSeek / Resend · usage-based billing · keys live in Vercel env vars; the code reads them at runtime

2 · First deploy from scratch

Create a GitHub repo and push your code

git init && git add . && git commit -m "first commit" && git remote add origin [repo URL] && git push -u origin main

Import the project into Vercel

Sign into vercel.com with GitHub → Add New Project → pick the repo you just created → Deploy. Vercel auto-detects the framework (Next.js, React, etc.) — you don't need to configure a build command by hand.

Set up environment variables (the easiest step to forget!)

API keys and database passwords must not live in the code. Set them in Vercel → project → Settings → Environment Variables:

DEEPSEEK_API_KEY = sk-xxxxxxxx
SUPABASE_URL = https://xxx.supabase.co
SUPABASE_ANON_KEY = eyJxxxxxxxx
STRIPE_SECRET_KEY = sk_live_xxxxxxxx

⚠ After adding them you must Redeploy once for the changes to take effect.

Connect your custom domain

The free yourproject.vercel.app URL already works. If you bought your own domain: Vercel project → Settings → Domains → enter the domain → follow the instructions to add an A record or CNAME at your registrar. DNS can take anywhere from 5 minutes to 24 hours to propagate.

Verify it's live

Open your domain and confirm the page loads. The Vercel Deployments tab should read ● Ready — if it shows ● Error, the build failed; click in to read the log.

3 · Daily update flow (the highest-frequency one)

The whole thing in one sentence: edit locally → Claude runs git push → Vercel auto-builds → site updates in 1–3 minutes. You don't have to log into anything along the way.

The one-liner you run after every code change

git add . && git commit -m "update" && git push

Edit locally

Claude edits files in your project folder

git push

Code uploads to GitHub

Vercel auto-builds

Picks up the new code, ~1–3 min

Site updated

Users worldwide see the new version

4 · Three kinds of changes (different propagation times)

Code change

⏱ 1–3 minutes

Local file → git push → Vercel auto-deploys. E.g. fixing a bug, restyling, adding a feature.

Env-var change

⏱ 1–3 minutes after Redeploy

Vercel → Settings → Env Vars → click Redeploy. E.g. new API key, key rotation.

Database change

⏱ Immediate

Edit through the Supabase admin or via API. E.g. fixing user data, clearing cache.

5 · Something broke? Full triage flow

Describe the problem (the more specific, the better)

Tell Claude: which page · what's happening · when it started · all users or just you.

For example: "the login button on the homepage doesn't respond when I click it; it worked yesterday, started this morning, same in another browser." A screenshot is even better — Claude can read images directly.

Claude hunts for the root cause

It walks through, in order:

Reads the relevant code files for logic bugs
Uses a browser tool to inspect actual network requests for failing endpoints
Checks the Vercel build log for failed deploys
Checks Supabase for unexpected data
Checks third-party APIs (DeepSeek / Stripe) for outages

Confirm the cause and pick the right fix

Code bug

Claude edits the file → git push (auto-redeploys)

API key missing/expired

Update env var in Vercel → manual Redeploy

Bad data in the DB

Edit directly in the Supabase admin (no redeploy needed)

Third-party outage

Wait for the provider to recover — out of your hands

Domain / DNS issue

Check DNS settings at your registrar

Verify the fix

Claude opens the site through a browser tool, exercises the broken flow for real, and confirms it's working before telling you "fixed."

test fix → git push → wait for Vercel deploy → verify in browser → done

6 · How to roll back if a change breaks things

Don't panic: every past version is preserved in GitHub and Vercel. You can always click back to a working build.

Vercel one-click rollback

Fastest · 30 seconds

Vercel → Deployments → find the last good build → ⋯ menu → "Promote to Production".

Git revert

More precise

Claude runs git revert <commit> to undo a specific change → push.

Git reset

Destructive

Claude runs git reset --hard to jump back to a specific commit (later changes are lost).

7 · Most common questions

6 / 6 items

Blank page / 500 error

Cause: a code bug or a missing env var.

Fix: read the Vercel build log for the actual error, or check that all env vars are set.

Edited the code, but the site didn't change

Cause: you forgot to git push, or push failed.

Fix: confirm the push succeeded, and check Vercel for a new deployment.

Added an env var but nothing changed

Cause: you didn't redeploy.

Fix: Vercel → Deployments → latest → click "Redeploy".

Custom domain unreachable, but .vercel.app works

Cause: DNS isn't set, or hasn't propagated.

Fix: check DNS at your registrar; allow up to 24 hours.

A feature suddenly stopped working (payments / AI)

Cause: third-party API key expired, or the account hit a billing issue.

Fix: log into the provider, top up or rotate the key.

Vercel deployment shows Error

Cause: code syntax error or a dependency issue.

Fix: click the Error to see the log; Claude can read it and find the cause.

8 · Post-launch maintenance checklist

Monthly check-in

Vercel usage vs. the free tier
Supabase database storage
Third-party API bills
Domain expiry (renew early)

Security notes

API keys never go into code
Audit Supabase access policies regularly
Keep Stripe live key and test key separate
Public repo: confirm no secrets are committed

One thing to remember: you don't need to operate most of these platforms yourself. Describe the problem to Claude, and Claude will tell you exactly which Vercel page to open and which button to click — or just handle the code-side fix for you. Your job is the final decision and sign-off.

Open the full interactive index →

Vexilo is the missing index for Claude Code — 31 agents, 125 commands, 123 skills and more, organized by scenario. Browse free; unlock search, filters and one-click CLAUDE.md export with a one-time $19 licence.