Landing Page Prompts for Lovable AI

# Context
Build a single-purpose landing page: capture an email address before a product launches. The visitor arrives from one known traffic source, so the page carries one offer and one action, and nothing that competes with them.

## Core Features (Priority Order)
1. Hero: the offer in one sentence, the form visible without scrolling
2. Email capture writing to Supabase with UTM parameters stor

# Context
Build a landing page for a dated event: a countdown to one canonical moment, email capture for reminders, and a defined transformation of the page when the countdown reaches zero.

## Core Features (Priority Order)
1. Countdown from a single UTC timestamp, rendered in the visitor's local time zone with the zone named
2. Email capture: 'remind me', storing the address with UTM parameters

# Context
An existing landing page converts at a known baseline. Build variant testing: serve visitors one of two versions differing in exactly one element, keep the assignment stable per visitor, and measure conversion per variant from the first impression.

## Core Features (Priority Order)
1. Variant definition: one changed block (hero promise, CTA wording, or proof section), everything else sh

# Context
Add first-party analytics to a landing page: enough to know traffic, source, device, conversion and drop-off, collected by your own endpoint, readable on one internal dashboard. No external analytics script.

## Core Features (Priority Order)
1. Pageview capture: path, referrer, UTM parameters, device class, timestamp
2. Conversion event tied to the page's one goal (form submit)
3. A dai

# Context
A generated site has public pages that should rank. Build the indexability layer: sitemap.xml, per-page canonicals and titles, robots.txt, and basic structured data, all derived from the route list so nothing can drift.

## Core Features (Priority Order)
1. One route registry: path, title, description, indexable flag, content date
2. sitemap.xml generated from the registry, indexable rou

# Context
Build a press and media page: everything a journalist needs to write about the company accurately without waiting for a reply. Facts, quotes, assets, contact, all current and all downloadable.

## Core Features (Priority Order)
1. Fact block: what the product is in one sentence, founded date, founder names, location, one-line traction statement with its as-of date
2. Approved quotes: two

# Context
Build a landing page targeting one search query. The searcher's intent defines the structure; the page answers it thoroughly enough to deserve the ranking, then converts attention it has earned. Server-rendered throughout.

## Core Features (Priority Order)
1. An H1 and title matched to the query's actual intent, not just its words
2. The direct answer within the first 150 words, before 

# Context
Build a gated download page for one asset (guide, checklist, template pack): the visitor sees what they get, trades an email, receives it instantly, and knows exactly what follows. The gate is a fair trade, not a trap.

## Core Features (Priority Order)
1. Asset preview: table of contents or sample pages, page count, format, last-updated date
2. Capture form: email only, with a disclosur

# Context
Build a pricing page for two or three plans: what each costs, what genuinely differs, which one fits whom, and answers to the questions that stall purchases. Every number on it must match what the product enforces.

## Core Features (Priority Order)
1. Plan cards: price, billing unit, the three differences that matter, one CTA each
2. A recommendation with a reason ('most solo builders s

# Context
Build a social-proof page assembling verifiable customer evidence: quotes, results and logos, each with provenance. This page's entire value is credibility, so its design constraint is verifiability, not volume.

## Core Features (Priority Order)
1. Featured quotes: full name, role, company, photo where permitted, each with permission on record
2. Result statements with context: what cha

# Context
Build a waitlist page for a pre-launch product: explain what is coming and when, capture emails with source attribution, confirm honestly, and keep the list unreadable from the client. Clarity converts here; vagueness reads as vapor.

## Core Features (Priority Order)
1. Hero: what the product is in one concrete sentence, and the expected launch window
2. What joining gets you: early acc