← Blog
ToolsUpdated 2026-10-11 · 5 min read

Prompting Claude vs ChatGPT for Web Design

How to structure a web design request for Claude or ChatGPT, what to specify in both, and how to iterate without losing decisions. A guide, not a ranking.

Claude and ChatGPT can both build a hero section from a detailed spec, so the difference you notice in practice comes mostly from how you structure the request and how you iterate on the result. This guide covers what to specify for either model, how to shape the request for each, and how to keep your decisions intact across revisions.

It does not rank the two models. HeroPrompts has not run a comparison between them, so nothing here is a finding about which one writes better code.

What to specify for both

Whichever chat you use, the same decisions need to be in the request, because each one is a decision the model would otherwise make for you:

  • The stack, on one line.
  • The palette as named tokens, with hex values.
  • The fonts, by name and weight.
  • Timing in milliseconds or seconds, including the easing.
  • One signature mechanic, with what starts it.
  • Responsive rules, a reduced-motion path and an avoid line.
  • The output: which files you want back, and whether they should be complete.
  • The six-part framework for web design covers the full structure. The difference between a vague request and a specific one is clearest at the level of a single line. Compare these two:

    Vague: "Make the headline bold and modern."

    Specific: "H1: Hanken 800, clamp(44px, 6vw, 72px), leading-[1.02], tracking-[-0.045em]."

    The second line leaves the model nothing to choose, and you can check it against the output. The headline in Parapet is specified that way, and so is the rest of its layout.

    Specification also covers what the model should not do. Merrow's background spells out its reduced-motion case in full, so the behaviour is decided before anyone opens a browser:

    Merrow — Drifting Gradient Background — live preview
    Merrow — Drifting Gradient Background — A deep teal, slate, plum and rust gradient slides slowly behind a headline, with fine grain shimmering over it and a copy button rising into place.

    Shaping the request for Claude

    A long spec with clear headings is easy to follow in a single reply. Split the request into labelled sections: stack, colour system, typography, layout, signature interaction, motion, responsive behaviour, accessibility and file structure. Each heading tells the model which decision it is reading, and it tells you where to look when a value is wrong.

    End with a request for the file list, then the files: "List the files you will create, then write each one in full." Seeing the file list first makes it easier to spot a file you did not expect before you read any code.

    Revisions work best when they name one value and the value it must keep. For example: "Change only the subheadline size to 18px. Keep every other value identical, including the token names."

    Shaping the request for ChatGPT

    Keep the whole spec in one message. Put the constraints that must not change in a short numbered list near the top, so they are read before the detail. End with the output format.

    If you plan to paste the reply into a project, ask for complete files rather than fragments. A complete file can be checked against the spec from top to bottom, while a fragment hides whatever it left out. Repeat the avoid line next to the output request, so the constraint sits in the same message as the instruction the reply answers.

    Revisions follow the same rule: name the one thing to change, and say that everything else stays identical.

    Iterating without losing decisions

    Vague revisions invite drift in either model. A palette value gets "improved", a timing gets rounded or a layout gets simplified. A few practices protect against this in either chat:

  • Keep one thread per component. A settled section makes a clean reference, and a new section starts a new thread.
  • In a long thread, restate the token names and timing values in the revision message, rather than relying on the first message.
  • Ask for the change in one line, then the constraint: "Change X to Y. Keep everything else identical."
  • Ask the model to compare its output with the spec line by line and list anything it did not implement. A short list is faster to check than the whole file.
  • Keep the spec in a file inside your project and paste from that file. If you change tools, the spec survives and the chat does not.
  • Check the output the same way

    Use the same checks for either model, because the checks test the spec rather than the model:

  • Does the code compile, and do the imports exist in your project?
  • Are the token names used, rather than replaced with values that look better?
  • Do the timings match exactly, including the easing?
  • With reduced motion on, does the finished layout appear?
  • Has anything appeared that the spec did not ask for, such as a section, extra copy or a new colour?
  • A failed check tells you which line of the spec to tighten. Tighten the spec first, then ask again, whichever model produced the output.

    Pick the model by how you work

    This guide cannot tell you which model is better for your hero, and anyone who claims to from a single test should be read with caution. What it can tell you is where the request matters. Choose the model you can iterate with comfortably, keep the spec in a file and judge both outputs by the same checks.

    If the output keeps drifting from the spec, tighten the spec before you switch models. Check first whether the detail is missing from the request.

    For Claude-specific phrasing, read how to write Claude prompts for web design. For the tool side of the same question, read prompts for AI website builders. To see how a full spec is laid out, browse the SaaS prompts or open the Velocity sportswear spec.

    FAQ

    Is Claude or ChatGPT better for web design prompts?

    This guide does not rank them, and HeroPrompts has not compared them. A spec that names every decision can work in either model. Choose the one you iterate with more comfortably, and judge the output with the same checks.

    Should I write a different prompt for each model?

    Keep the spec the same and change its shape. For Claude, use labelled sections and ask for a file list first. For ChatGPT, put the constraints in a numbered list near the top and ask for complete files.

    Do I need exact hex codes and font names in ChatGPT?

    Yes, as with any model. A colour name such as "navy" covers many shades, and "modern sans-serif" leaves the choice of font to the model. Hex values and named weights remove that guess.

    Why does my hero look generic after a few revisions?

    Often the revisions were vague. Each one should name the token or value it changes and say what must stay the same. In a long thread, restate the palette and timings so they are not lost.

    Try it yourself

    Build a starter hero prompt in four questions with the free generator, or copy five prompts from the library with no account.

    Get the next guide by email

    New hero prompts and practical AI design guides like this one, when they go live. No spam, unsubscribe any time.

    By signing up you agree to receive these emails. See our privacy policy.

    Prompts from this article

    SaaS

    Parapet — Modern SaaS Hero

    Light, paper-toned SaaS hero with an odometer headline that rolls plan, write, ship, and a live roadmap panel whose bars draw in with a sweeping today marker. Built for product teams and planning tools.

    E-commerce

    Apex Athletic — Sportswear E-Commerce Hero

    A split-screen sportswear hero where a lime divider sweeps across a black-and-white product image to reveal full colour, while performance stats count up beside it. Built for athletic apparel, performance gear and DTC sports brands.

    Backgrounds

    Merrow — Drifting Gradient Background

    A pure-CSS six-stop gradient that slides across the viewport on a seamless 18-second loop, with film grain and a vignette. For hero backgrounds, card overlays and section dividers that need atmosphere without a JavaScript loop.

    From HeroPrompts

    The prompts in the HeroPrompts library are engineered at the level of detail described above — every font, colour, interaction, and animation specified. Skip the iteration and ship a hero section that looks like it cost money.

    ClaudeChatGPTprompt engineeringweb designAI toolshero sections