Contents
Prompting

Changing it

One change at a time beats a list of ten. You see what moved before choosing next.

Look at it, then talk

You do not have to get the first request right. Open what came back, use it like a customer would, and say what bothers you.

The preview is a working app, not a picture. Buttons work and enquiries are really saved.

One at a time

If ten things are wrong, saying them one at a time works better than sending all ten.

You get to see what each change did before choosing the next one. Change everything at once and you cannot tell which part went sideways.

Small edits are cheap

Rewording a line or nudging a colour is 0.5 credits. Adding a feature is 2.75. Rebuilding across several screens is 6.

The class is decided from what you asked for, and the number on the card is the number that leaves your balance.

Click text and colours instead of asking

In the preview you can click a heading and retype it, or change a colour. No credits are used for that.

Splitting the work this way — click the small stuff, ask for the real stuff — makes a balance last a lot longer.

You can always go back

Every change that worked leaves a point you can return to. If a change made things worse, go back to the previous point. Returning does not cost credits.

Which language to write the change in

Changes follow the language the app already speaks, not the language you typed the request in. Asking in English will not quietly rewrite a Korean app into English.

Read next