How to Design a Landing Page With Claude Code
The five steps, the brief and the checks we used to build a real ClaroSi page with Claude Code, written so you can follow them on your own site.

You have heard that AI can build a web page, but the results you have seen look generic. How do you get a page that actually fits your site?
Give Claude Code a short, plain brief inside your website's own folder. Name the files that hold your look, say who the page is for and the one action it should lead to, and ask for a plan before anything is built. Then check the page in a real browser at phone and desktop width, measure what it downloads, and only publish after a person has reviewed a preview link.
What this guide is based on: one real page, ClaroSi's Claude Code page, built in November 2026. The steps describe how we worked. They are not a promise of speed, rankings or results on your site.
What is Claude Code?
Claude Code is an AI coding assistant made by Anthropic. It works in a terminal, inside the folder that holds your website, so it can read your existing files, propose changes and run checks. Think of it as a capable assistant who can see your whole project folder, but who still needs a clear brief and a person to approve the work.1
That last point matters. Claude Code can edit files and run commands if you allow it. Keep the approval step: read the plan, review the change, and decide yourself what goes live.
Step 1: How do you write a brief Claude Code can follow?
Start with plain English, not design adjectives. A good brief answers three questions: who is the page for, what is the one action it should lead to, and which files hold the look it should match.
- Say who the page is for and the one action you want them to take.
- Name the files that hold your style, for example your main stylesheet.
- Ask for a plan first, and approve it before anything is built.
Because Claude Code works inside your project, the brief can point at real files instead of describing a style from memory. That one habit does more to avoid a generic result than any amount of “make it modern and beautiful”.
Do this: write your brief in five or six short lines and end it with “Show me the plan before you build.”
Step 2: How do you keep the new page looking like the rest of your site?
Reuse what you already have. Every new ClaroSi page starts from the same colours and fonts as the rest of the site. Claude Code reads them from the stylesheets, so nothing is invented.
- One font for headings and one for reading text, the same as the rest of the site.
- The existing colour set, with any new colour limited to the one page that needs it.
- A contrast check so small text stays readable.
On our page, the site's ink, cobalt and cyan stayed, and one extra warm colour was added only on that page, to tie it to Claude Code. Everywhere else stayed unchanged.
Do this: tell Claude Code “Do not add new colours” unless you have a reason, and name the one exception if you do.
Step 3: How should you plan the sections?
A landing page is a short story told in blocks. Agree the order of the blocks first, then write the words, then style them. Changing the order after the styling is done costs far more time.
- One idea per section, each with a clear heading.
- Proof near the top, the next step at the bottom.
- Every section designed for a phone as well as a desktop.
| Section | Its one job |
|---|---|
| Hero | Make one clear promise. |
| Three cards | Answer the three questions a visitor asks first. |
| Proof | Show one real, measured result. |
| Next step | Offer a single action. |
Do this: ask Claude Code for the outline as a list of sections before it writes any styling.
Step 4: How do you check the page before anyone sees it?
Ask Claude Code to open the page in a real browser and look at it, not just to say it is finished. On ClaroSi, that check covers three things.
- Phone, tablet and desktop width, with nothing spilling off the side of the screen.
- Error messages in the browser and links that go nowhere.
- Page weight: how much the page downloads, measured before and after.
Measuring is where real improvements show up. During this build, the check found a large looping animation on the homepage. We re-encoded it, compared the frames side by side, and kept the replacement only after the visual check passed. That is a file-level check, not a promise that every visitor will see the same loading time.
Do this: end every brief with “Check it at phone width and measure the page weight before you say it is done.”
Step 5: How do you publish safely?
Treat publishing as a human decision, every time. The way we work has four stages:
- Separate working copy. Changes are made away from the live site, with a written note on what changed and why.
- Shared history. The change is saved to GitHub, so it can be reviewed and undone.
- Private preview. A preview link shows the page before it is public, so you can check it on your own phone.
- Your approval. It only goes live when a person says yes.
You do not need these exact tools to follow the idea. What matters is that nothing reaches visitors without a preview and a person's approval.
Do this: never let an AI tool publish straight to your live site. Keep a preview step, even for one-line changes.
A landing page brief you can copy
This is the shape we use for every ClaroSi landing page. Replace the words in square brackets.
Landing page brief 7 lines · paste into Claude Code
- PageBuild a landing page for [PAGE TOPIC].
- ReaderWho it is for: [AUDIENCE].
- One actionThe one action: [BUTTON TEXT] → [LINK].
One page, one action. A single button makes every section easier to write.
- LookUse the look in [YOUR STYLESHEET]. Do not add new colours.
Point at real files. Naming the stylesheets keeps every page in the same family.
- SectionsSections: hero, three cards, one real proof point, next step, footer.
Ask for proof, not adjectives. A measured result beats “fast” or “beautiful” in the copy.
- ChecksCheck it at phone width and measure the page weight before you say it is done.
- GateShow me the plan first.
Plan before build. Approving the outline first saves a round of rework.
What are the common mistakes?
- Describing a style instead of pointing at it. “Clean and modern” produces a page that looks like everyone else's.
- Skipping the plan. Building first and changing the structure later doubles the work.
- Trusting “done”. Ask to see the page at phone width and the measured page weight.
- Inventing proof. Do not let the page claim results, reviews or numbers you cannot back up.
- Publishing without a preview. Keep a person in the approval step.
Common questions about Claude Code
Do I need to know how to code to use Claude Code?
It helps to understand the basics of how your website's files are organised, but you do not need to write the code yourself. You do need to read the plan, review what changed and decide what goes live. Learning those review habits matters more than learning to type code.
Can Claude Code design a page that matches my existing website?
Yes, if you point it at the files that hold your current look, such as your stylesheets. It can then reuse your fonts, colours and spacing instead of inventing new ones. Without those files it will guess, and the result tends to look generic.
Will Claude Code publish changes to my live site?
Only if you set it up to. Keep your changes in a separate working copy, review them on a private preview link, and publish yourself. That way nothing reaches visitors without a person's approval.
How do I stop an AI-built page from looking generic?
Give a brief with a specific audience, one action, named style files and a real piece of proof. Ask for a plan before it builds. Generic pages usually come from generic briefs.
Is a page built with Claude Code good for search?
It can be, if the page is useful, accurate and checked by a person. Google's guidance focuses on the quality and accuracy of content, not on which tool produced it. A tool does not guarantee rankings.
Sources
- Claude Code documentation: overview. Anthropic's description of what Claude Code is and how it works in a project folder.
- Google Search Central: Guidance on using generative AI content on your website. Google advises accuracy, quality, relevance and human checking for generated content.
- web.dev: Web Vitals. Google's explanation of the page experience measurements that page weight affects.
Refresh note: Claude Code's features and settings change. Check the current documentation before relying on a specific command or permission. The animation check described above is a ClaroSi build record, checked 20 November 2026.
See the steps in action on ClaroSi's Claude Code page, with an interactive walkthrough and the layouts it produced.