---
title: Write Effective Requests
description: Give Runner a clear goal, useful context, and practical boundaries.
---

**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:

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

<Prompt description="For example:" actions={["copy"]}>
  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.
</Prompt>

## Send a well-scoped request

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

## Use Enhance prompt when available

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

## 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**.

## Related guides

- [Chat with Runner](./chat-with-runner.mdx)
- [Images, models, and skills](./attachments-profiles-and-skills.mdx)
- [When Runner asks a question](./answer-runner-questions.mdx)
- [Task states and details](./task-states-and-details.mdx)