← Guide / Learn / Improve a generated result
Improve a generated result
Change one thing per iteration, name the specific fault, and keep a log — that loop beats rewriting from scratch every time.
Diagnose before you rewrite
The instinct after a disappointing generation is to rewrite the whole prompt. That destroys the information in the attempt: you no longer know which change helped. Instead, write down one sentence naming the specific fault — *the chorus does not lift*, *the vocal is buried*, *the tempo drags*, *the ending fades* — and change only the field that controls it.
Generation is also stochastic. Before editing at all, run the same prompt two or three more times. A surprising share of 'bad prompts' are just unlucky takes, and regenerating is cheaper than debugging.
Fault to field map
| What is wrong | What to change |
|---|---|
| Flat, no dynamics | Add an energy shape and strip the verses |
| Chorus does not lift | Shorten the chorus lyric; add register or density change |
| Vocal buried | Remove one lift mechanism; add 'dry vocal up front' |
| Muddy mix | Name a dry anchor; cut reverb on bass and kick |
| Wrong genre feel | Move genre words earlier; delete competing genre |
| Abrupt or fading ending | Name the outro explicitly |
| Too generic | Delete quality words; add two specific technique cues |
The iteration loop
- Regenerate unchanged two or three times first.
- Name one fault in one sentence.
- Change one field — keep everything else byte-identical.
- Generate two or three takes of the new version.
- Keep or revert, then log what you changed and what happened.
Example
Practice
Take your least successful generation and run three disciplined iterations on it, changing exactly one field each time and logging the verdict. Resist the urge to fix two things at once even when both are obvious. The point is not this one track — it is building the habit that makes every later prompt converge faster.