Landing page prompts for AI app builders: v0, Lovable, Bolt, and Replit Agent

"Make it modern and clean" is the most common landing page prompt ever pasted into an AI app builder, and it produces the most common-looking landing pages on the internet. The tools are not the problem. v0, Lovable, Bolt, and Replit Agent will all follow real design direction — border weights, type scale, spacing rhythm, section order — the moment a prompt actually supplies it.

That is what every prompt below does. Each one specifies the section anatomy, the content skeleton, concrete spacing, responsive behavior, and an acceptance check the tool can verify its own output against. The parts that should vary — visual style, color direction, type pairing, motion level — are dropdowns in the customizer on each page, and each dropdown option substitutes a full specification block, not an adjective. Choosing "Neo-brutalist" injects border widths and shadow offsets; choosing "Scroll-driven parallax" injects layer ratios and a reduced-motion fallback.

A note on how to use these: paste the prompt as your first message in a fresh session, not as a correction halfway through. App builders commit to layout decisions early, and steering an existing generation toward a different visual system is much harder than starting from a complete spec.

v0 landing page prompts

v0 responds best to prompts that treat the page as a set of components. These prompts split the page per section so you can regenerate the hero without touching the footer.

v0 prompt for a portfolio website — This v0 prompt turns a portfolio into six regenerable components, with the work grid's hover states specified down to the outcome-line reveal.
v0 prompt for a waitlist landing page — This v0 prompt builds a waitlist page as five small React components, so the form or hero can be regenerated without redoing the page.
v0 prompt for a SaaS landing page — This prompt makes v0 generate a nine-section SaaS landing page as separate React components, so you can regenerate the hero without losing the pricing section.
v0 prompt for an agency landing page — A v0 prompt for a portfolio-forward agency landing page, built as seven regenerable React components from nav to contact footer.
v0 prompt for an ecommerce landing page — A v0 prompt for a single-product landing page built from seven independent components, from gallery and buy box to a scroll-aware sticky purchase bar.
v0 prompt for a 404 page — A 404 page prompt for v0 that outputs one drop-in not-found component: oversized numeral, wry one-liner, and three recovery paths — button, home link, and search.

Lovable landing page prompts

Lovable builds the page as part of a working app, which makes it the right tool when the landing page has a live job to do — a waitlist form that actually stores signups, an ecommerce page with a real cart.

Lovable prompt for a portfolio website — A Lovable portfolio prompt that treats the contact form as the product: submissions land in a messages table with budget and project type, ready to triage.
Lovable prompt for a waitlist landing page — A Lovable prompt for a pre-launch page that stores signups in a real database table, not a dummy form.
Lovable prompt for a SaaS landing page — A single message that has Lovable build a full SaaS marketing page with a working email-capture form wired to its built-in database.
Lovable prompt for an agency landing page — This Lovable prompt produces an agency landing page with a contact pipeline that actually works: validated form, database-stored submissions, email notification, then deploy.
Lovable prompt for an ecommerce landing page — This Lovable prompt builds a one-product landing page with measurable conversion wiring: buy clicks logged to the database, an email capture that stores addresses, and a deploy at the end.
Lovable prompt for a 404 page — This prompt turns Lovable's 404 into a diagnostic tool: every dead-end hit gets logged to a broken_links table, and a one-field report form flags the worst offenders.

Bolt landing page prompts

Bolt scaffolds a runnable project in the browser, so these prompts lean on file structure and the instant preview loop: generate, look, tighten one section, repeat.

Bolt prompt for a portfolio website — This Bolt prompt builds the portfolio around a data file: six project objects render the work grid, so updating your work never touches markup.
Bolt prompt for a waitlist landing page — This Bolt prompt scaffolds a flat, runnable waitlist project with the form logic isolated in one file, so the localStorage stand-in can be swapped for a backend later.
Bolt prompt for a SaaS landing page — Paste this into Bolt and it scaffolds a Vite + React landing page with every string extracted into one content file, so copy edits never touch markup.
Bolt prompt for an agency landing page — A Bolt prompt that scaffolds an agency site as a runnable Vite project, manifesto-first instead of hero-first, with one file per section rendering live in the preview.
Bolt prompt for an ecommerce landing page — A Bolt prompt that scaffolds a product landing page where all copy lives in one data file — change the price once and both buy points update.
Bolt prompt for a 404 page — A single-viewport 404 for Bolt with a fake command line that types "searching for page...

Replit Agent landing page prompts

Replit Agent plans before it builds. These prompts are written so the plan it proposes is already the page you want — section list, copy skeleton, and checks included — and hosting is one click after.

Replit Agent prompt for a portfolio website — A Replit Agent portfolio prompt built for the plan-first workflow: the section map and file layout get approved before any code is written.
Replit Agent prompt for a waitlist landing page — A Replit Agent prompt that forces a plan — route, storage, sections — before any waitlist code gets written.
Replit Agent prompt for a SaaS landing page — This prompt makes Replit Agent propose a section plan for your approval before building, then deploy the finished SaaS page to a live URL.
Replit Agent prompt for an agency landing page — This prompt has Replit Agent plan an agency landing page before building it, then host the result on a public URL.
Replit Agent prompt for an ecommerce landing page — This prompt makes Replit Agent plan a single-product landing page, build it, and host it — with an objection row answering buyer hesitations before the benefit sections.
Replit Agent prompt for a 404 page — This prompt makes Replit Agent pitch three 404 headline directions before building, so you choose the voice instead of accepting a first draft.

Pages versus sections

The full-page prompts above ship a complete landing page in one paste. The section prompts (hero, pricing, bento grid, testimonial wall, footer, and the rest) exist because the second week of a landing page's life is section-by-section: the page converts, but the pricing section is weak, or the hero needs a rebuild for a new positioning. Running a section prompt inside an existing project is faster and safer than regenerating the page — and every section prompt states how to slot into surrounding markup without breaking it.

If you use a different tool, the same prompts exist for Cursor and Claude Code as part of each tool's prompt directory, and every page above links to its equivalents across tools.