BoilerPrompt
Replit Agent

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. The section spec favors editorial restraint: an outcome-first headline formula, a definition-list of capabilities, and principles instead of process steps. Swap style, palette, typography, and motion from the customizer above.

Last updated

Prompt
I want Replit Agent to plan, then build, a single-page agency site for {{product}}, speaking to {{audience}}. Show me the plan first — sections, files, stack — before writing any code, and keep it a static frontend with no database.

Build these sections in this order:
1. Header — the studio name plus a one-word descriptor of the specialty; nav links that scroll to each section.
2. Hero — headline formula: outcome first, method second ("[the result {{product}} delivers]. Through [the specialty]."); one subline; the primary button.
3. Selected work — one featured project at 70% viewport height with client, brief, and outcome, followed by a 3-up grid of smaller cards (title, sector, metric).
4. Capabilities — a two-column definition list: service on the left, a 15-word description on the right, 6 rows.
5. Approach — 3 principles, each a short titled paragraph rather than numbered steps; write them from {{product}}'s discipline.
6. Team note — one paragraph on who does the work, signed with 2–4 names and roles; no photo grid.
7. Contact — heading, direct email, and the primary button repeated.

Visual direction:
{{style}}

Palette: {{palette}}
Typography: {{type}}
Motion: {{motion}}

Layout rules:
- Vertical rhythm on a 12px base: sections get 8 steps (96px) of padding on desktop, 5 steps (60px) on mobile.
- On mobile the featured project drops to auto height with text below the media area, and the definition list becomes stacked label-over-text rows.

The primary call to action is "{{cta}}" — the hero button and the Contact button, nowhere else. After building, host the page on Replit and send me the public URL; I will refine it with follow-up messages section by section, so keep each section a separate component.

Verify before finishing: nav links land on the right anchors; the featured project reads correctly at 1440px and at phone width with no sideways scrolling; exactly two "{{cta}}" buttons exist; the hosted URL serves the page.

Customize it

Runs in your browser. Nothing you type here is sent anywhere.

Your customized prompt
I want Replit Agent to plan, then build, a single-page agency site for a project management SaaS, speaking to engineering managers at startups. Show me the plan first — sections, files, stack — before writing any code, and keep it a static frontend with no database.

Build these sections in this order:
1. Header — the studio name plus a one-word descriptor of the specialty; nav links that scroll to each section.
2. Hero — headline formula: outcome first, method second ("[the result a project management SaaS delivers]. Through [the specialty]."); one subline; the primary button.
3. Selected work — one featured project at 70% viewport height with client, brief, and outcome, followed by a 3-up grid of smaller cards (title, sector, metric).
4. Capabilities — a two-column definition list: service on the left, a 15-word description on the right, 6 rows.
5. Approach — 3 principles, each a short titled paragraph rather than numbered steps; write them from a project management SaaS's discipline.
6. Team note — one paragraph on who does the work, signed with 2–4 names and roles; no photo grid.
7. Contact — heading, direct email, and the primary button repeated.

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.

Layout rules:
- Vertical rhythm on a 12px base: sections get 8 steps (96px) of padding on desktop, 5 steps (60px) on mobile.
- On mobile the featured project drops to auto height with text below the media area, and the definition list becomes stacked label-over-text rows.

The primary call to action is "start a free trial" — the hero button and the Contact button, nowhere else. After building, host the page on Replit and send me the public URL; I will refine it with follow-up messages section by section, so keep each section a separate component.

Verify before finishing: nav links land on the right anchors; the featured project reads correctly at 1440px and at phone width with no sideways scrolling; exactly two "start a free trial" buttons exist; the hosted URL serves the page.

Same task in other tools

Questions about this prompt

Why make Replit Agent show a plan before building?

The plan is the cheapest point to catch scope drift — wrong sections, a surprise database, a stack you didn't want. Approving or correcting a bullet list takes seconds; steering the same change after the code exists takes several follow-up rounds.

The outcome-first headline came out vague — how do I steer it?

Send a follow-up with the concrete result filled in: "rewrite the hero headline using this outcome: [your number or transformation]". Keep the outcome-before-method order from the prompt; that ordering is what separates it from every we-are-an-agency opener.

Is Replit hosting enough for a real agency site?

For launch, yes — the build gets a public URL you can put on a proposal today, and Replit supports connecting a custom domain. If you outgrow it, ask the Agent to export the static build and move it to any host.

Part of the Replit Agent landing-page cluster — start from the main Replit Agent landing page prompt.

Related prompts