library

image

effects

mcp

workflow · 4 min read

How to vibe code a website that doesn't look vibe coded

To vibe code a website, you describe what you want to an AI tool in plain words and it writes the code. Today that takes one app and no terminal. The hard part is no longer getting a site. It is getting one that doesn't look like every other vibe coded site, and that comes down to one rule: decide the design yourself, and let the AI build on it.

At this point anyone can do it. The technical skill you need is about what it takes to search for instructions and follow them.

How to vibe code: the steps

  1. Download Claude for your computer and open Claude Code inside it.
  2. Start from a design, not a description. Use a finished template's prompt, or two or three sections you designed yourself.
  3. Say what you want built in plain words, and let it build.
  4. Look at the result and say what's wrong, the way you'd tell a colleague.
  5. Repeat until it is right, then put it live.

Compared with 2025, a lot has gone away. You don't use the terminal. You don't copy and paste code anywhere. You don't debug and hunt for issues yourself. That happens automatically now.

If you want the longer version of the first build, see how to build a website with Claude Code.

How to tell a website was vibe coded

The giveaways are the fonts, the spacing, particular interface elements and the colours.

For a long time the easiest sign was a purple glow, purple running to pink, on site after site. Then Claude Design launched and the look changed: a mix of serif and sans-serif type, Instrument Serif everywhere, and small labels in capitals that say things like "SECTION 1" and "SECTION 2".

The details move on, but the cause stays the same. When the AI picks the look, it picks the look it gives everyone. We went into that in why every AI website looks the same.

The one thing never to let the AI decide

Never let the AI decide the main design theme of the site.

Make a base yourself first. Two or three sections is enough, so that when Claude builds the rest it has plenty to pull from. Then ask it to build on that. The AI is good at expanding a design and making it richer. It is poor at inventing one worth expanding.

If you are a designer, there's a second route: let Claude build the whole site first, bring it into Figma, edit it there the way you like, then ask Claude to change the site to match.

A first build goes wrong when the AI is left to make a lot of decisions. In our experience this is worse with Codex than with Claude. Claude is able to make choices that aren't the obvious ones. Codex doesn't, so unless you tell Codex exactly what you want, the result can be very generic. Claude does it too sometimes, just not every time.

A real build: EasyLog 3D in about 40 minutes

EasyLog 3D is a template of ours that started as an update to one we made more than nine months ago. The old version had a tree branch where moss appeared when you moved the mouse over it. It did that with two images on top of each other.

The new build went like this:

  1. The old template went in as a reference image. Since an image can't show behaviour, the behaviour was explained in words: when the mouse is over the branch, the branch changes.
  2. Claude was asked to rebuild it piece by piece from the image, and to make it real 3D.
  3. The first result looked like Roblox. There were no real textures, only material settings applied to the branch.
  4. One request fixed it: increase the quality of the textures. Claude found high-quality open textures on its own and used them. That made the result look very good.
  5. Then came the variations. Claude was asked for more versions of the same scene, and the template now has fire, frost and moss themes beside the blossom.

The whole thing took 30 to 40 minutes, and most of that was Claude thinking.

Two things in that build are worth copying. It started from an existing design, not from a sentence. And when the result looked cheap, the fix was to say what was wrong with the quality, not to describe a new design.

FAQ

Do I need to know how to code to vibe code a website?

No. You need to be able to follow instructions and say clearly what you want. Claude Code runs inside the Claude app, so there's no terminal to learn.

Why does my vibe coded website look generic?

Because the AI chose the design. Give it a base to build on: a finished template, or a couple of sections you designed yourself.

Is Claude or Codex better for vibe coding a website?

In our experience Claude copes better when you leave decisions open, and Codex needs to be told exactly what you want. With a precise design to follow, both can build it.

How long does it take to vibe code a website?

A single section with real 3D took us 30 to 40 minutes, mostly waiting for Claude. A whole site depends on how much of the design is decided before you start.