How to Prompt Any AI Builder for a Landing Page That Doesn't Look AI-Generated (Full Walkthrough)
Short answer: write the prompt as a design brief in five blocks: Identity, Structure, Content rules, Motion, Never. Put the restraint rules last, because the last constraints get followed most reliably. The same prompt t
Short answer: write the prompt as a design brief in five blocks: Identity, Structure, Content rules, Motion, Never. Put the restraint rules last, because the last constraints get followed most reliably. The same prompt then works in v0, Lovable, Bolt, Cursor, Windsurf, ChatGPT, Claude, Gemini, Replit or GitHub Copilot. Below is a complete example prompt you can copy, a line-by-line explanation, and how to paste it into each tool.
Why does the AI keep giving me the same landing page?
A model writing a landing page has thousands of open decisions: font, weights, spacing, accent colour, section order, hero layout, motion. Each one you leave open defaults to the statistical middle. That's why so many AI landing pages share the same centred hero, gradient headline and three icon cards.
You don't need a better model. You need to close the decisions.
What should a landing page prompt include?
| Block | What it fixes | Example line |
|---|---|---|
| Identity | colour, type, radius, borders | background #0A0A0B, one accent #FF5A1F, Inter 400/600 only |
| Structure | section order and layout | (1) Nav Γ’β¬Β¦ (2) Hero Γ’β¬Β¦ (3) Logos Γ’β¬Β¦ |
| Content rules | copy length and honesty | headline max 8 words; no invented testimonials |
| Motion | what moves and how | fade-up 16px, 500ms, stagger 60ms, respect reduced-motion |
| Never | the generic defaults | no gradient text, no emoji in headings, no carousel |
The full example prompt (copy it)
Here's a brief for a fictional developer tool called Tracebit:
Build a single-page landing page for "Tracebit", a log search tool for backend developers.
Stack: React + Tailwind CSS, one file, responsive down to 360px.
IDENTITY
- Background #0A0A0B, text near-white at 92%, secondary text at 60%.
- One accent only: #FF5A1F. Used for the primary CTA, one highlight per section, focus rings.
- Font: Inter, weights 400 and 600 only. Monospace: JetBrains Mono for code.
- Radius 12px. Borders: 1px white at 8% opacity.
STRUCTURE
(1) Nav: wordmark left; 3 links + accent "Start free" button right; sticky; adds backdrop blur and bottom border after 24px scroll.
(2) Hero: left-aligned. Headline clamp(2.75rem, 6vw, 4.75rem), tracking -0.03em, max 8 words.
Subline max-width 34rem at 60% opacity. Primary CTA + ghost secondary CTA.
Right side: a terminal window showing 6 lines of a log query with one matched line highlighted in the accent.
(3) Logo row: 6 grey placeholder wordmarks at 40% opacity.
(4) Features: 3 rows alternating text/visual sides. Each visual is a bordered panel with a faint 24px grid background.
(5) One large testimonial quote in display type, with a placeholder name clearly marked [CUSTOMER NAME].
(6) Pricing: 3 tiers, middle tier elevated with accent border and "Most popular" tag.
(7) FAQ: accordion, one item open at a time, 5 questions.
(8) Final CTA band, then a minimal 2-row footer.
CONTENT RULES
- Use the placeholder copy in [BRACKETS] where real content is needed. Do not invent customer names, logos, numbers or reviews.
MOTION
- Sections fade up 16px over 500ms on first entry into view; children stagger 60ms.
- Cards lift 3px on hover. Respect prefers-reduced-motion (no movement).
NEVER
- No gradient text. No emoji in headings. No three-icon feature row. No stock illustrations.
- No carousel. No more than one accent colour. No centred hero.
Why does each line matter?
- "One accent only" and "weights 400 and 600 only." These are restraint rules. Left free, generators add a new colour and weight per section, and that's what reads as amateur.
- "Max 8 words" on the headline. It forces real display-type hierarchy. Long headlines quietly shrink the hero.
- A focal object in the hero (the terminal). Heroes fail from emptiness more often than from clutter.
- "Do not invent customer namesΓ’β¬Β¦" AI builders pad pages with fake social proof unless you say otherwise. Publishing that is a real liability.
- NEVER block last. Trailing constraints tend to get the highest obedience, so the anti-generic rules go at the end.
How do I use this prompt in each AI tool?
| Tool | Where to paste | Tip |
|---|---|---|
| v0 | New chat | Ask for "one file, no extra libraries" to keep it portable |
| Lovable | First message of a new project | Keep design and features in separate messages |
| Bolt.new | Main prompt box | Ask it to put colours in the Tailwind theme first |
| Cursor / Windsurf | Agent chat with your repo open | Name the target file, e.g. app/(marketing)/page.tsx
|
| Claude / Claude Code | Chat (Artifacts preview) or terminal agent | Ask for a single React component first, then split it up |
| ChatGPT | Chat, then open in Canvas | Iterate on copy in Canvas without regenerating the layout |
| Gemini / Google AI Studio | Chat or Build mode | Build mode gives you a live preview and a shareable link |
| Replit | Replit Agent | It can host the result immediately |
| GitHub Copilot | Copilot Chat / agent mode in VS Code | Paste into a new branch so you can diff the result |
How do I iterate without breaking the design?
- Swap content, not structure. Replace the [BRACKETS] with real copy first.
- Change one decision per message. "Make the accent #3B82F6" is safe. "Make it more modern" undoes your brief.
- Check 360px width, keyboard focus and dependencies before you accept it.
Where can I get more prompts like this?
Writing a brief like this takes 30Γ’β¬β60 minutes once you know the pattern, and much longer the first few times. If you'd rather start from a tested one, VibUI has 2,800+ website prompt templates written in this style: 775 full pages, 1,100 sections, 817 UI prompts and 160 animated backgrounds, each with a live preview. About 1,000 also ship with finished source code.
- It's plain text, so it works in every tool in the table above
- One-time payment, no subscription: $48 (90 days), $99 (1 year, includes source code), $179 (lifetime, listed down from $384)
- 60 free samples you can browse without an account at vibui.dev/free, and a free account can copy 2
FAQ
Does this work with ChatGPT and Claude, or only v0? All of them. The prompt is plain text. Any tool that writes front-end code from a prompt can use it.
Should I specify the framework? Yes, if you have one. Otherwise say "React + Tailwind, one file" for portability, or "plain HTML + CSS" for ChatGPT or Claude previews.
Why not just use a component library? Components give you parts. The brief gives the AI the layout, type, colour and motion decisions that make the parts look designed. They work well together.
How long should a landing page prompt be? Usually 250Γ’β¬β500 words. Length isn't the goal. Closing open decisions is.
Disclosure: written by the VibUI team. The Tracebit prompt above is an original example written for this tutorial.
Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.