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

Hero Section Prompt: Same Brief, Three Levels Compared

Same brief, three prompt levels. See which details change an AI-built hero, with real spec excerpts and a checklist for a hero prompt that names its moment.

A hero section prompt produces a specific result only when it removes the decisions the model would otherwise make for you: the palette, the typefaces, the one motion the hero is built around, and what happens on mobile. Below, the same sportswear brief is written at three levels of detail. The third level is the Apex Athletic spec from our library, and every excerpt in the final section is taken from its file.

These prompts are written to show what each level leaves open. We haven't scored the outputs against a rubric, so read the comparison as a way to judge prompts, not as a benchmark.

The brief

Every level starts from the same request: a hero for a premium sportswear brand called Apex Athletic, with a product image and performance stats. It's the brief most people start with.

Level 1: the brief as the prompt

> Build a sportswear e-commerce hero section with a product image and some stats.

The model has to decide the colours, the type, the layout, the motion and whether the stats are counters, charts or plain text. With nothing else specified, you get the most common choices for that kind of request. The likely result is competent and interchangeable. Nothing in it tells a visitor which brand this is.

Level 2: add a palette and fonts

> Modern sportswear hero with a lime accent, Barlow Condensed headlines, Inter body text, a dark background and subtle animations on load.

This is a real improvement. The brand now has a colour and a type voice. Two parts are still open, though:

  • "Lime" covers a wide range of greens and yellows. Without a hex value, the model picks one.
  • "Subtle animations" has no duration, easing or trigger. The likely result is a fade-up on the headline, the motion that most heroes already use.
  • Level 2 gets the look right and still leaves the hero without a moment anyone will remember.

    Level 3: specify the moment, the numbers and the fallback

    The Apex spec states its signature mechanic in one sentence:

    > The signature mechanic is a split-screen product reveal: the left 60% of the hero shows a still black-and-white product image, and 600ms after load a lime divider sweeps left-to-right across it, unveiling the full-colour version of the same image beneath.

    The rest of the spec turns each adjective into a value:

  • Palette: apex-black #0A0A09, apex-lime #C8FF00, apex-gray #5A5955, defined as tokens in tailwind.config.js.
  • Reveal: the colour layer is clipped back over 1200ms on the easing curve cubic-bezier(0.76, 0, 0.24, 1).
  • Choreography: the copy fades up at 0, 100, 220, 340 and 440ms. The reveal runs from 600ms to 1800ms. The four stat counters start at 500ms and finish at 2000ms.
  • Mobile: below 768px the reveal doesn't run on a timer. It starts once, when the image panel first reaches 40% visibility.
  • Reduced motion: "skip the animation, c = 0 immediately."
  • The spec also settles things most briefs never mention. There is no photograph. The product is an original, unbranded trainer drawn as inline SVG, so there are no third-party logos or trademarked shapes to clear. It also says what must stay out: "Do not add any text, badges or logos to the shoe."

    Apex Athletic — Sportswear E-Commerce Hero — live preview
    Apex Athletic — Sportswear E-Commerce Hero — Split-screen hero: a black-and-white trainer illustration with a lime divider sweeping left to right to reveal colour, Barlow Condensed headline and stat counters ticking up on the right.

    What each level changes

    Going from Level 1 to Level 2 changes the look: palette, type and mood.

    Going from Level 2 to Level 3 changes the decisions: which element moves, when, for how long, what triggers it, and what replaces it on mobile and for visitors who prefer reduced motion. That second step is what separates a hero that was styled from one that was designed.

    A checklist for your own hero prompt

  • Name the moment. Write one sentence that starts "The signature mechanic is...". If you can't, the hero doesn't have a point of view yet.
  • Turn adjectives into numbers. "Smooth" becomes an easing curve, "fast" becomes milliseconds, "lime" becomes a hex code.
  • Put a clock on the sequence. State when each element starts, measured from load.
  • Specify the mobile version. Say what stacks, what reveals and what triggers it.
  • Write the fallback. Say what a visitor with reduced motion sees.
  • Say what must not appear. Negative constraints stop the model adding decoration you didn't ask for.
  • Check the output against the spec

    Once the code runs, test it against the prompt rather than against your taste. Four checks catch most drift:

  • Timing. Reload the page and watch the first two seconds. The counters should start at about 500ms and the reveal at about 600ms, so the two overlap.
  • Colour. Open tailwind.config.js and confirm the hex values match the spec, not the nearest colour the model used.
  • Mobile. Set the viewport to 375px wide. The image should sit above the copy, and the reveal should wait until it scrolls into view.
  • Reduced motion. Turn on reduced motion in your operating system settings and reload. Every counter should show its final value, and the reveal should be skipped.
  • If a check fails, quote the failing line back to the model. "The counters start at 500ms, not on load" gets a fix far faster than "the animation feels off".

    Where detail stops helping

    More detail is not automatically better. Apex's spec is long because the reveal, the counters and the stacking behaviour all have to be exact. A static content section doesn't need that. For a simple section, a shorter prompt with exact hex values and one type scale is usually enough.

    Use the detail where the model would otherwise guess. Each line should answer a question the model would get wrong without it. The same structure works for quieter or busier heroes: Luminary's scrambled headline and Flux's live converter card are specified the same way, with different mechanics.

    For the full structure behind these prompts, read our six-part prompt framework for web design. For Claude-specific phrasing, see how to write Claude prompts for web design. If you want more e-commerce examples, browse E-commerce prompts.

    FAQ

    Does a more detailed prompt always produce a better hero?

    No. Detail helps when it fills a decision the model would otherwise guess. Repeating the same idea in longer words, or specifying things the layout doesn't need, adds noise.

    What is the most useful addition to a hero prompt?

    A named signature mechanic with a duration. Colours and fonts are easy to change later. The mechanic is what the hero is built around, and it's the part generic prompts most often leave out.

    Do I need to give exact hex codes?

    Yes. A hex value has one meaning, while a colour name such as "lime" or "navy" can resolve to many shades. Apex's spec defines each colour as a Tailwind token, so the designer can change one value later without touching the components.

    Can I use a Level 3 prompt for a brand that isn't in sportswear?

    Yes, but replace the mechanic and keep the structure. Keep the palette tokens, the timing values, the mobile rule and the reduced-motion fallback, then write a moment that fits your product. Sentinel's security prompt, for example, uses a live threat feed instead of a product reveal, with the same kind of detail throughout. See the Sentinel enterprise security hero.

    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

    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.

    SaaS

    Sentinel — Enterprise Security SaaS Hero

    A dark enterprise hero whose live security-operations dashboard prepends a new blocked threat every three seconds while SOC 2, ISO 27001 and HIPAA rings sweep to their scores. Built for cybersecurity, compliance and B2B platforms selling to IT and security buyers.

    Agency

    Luminary — Creative Studio Hero

    A dark, high-drama creative studio hero where the headline scrambles through random glyphs on load before resolving letter by letter, like decrypting a transmission. Built for brand studios, motion designers and creative agencies.

    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.

    prompt engineeringhero sectionAI promptscomparisonweb design