Ship a real website
in a single day.

What this actually is

A field guide, not a tutorial. Every step below is something I did to ship transfast.ae — a real site for a UAE container-trucking company — including the parts that went wrong.

The point isn't "AI writes code." Everyone knows that. The point is a workflow where one agent carries a project from a vague idea to a live domain: it asks what you actually need, writes a plan, builds against that plan, reviews its own work, and then deploys — through the same chat window.

What you'll end up with

Get the tools in place

Four things. Nothing exotic.

# install once, globally
npm install -g @anthropic-ai/claude-code

# cd into your project folder, then just:
claude

Don't start by asking for code

This is the part most people skip, and it's the part that decides whether you get something real or something generic.

Step 1 — Make it interview you

Before any code exists, make the agent ask questions. What's the business? Who's the customer? What should the site rank for? Every answer removes a guess it would otherwise make badly.

Step 2 — Get a written plan before a single file

Ask for a spec, then an implementation plan, saved as files in the repo. This sounds like overhead. It isn't — it's what stops the agent from drifting halfway through and inventing a different architecture than the one you agreed on.

Step 3 — Build in small, reviewed chunks

One task at a time, each ending in a working build and a commit. After each chunk, have it review its own diff against the plan. It catches a surprising amount — in my build it flagged its own colour-contrast failures and a meta description 11 characters over the limit.

Give the agent hands

MCP (Model Context Protocol) lets the agent talk to real services — your Cloudflare account, your database, your design tool — instead of just telling you what to click.

Without MCP, deployment goes: agent writes instructions → you read them → you click through a dashboard. With MCP, the agent creates the project, configures DNS, and attaches the domain itself, then verifies it worked.

Connecting a server

Inside Claude Code, run /mcp to see available servers and authorize them through your browser. Cloudflare, GitHub, Sentry, Supabase, Figma and many others publish official ones.

/mcp          # list + authorize servers

# then just ask in plain English:
"Create a Cloudflare Pages project and deploy this,
 then attach my domain and verify it's serving."

Get it on the internet

# one-time browser login
npx wrangler login

# build, then ship the static output
npm run build
npx wrangler pages deploy dist --project-name=my-site

✨ Deployment complete! https://my-site.pages.dev

Add it as a script so redeploying is one word:

"scripts": {
  "deploy": "astro build && wrangler pages deploy"
}

Pointing your domain at it

1. Add your domain in Cloudflare → it gives you two nameservers.
2. At your registrar, replace the existing nameservers with those two. Remove the old ones entirely — leaving one behind causes random failures.
3. Wait for the zone to go active (often minutes, officially up to 24h).
4. In your Pages project → Custom domains → add the apex and the www version. SSL is automatic.

Five things that bit me

The parts no tutorial mentions, because they only show up when you ship something real.

The short version

• Install Claude Code, open it in your project
• Make it interview you before it writes anything
• Get a written spec and plan, saved in the repo
• Build one task at a time, verifying and committing each
• Connect the Cloudflare MCP with /mcp
• Deploy with wrangler pages deploy
• Point your domain, add the custom domain, done
• Run Lighthouse against the live URL, not localhost