Write Effective Requests

What this covers: You will write requests that are easier for Runner to act on and easier for you to review.

A useful request describes the result, not just the topic. Give enough context to make the next decision clear, then use follow-up messages for focused refinements.

Entry path: Open a store project → open a conversation → message box.

Before you start

Confirm the store and page or workflow you want to change.
Decide one visible outcome and any boundary Runner must preserve.
Remove passwords, secrets, payment details, and unnecessary customer data.

Composer controls and results

Control	What happens after you select it
More actions	Opens less frequently used composer tools when they do not fit in the toolbar.
Enhance prompt	Generates a refined draft; it does not send the request or change the store.
Accept	Replaces the composer draft with the displayed refinement.
Dismiss	Closes the refinement and keeps the existing draft.
Regenerate	Requests another refined version.
Revert to original	Restores the earlier wording after an accepted refinement.
Send	Adds the final draft to the conversation and starts the task.

A simple request structure

Include these five parts when they matter:

Goal: What should be different when the work is done?
Store context: What do you sell, and who is the customer?
Current issue: What is confusing, missing, or underperforming now?
Desired result: What should a customer be able to see or do?
Boundaries: What must stay unchanged, and what should Runner verify?

For example:

Update the homepage hero for our minimalist travel-bag store. Make the carry-on collection the main focus, keep the existing navigation and product data, and make the primary action lead to that collection. Check the result on mobile and desktop before you finish.

Send a well-scoped request

Start with one coherent outcome.
Name the page, section, product, or workflow involved.
Describe the customer action you want to improve.
Add a reference image when appearance or existing content matters.
State anything Runner must not change.
Ask for the checks you care about, such as mobile layout or a specific click path.
Select Send.
Review the result, then send one focused correction at a time.

Use Enhance prompt when available

Draft the request in the message box.
Open More actions if Enhance prompt is not visible.
Select Enhance prompt.
Wait while the control shows Enhancing….
Review the Refined prompt.
Choose Accept to use it, Dismiss to keep your draft, or Regenerate for another version.
Use Revert to original if you accepted the refinement and want your earlier wording back.
Select Send only after the request still matches your intent.

Avoid ambiguous requests

Instead of	Try
“Make it better.”	“Make the collection cards easier to scan on mobile, while keeping their current product links.”
“Fix checkout.”	“Trace the Add to cart → Cart → Checkout path and tell me where it stops before changing anything.”
“Copy this site.”	“Use this reference for spacing and tone, but keep our own branding, products, and navigation.”
A long list of unrelated changes	Start one chat for the main outcome, then create another for separate work.

Recovery when the result misses the goal

Point to the exact part that is wrong.
Describe the expected click result or visible state.
Add a clearer reference image if the earlier one was unclear.
Answer Runner's questions rather than repeating the full request.
For a failed task, read Details before choosing Try again.

Write Effective Requests

On This Page