BoilerPrompt
Replit Agent

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. Each case tile requires a measurable outcome line, and the acceptance pass runs on the hosted URL, not localhost. Style, palette, typography, and motion come in from the customizer's spec blocks.

Last updated

Prompt
Start with a plan, then build and host a portfolio site for {{product}} on Replit. The plan should name the stack (static files are fine — justify anything heavier), the file layout, and the section map below; show it to me before writing code, and expect per-section follow-ups afterwards.

Section map:
1. Hero — an identity statement in two lines: who this is, then the one sentence that tells {{audience}} why they're the right hire. No buzzword adjectives; name the craft plainly.
2. Selected work — four case tiles in a 2x2 arrangement, each with an image, project name, and a measurable outcome line; on hover the tile darkens while the outcome line brightens; each tile links to a placeholder anchor for now.
3. About — a horizontal strip pairing a portrait placeholder with a bio of exactly three sentences: background, philosophy, availability.
4. Services — one row of four offerings, each with its deliverable spelled out in a sub-line; below it, a plain comma-separated tool list.
5. Contact — a big closing invitation line, the email address printed in full rather than hidden behind an icon, and two profile links.

Visual direction:
{{style}}

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

Layout rules:
- One spacing scale: 8, 16, 32, 64, 96px. Sections take the 96 step on desktop and 64 on mobile; invent no other values.
- Under 720px the 2x2 tiles stack single-column in the same order and the hero text left-aligns.

The primary call to action is "{{cta}}"; render it as the Contact mailto button label and in the nav if you add one.

Before calling it done, verify on the hosted URL: all four tiles keep correct image aspect ratios; the hover treatment doesn't stick on touch — outcome lines show by default on mobile; the mailto link carries a prefilled subject; and every section scrolls into view from a nav or hero link. Report the URL plus anything you'd fix next.

Customize it

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

Your customized prompt
Start with a plan, then build and host a portfolio site for a project management SaaS on Replit. The plan should name the stack (static files are fine — justify anything heavier), the file layout, and the section map below; show it to me before writing code, and expect per-section follow-ups afterwards.

Section map:
1. Hero — an identity statement in two lines: who this is, then the one sentence that tells engineering managers at startups why they're the right hire. No buzzword adjectives; name the craft plainly.
2. Selected work — four case tiles in a 2x2 arrangement, each with an image, project name, and a measurable outcome line; on hover the tile darkens while the outcome line brightens; each tile links to a placeholder anchor for now.
3. About — a horizontal strip pairing a portrait placeholder with a bio of exactly three sentences: background, philosophy, availability.
4. Services — one row of four offerings, each with its deliverable spelled out in a sub-line; below it, a plain comma-separated tool list.
5. Contact — a big closing invitation line, the email address printed in full rather than hidden behind an icon, and two profile links.

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:
- One spacing scale: 8, 16, 32, 64, 96px. Sections take the 96 step on desktop and 64 on mobile; invent no other values.
- Under 720px the 2x2 tiles stack single-column in the same order and the hero text left-aligns.

The primary call to action is "start a free trial"; render it as the Contact mailto button label and in the nav if you add one.

Before calling it done, verify on the hosted URL: all four tiles keep correct image aspect ratios; the hover treatment doesn't stick on touch — outcome lines show by default on mobile; the mailto link carries a prefilled subject; and every section scrolls into view from a nav or hero link. Report the URL plus anything you'd fix next.

Same task in other tools

Questions about this prompt

What should I actually push back on at the plan step?

Two things: the stack (static is right for a portfolio unless a case-study CMS is coming) and the section order. Moving Contact higher or cutting Services is a one-line plan edit; once code exists, the same change costs a whole follow-up cycle.

What's the best shape for the follow-up passes after the first build?

One section per message, phrased as a checkable request: "About strip — cut the bio to three sentences, availability last." Replit Agent handles scoped diffs well and gets muddy on multi-section rewrites; the prompt's numbered section map gives you stable names to reference.

The hover styles fire on my phone and stick after a tap — is that a bug?

It's default touch-browser behavior: :hover states stick after tapping. The acceptance list has you confirm outcome lines are visible by default on mobile; if the Agent missed it, ask for a hover: hover media query wrapped around every hover rule.

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

Related prompts