Guide
How to build a website with Claude Code: the 7 honest steps
You’ll see claims that a gorgeous website takes 5 minutes and one prompt. We haven’t found that to be true. A site that holds up in front of a client takes seven steps, and in our estimate a first build takes 5 to 10 hours in total. Here they are, with how long each one takes and the mistake that costs the most time. The same steps work in Codex.
1. Write the brief before you open Claude Code
Six lines are enough: who the business is, who it’s for, the one action a visitor should take, the proof you can show, the words to avoid, and the sector it sits in. Then ask Claude to question you before it proposes anything. Allow 20 to 30 minutes. The usual mistake is describing the look before the business, since “dark, glossy, cinematic” tells Claude nothing about what the site has to do.
2. Choose a direction from three
Ask for three visual directions, each a sentence on mood, colour, and type, and pick one before anything is built. Allow 30 to 45 minutes. Skipping this step is why so many AI-built sites look alike: a vague brief returns the average of every site Claude has seen. The prompts for steps 1 and 2 are free on our free prompts page.
3. Decide what the visitor does in the first 10 seconds
Give the first screen one action that belongs to what the business sells. A flight school lets you draw a climb-out; a pen maker lets you pick up the pen. One idea, not five, and it has to work by touch as well as with a mouse. Allow 30 to 60 minutes. The common failure is a hero that’s a beautiful film and nothing else.
4. Make the media before you build
Generate the hero film, its poster frame, six stills in one light and colour grade, and a phone crop of each, with a file size limit agreed first. Tools such as Google Flow and Higgsfield (affiliate link) can make all of it, so test one shot before you commit and check what the licence lets you do with the result. Allow 1 to 2 hours. Building first and generating later is how you end up with pictures that don’t match each other.
5. Build, then change one thing at a time
Give Claude the brief, the direction, the interaction, and the media, and review the result in a browser. From there, send a screenshot with one thing marked and ask for one change. Expect 3 to 6 rounds over 90 minutes to 3 hours. Asking for five changes at once, or simply “make it better”, is how you lose the version you liked.
6. Test on a real phone, with reduced motion on
Open the site on a phone, not a narrow browser window, and try every interaction with your thumb. Then switch on reduced motion in your device settings and check that every word and link still works. Allow 45 to 90 minutes. Hover effects vanish on touch, headings clip, and a scroll that felt smooth on a laptop can stall on a phone.
7. Read every word aloud
Replace every placeholder, invented name, date, and figure with something you can prove, then check the titles, alt text, and links, and run the page on the phone once more. Allow 30 to 60 minutes. Generated copy sounds right and says little, and a client will find a made-up figure in seconds.
Where the time goes
Steps 1 to 4 are where most first builds go wrong, because each one is a decision that’s hard to undo once the code exists. Steps 5 to 7 are slower than people expect, because they’re where a site meets real hands and real readers.
Every template in the Vibesignet library starts from a worked brief, a chosen direction, one tested interaction, and a stated list of the photographs and films it needs, so the guesswork in steps 1 to 4 is already done, and each comes with a live build to compare yours against in steps 5 to 7. It doesn’t remove the work: you still decide, test, and write the words that are true.
What you need before you start
Five things, none of them exotic. Claude Code builds the site. For step 4 you need an image and film tool: we start in Google Flow and use Higgsfield after it. A host puts the finished site online, such as Vercel, which runs Vibesignet itself, and a domain from a registrar such as Namecheap gives it an address. And a real phone, for step 6. The Higgsfield links on this page are affiliate links, so we may earn a commission if you sign up through them. Pricing, credit costs, and licence terms for all of these change, so read the current ones before you commit to a plan.
Get the prompt for every step
The seven steps above tell you what to do. The full guide gives you the exact prompt to paste for each one.
- A prompt or checklist for every step. From the six-line brief to the table that finds every invented figure on your page.
- A free access key. It unlocks one complete template prompt of your choice in Claude Code, Codex, Cursor, or any tool that connects to MCP servers.
- First word on paid plans. We email you before they open.
The guide gets you through one site. The Vibesignet library does the groundwork for every template in it: each starts from a worked brief, a chosen direction, and one tested interaction, with a live build beside it to compare yours against.
Free. One confirmation email, then the guide.
We send a confirmation email first; the guide arrives once you click its link. See our Privacy Policy.
Here is how the prompts read. This is the start of the step 3 prompt:
Propose three first-screen interactions for this brand. Each must:
- be an action the visitor performs in the first 10 seconds, taken from what
the business actually does or sells
- work by touch as well as by mouse, with no hover needed
...and the rest arrives with the guide.