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. Server-side validation, duplicate detection, and a live signup count are in the spec, so the hosted URL is shareable the same day. The customizer supplies the look: style, palette, typography, and motion slot in as spec blocks.
Last updated
Plan first, then build a pre-launch waitlist page for {{product}}, aimed at {{audience}}, hosted on Replit at a public URL I can share today. The plan should list the single route, the storage choice for emails (Replit DB or SQLite — say which and why), and the section map below. Show me the plan before writing any code.
Section map:
1. Hero: a headline naming the outcome, a one-sentence subhead saying what early members get that late signups don't, and the email form directly below it.
2. Three teasers: an "Inside at launch" list of three bullets; a short founder paragraph on why {{product}} exists; a momentum line pulled live from the stored signup count.
3. Full signup block: the form with server-side validation on POST, duplicate detection, and a success view showing position in line (the count at insert time) plus a personal referral URL.
4. FAQ, four items: launch date, launch pricing, unsubscribe policy, how referrals reorder the queue.
5. Minimal footer with a contact address.
Visual direction:
{{style}}
Palette: {{palette}}
Typography: {{type}}
Motion: {{motion}}
Rules:
- One spacing scale for the whole page: 96px section padding on desktop, 56px on mobile — no per-section values.
- Under 700px the teaser row stacks, and the success view replaces the form in place without a scroll jump.
- The primary call to action is "{{cta}}" — that exact text on every submit button.
After the build, verify on the live URL before reporting done: a valid POST returns the success view with a numeric position; the same email twice gets a friendly duplicate notice; the page loads over HTTPS; and swapping the form for the success card causes no visible layout shift. Fix failures in a follow-up pass, then hand back the URL.Customize it
Runs in your browser. Nothing you type here is sent anywhere.
Plan first, then build a pre-launch waitlist page for a project management SaaS, aimed at engineering managers at startups, hosted on Replit at a public URL I can share today. The plan should list the single route, the storage choice for emails (Replit DB or SQLite — say which and why), and the section map below. Show me the plan before writing any code. Section map: 1. Hero: a headline naming the outcome, a one-sentence subhead saying what early members get that late signups don't, and the email form directly below it. 2. Three teasers: an "Inside at launch" list of three bullets; a short founder paragraph on why a project management SaaS exists; a momentum line pulled live from the stored signup count. 3. Full signup block: the form with server-side validation on POST, duplicate detection, and a success view showing position in line (the count at insert time) plus a personal referral URL. 4. FAQ, four items: launch date, launch pricing, unsubscribe policy, how referrals reorder the queue. 5. Minimal footer with a contact address. Visual direction: Minimal dark style. Near-black canvas (#0A0A0B) with one elevated surface tone (#141416) for cards — never more than two surface steps. Hairline borders (1px, white at 8% opacity) instead of shadows; if a shadow is unavoidable use 0 1px 2px rgba(0,0,0,0.4) and nothing softer. Text in exactly three steps: white at 92% for headings, 60% for body, 40% for captions. Generous negative space — section padding at least 120px on desktop, 64px on mobile. The accent color appears only on interactive elements and one hero highlight, nowhere else. Palette: a strict neutral ramp (white, #F5F5F5, #E5E5E5, #737373, #171717) carries the entire interface; pick one accent and use it only for primary CTAs, active states, and a single hero highlight. If the accent appears more than five times per viewport it stops being an accent. Keep semantic colors (success, error) desaturated so the accent stays in charge. Typography: one geometric sans (a Futura/Poppins-class face) at three weights maximum (400/500/700). Scale: 64-88px hero, 32px section heads, 18px lede, 16px body, 13px caps labels with 0.08em tracking. Tight headline leading (1.05-1.1), relaxed body (1.6). Let the geometry carry the personality — no italics; weight and size do all hierarchy. Motion: none. Zero scroll animations, zero entrance effects — the page is fully composed the instant it paints. Spend the motion budget on input feedback instead: 120-150ms ease-out color and transform transitions on hover and press states only. Hold this constraint absolutely; it is a statement, not an omission. Rules: - One spacing scale for the whole page: 96px section padding on desktop, 56px on mobile — no per-section values. - Under 700px the teaser row stacks, and the success view replaces the form in place without a scroll jump. - The primary call to action is "start a free trial" — that exact text on every submit button. After the build, verify on the live URL before reporting done: a valid POST returns the success view with a numeric position; the same email twice gets a friendly duplicate notice; the page loads over HTTPS; and swapping the form for the success card causes no visible layout shift. Fix failures in a follow-up pass, then hand back the URL.
Same task in other tools
Questions about this prompt
The Agent skipped the plan and went straight to code — how do I get it back on track?
Stop the run and restate the gate: "Show me the plan first — route, storage choice, section list — and wait for my approval." Replit Agent respects an explicit gate when it's the most recent instruction. The plan review is where a wrong storage pick gets caught cheaply.
Replit DB or SQLite for the emails?
Either satisfies the prompt. Replit DB is zero-setup key-value storage, fine for an email list and a count; SQLite gives you real queries and a painless CSV export when you move the list into a mailing tool. If migration is on your roadmap, pick SQLite.
How do I put this on my own domain instead of the replit.app URL?
Deploy it (Autoscale or Static depending on how the Agent built it), then add a custom domain in the deployment settings and point a CNAME at it. Run the prompt's verification list after the domain switch too — it behaves identically on either URL.
Part of the Replit Agent landing-page cluster — start from the main Replit Agent landing page prompt.