Part II: Pick a Path (build and review the preview)04
Chapter 04
Path A: How to build a website with Claude Code
No purple gradients. Promise.
Give Claude Code a real brief and it builds the whole site: it designs it, writes the copy from your material, checks it at phone size and puts it on a free Cloudflare preview address. Your part is the photos, a one-page brief and honest feedback, and you need Claude Pro (US$20 a month) plus free Cloudflare and GitHub accounts.
Most people need this path, and nothing more complicated. One brief, one prompt, no domain needed yet. Haven't set up yet? Do your three accounts and the agent setup first.
Why most AI websites look the same
You've seen them. Purple gradient hero. "Welcome to [Business]" in a huge font. Three cards with emoji icons. A stock photo of people laughing at a laptop. Everyone calls it AI slop, and it's real, but it isn't the AI's fault.
It's the prompt. "Make me a website for my bakery" gives the model nothing to work with, so it hands you the average of every bakery website ever made. The average is boring by definition.
Opus 5.5 is a genuinely good designer. Give it real material and real taste to work from, then get out of its way. That's what the brief is for.
Step 1: Gather your material
Make a folder inside Websites named after your business. Put in it whatever you have:
- Photos. Your actual work, your space, your products, your face. Real photos beat everything. Phone photos are fine if the light's decent. Twenty mediocre real photos beat one perfect stock image.
- Logo, if you have one. Any format.
- Text you already have. Old website, Instagram bio, menu, price list, a Google Doc. Doesn't need to be good. The agent rewrites it.
- Your old site's address, if there is one. The agent can pull everything from it.
Step 2: Write the brief
Fill this in. Short answers are fine. Honest answers are better than impressive ones.
BUSINESS
What you do, in one or two sentences:
Where you are / who you serve:
What makes you different from the three competitors down the road:
VISITORS
Who's landing on this site:
The ONE thing you want them to do (call, book, order, get a quote, visit):
The questions they always ask you before buying:
PAGES
[e.g. Home, Menu, About, Catering, Contact. Or "one long page".]
THE FEEL
Three words for how it should feel (not "modern" and "clean", everyone says
that. Try "warm, flour-dusted, slightly chaotic" or "quiet, expensive, gallery"):
Sites you love (any industry) and what exactly you love about each:
1.
2.
3.
Sites or styles you hate:
Borrowing from someone else's look (a famous brand, a book series, a movie)?
Say "evoke it, don't copy it": no names, logos or characters that aren't yours.
Brand colours / fonts, if you have them (or "make them up"):
MOTION AND INTERACTION
[None / subtle / show off.] Any specific idea? ("the menu could be a
flippable card deck", "the hero reacts to the mouse", "scroll through the
steps of making sourdough")
LANGUAGES
[English only / English and French / ...]
MATERIAL
Everything is in this folder: [path]. Old site: [URL or none].Step 3: The build prompt
New session in your business folder. Opus 5.5, effort High. Paste your brief, then this underneath it:
Above is my brief. Build my website.
You're the designer here, not just the developer. Use the brief and the
material in this folder, then make real design decisions: a concept, a type
pairing, a colour system, a layout idea that belongs to THIS business. Push
it. I would rather you take a big swing I have to pull back than hand me
something safe. Write your design direction to DESIGN.md before you build,
and follow it.
Hard no's: generic gradient heroes, "Welcome to [business]" headlines, rows of
three identical cards with icons, emoji as icons, stock-photo people, fake
testimonials, lorem ipsum, and any copy that could be on a competitor's site.
Write real copy from my material, in plain language, specific to me. If you
need a fact you don't have (prices, hours, address), leave a clearly marked
TODO and list them all for me at the end. Don't invent them.
Build it properly:
- A Vite/static site deployed with Cloudflare's cf CLI. Generate real HTML
for each public page so visitors and search engines get the content
without waiting for JavaScript. Use React only for interactions that
benefit from it. I'm on Workers [Free / Paid]; stay within its limits
and tell me before adding anything that needs Paid.
- Configure this new project with cf init and cloudflare.config.ts. Pin
the tested cf version and commit the lockfile. Keep the configuration
in the repo, with .cloudflare output and secrets ignored.
- Keep all the words and data in Markdown or data files, separate from the
design, so a redesign never touches the content.
- Fast: optimised and properly sized images, minimal JavaScript, and no
layout shift from web fonts (CLS under 0.1). It should score 90+ on mobile
Lighthouse for performance, accessibility and best practices on staging.
SEO gets checked on the live domain, since staging is noindex on purpose.
- Motion that fits the brief, and that respects reduced-motion settings.
- Fully responsive. Design the phone version on purpose, most visitors
will be on one.
- Accessible: real headings, alt text, keyboard navigation, readable
contrast.
- SEO basics: titles, descriptions, Open Graph images, sitemap, robots.txt,
schema.org structured data for my business.
Ship it:
- Build and check a local preview first. Then create a private GitHub repo
and push, using the GitHub browser sign-in if needed.
- Run type checks, tests, cf build and cf deploy --dry-run. Keep type
checks separate: cf can invoke the framework build directly.
- When those pass, use cf auth login if needed and tell me when to review
access. Use cf deploy for a separate staging Worker on workers.dev.
No custom domain, vault or CI token needed for this local deploy.
- Keep staging noindex. It is still public, so use no private customer data.
- Open the staging site yourself, check every page on desktop and phone
sizes, and fix anything that looks off before you show me.
- Leave automatic GitHub deployments for the optional tokens appendix.
Keep this new site on cf; do not add Wrangler as a second setup path.
Then send me the staging link, a short summary of the design direction, and
the list of TODOs you need from me.Video coming soon
- The staging site, checked on a phone
Step 4: Review like a client, not a developer
Open the staging link on your phone first. Then give feedback the way you'd give it to a human designer:
- Specific: "The hero photo is too dark, use the one of the counter instead" beats "make it pop".
- Why, not just what: "Customers always ask about gluten-free, so it needs to be on the home page."
- Batch it. One message with ten points beats ten messages.
- Answer its TODO list in the same message.
Questions people ask before they start
Can Claude build a website for free? Not the real thing. Claude Code isn't on the free plan; it starts with Claude Pro at US$20 a month (checked 17 November 2026). There's a yearly plan at US$200 up front, but most people only need Claude while they build, so pay monthly. The free plan now includes Claude Design, which is fine for trying out a look. It makes designs and prototypes, not a live site with a working contact form on your domain, though it can hand a design to Claude Code to build.
I made a site in Claude chat or Claude Design. How do I put it online? Hand it to Claude Code. A published artifact gets a public link that anyone can open without a Claude account (Claude's help). That's fine for sharing a page. But it's a Claude link, not your domain, and none of the business setup in this guide comes with it: the domain, the contact form's email, analytics, Search Console. In Claude Design, open Export → Handoff to Claude Code → Send to local coding agent, or Export as standalone HTML into your business folder (Claude Design's export options). Then run the build prompt above, with this added under your brief:
I designed this site in Claude [chat / Design]. The design is in
[FILE, FOLDER OR HANDOFF]. Keep its look and its content, and build it
as my real website following everything below.Used the standalone Claude Design at claude.ai/design? It closes on 14 December 2026, so export before then.
Do I need a design skill or plugin for Claude Code? No. Design skills make Claude settle on a look before it writes code and steer it away from the generic one. The build prompt above already does that, and DESIGN.md keeps it on track. If you want it on every project anyway, use Anthropic's own Frontend Design plugin: it's verified by Anthropic and switches on by itself when Claude builds a page. In the Code tab, click + next to the prompt box, then Add plugins, or Plugins → Browse plugins (how to install plugins). Skip design skills from strangers on GitHub unless you've read what they tell Claude to do.
Claude chat or Claude Code? Claude Code. The chat writes code and hands it back to you, and then you're stuck with a file you don't know what to do with. Claude Code works on your computer: it creates the files, runs the preview, fixes what breaks and deploys the site. That difference is the whole point of this guide.
Lovable or Claude Code? Lovable is the easier start, in a browser tab with a free plan to try. For a business site I'd still use Claude Code: the year-one bill comes out about the same, and it also sets up the domain, email and analytics in your own accounts. Lovable vs Claude Code, side by side, including how to move a site you already built in Lovable.
Does Claude host the website? No. Cloudflare does, and the free plan covers most small business sites. Claude sets it up for you. What it all costs, per month.
Will a website Claude built show up on Google? Yes, if it's built for it, and the prompt above asks for exactly that: real HTML for every page so Google doesn't wait on JavaScript, titles and descriptions, a sitemap, structured data for your business, and a fast phone score. Then the analytics chapter has the agent verify Search Console, so you can see what Google sees. Ranking still comes down to what your pages say.
Can Claude build my site on Wix, WordPress or Shopify? It can write WordPress themes and plugins or Shopify theme code, and snippets for the custom-code boxes on Wix and Squarespace. But then you pay for the platform and build inside its limits, which is the thing you were trying to get away from. My answer is a site of your own: WordPress compared, Wix and Squarespace compared, and for selling things, Shopify or Stripe.
Do I need to know how to code? No. You never read the code; you read the preview on your phone. You don't need the terminal either: it all happens in the Code tab of the Claude desktop app.
Is the website mine? Yes. The code lives in your GitHub account and the site runs on your Cloudflare account. Cancel Claude after launch and the site keeps running. Pick it back up when you want changes.
What do I type? The brief and the build prompt above. Every other prompt in the book is in the prompt pack.
Add-ons
- Contact form and email: chapter 8, after the domain is ready. You can build the form layout now.
- Analytics: chapter 9. Do it before launch.
- Domain: chapter 7, when you like the preview.
- Live on your domain: chapter 10, after forms and analytics are ready.
Or, if you need other people editing content, go to Path B. Selling things, Path C.
On a phone, swipe left and right to turn pages.