# Iterating in chat

> Small, specific messages get better results than long wish lists.

Once the first version exists, you will spend most of your time refining it. The rhythm is the same every time: look, describe one thing, review the result.

## Change one thing at a time

Each message should have a single goal. That makes the result easy to judge and easy to undo. If a change comes back wrong, you know exactly what caused it.

## Point at what you mean

The builder can see your project, so refer to it the way you would to a colleague:

- "The 'Add client' button in the top right should be blue, not grey."
- "On the member detail page, put the notes above the booking history."
- "The table cuts off the last column on a narrow screen."

Names on screen are the best anchors. If there are two buttons called "Save", say which screen you mean.

## Paste a screenshot for anything visual

For layout problems and odd rendering, a screenshot removes ambiguity. Add a sentence about what is wrong, such as "the price column is hidden behind the sidebar on tablets".

## Use plain corrections

- "Undo that."
- "Keep the new layout but put the filters back."
- "That is too tall, make the header half the height."
- "Same treatment for the invoices table."

Short follow-ups are normal. Five small messages usually beat one perfect paragraph.

## When to start a fresh conversation

Long chats stay usable, but a new conversation is a clean slate for a new area of work. Start fresh when you move from, say, the booking flow to admin reporting, and mention the context in your first line.

## Reviewing the result

After each change, the builder summarises what it did. Read that summary: it often mentions something it decided on your behalf, such as "kept old bookings visible to staff only". If you disagree, say so right away.

Next: [Editing files directly](/build/editing-files).