Write useful prompts
Give the builder clear context, specific changes, and a way to check the result.
A
JA useful prompt tells the builder what to change, where to change it, and what a good result looks like. Give it the audience and constraints that a designer would need, then refine the work in small, reviewable steps.
Before you begin
Open the relevant task and page in Website builder. Decide whether your request applies to one element, one page, or the whole site. Gather the exact copy, links, or brand assets the change needs.
Make a focused request
- Name the page or select the element in the preview.
- Describe the change in concrete terms. Include exact wording or values when you have them.
- State any important constraints, such as keeping the existing search behavior or applying a change to every job card.
- Send the request, review the result, and give the next piece of feedback.
Examples
| Instead of | Try |
|---|---|
| Make it more professional | Use our navy and white palette, reduce the hero height, and make job titles the strongest text in each card. |
| Fix mobile | On the mobile jobs page, the location overlaps the company name. Stack them below the title and keep the Apply button visible. |
| Add something for employers | Add a For employers page explaining who our audience is, with a Post a job button linked to the existing posting flow. Add it to the header. |
| Change the header | Replace the homepage heading with “Careers in civil engineering.” Keep its current size, spacing, and position. |
For a larger request, explain the visitor's journey: “A member arrives, searches by location, opens a job, and follows the application link.” This gives the builder a behavior to preserve as it changes the design.
Use references and attachments
Use the attachment control to add reference files, or drag a file into the composer. You can paste a screenshot from your clipboard. Wait for uploads to finish before sending, and say how each file should be used.
For example: “Use the attached logo in the header. Use the screenshot only as a spacing reference; keep our existing colors and content.” If an attachment fails or its format is not accepted, follow the upload message and retry with a supported file. You can also describe the relevant details in the prompt.
Follow up while work is running
A follow-up can wait for the current change to finish. Use Steer when you want a pending instruction incorporated into the current build. Use Stop if you need to halt the work; inspect the saved progress before continuing because stopping can leave a partial change.
Check the result
Compare the changed page with your request at desktop and mobile widths. Test the affected action, not just the appearance. For a navigation change, follow the link; for a job card change, open a real job.
Troubleshooting
If the result is too broad, narrow the next request to a specific page or element. If the builder repeats an unwanted approach, describe the visible problem and the required outcome. Use versions to return to an earlier direction instead of repeatedly repairing one you no longer want.
Next steps
Use element selection and theme controls for targeted changes, or share the draft for feedback.