Skip to main content
The fastest way to learn prompting is to build something. This guide walks you through one campaign, a product launch page, from first prompt to shipped page. Every step has a prompt you can copy, use as-is, or adapt to your own product.

​
Before you begin

You can follow along with any project. Results get noticeably better if you’ve set up your brand in Branding and connected your products through Integrations first: Replo pulls your colors, fonts, product data, and checkout automatically instead of guessing.

​
Step 1: Describe what you want built

Talk to Replo the way you’d brief a designer: what the page is for, who it’s for, and what’s on it. You don’t need special syntax.
Replo will start building and stream its work into the Site Builder so you can watch. For bigger requests it drafts a plan first, so you can review the steps and redirect before it commits.

​
Step 2: Add the context that changes the output

Replo follows what you say literally, so the details you give shape what you get. The three that matter most for a campaign page: where the traffic comes from, what the offer is, and what counts as success.

​
Step 3: Iterate one change at a time

Once you’re reacting to a real page, refine it with small, focused follow-ups. One change per prompt is easier for Replo to get right and easier for you to review.
If the result isn’t what you meant, say what’s wrong and ask again. You don’t need to start over; Replo keeps the rest of the page intact. Anything you want to undo lives in Version History.

​
Step 4: Point at the exact element

When a request is about one specific thing on the page, don’t describe where it is; select it. Turn on select mode (the Select cursor icon on the toolbar at the bottom of the site preview) and click the element. Change color, font, or alignment from the toolbar, or type a request so Replo updates exactly that.
Selecting the element beats writing “the second button in the third section” every time.

​
Step 5: Reference what you already have

Concrete references anchor the result far better than adjectives. Three kinds work especially well:
  • Your products. Type @ and pick a product; Replo pulls in real titles, images, prices, and variants, and wires the page to your checkout.
  • Images and ads. Paste a screenshot of an ad or a page you like, and Replo matches the layout, tone, or palette. Pages that match the ad that sent the visitor convert meaningfully better than generic ones.
  • URLs. Link to a reference site and say what to take from it: the whole layout, one section, or just the vibe.

​
Step 6: Say what not to do

Constraints keep pages focused and stop scope creep. State them as plainly as the asks.

​
Step 7: Ask Replo to sharpen your prompt

Not sure how to brief a new kind of campaign? Have Replo interrogate your prompt before building.
It will come back asking about the offer, the audience, and the traffic source, and you’ll have a stronger brief in one round trip.

​
Step 8: Keep what works

When a page performs, turn its prompt into a reusable asset instead of reconstructing it from memory next quarter.
For briefs you reuse constantly, go one step further and save it as a skill: a named routine Replo can run on demand, like /launch-page with your house style baked in.

​
Pro tips

Be specific about the change, not just the goal. Instead of: “make this page better” Try: “tighten the hero copy to one sentence, make the benefits icon bullets, and move reviews above the fold” Number your steps for multi-part requests. Replo mirrors your structure:
Spell out copy and placement when it matters. “Add an email capture somewhere” leaves Replo guessing on three things; “email field under the hero, button text ‘Get 15% Off’” leaves it guessing on none. Let Replo explore first. Before a redesign, ask “what would you improve on this page and why?” and pick from its answers.

​
What’s next

Prompt Library

Ready-to-run prompts for launches, sales, listicles, and more.

Prompting Principles

The three habits behind every good prompt.

Prompting Replo

Replo-specific moves: reference images, URL rebuilds, and recovering from mistakes.