When you ask the model to change what (content), it's relatively easy: you name the data point, it changes it. When you ask it to change how (tone, style, register) things drift more. "Make it more casual" doesn't mean the same thing to you as it does to the model.
Orbit is the communicator. Her default is formal and bureaucratic. "Dear crewmates, you are hereby informed...". You're going to redirect her to a professional but direct tone. without changing the content of the announcement.
| Vague (one notch at a time) | Specific (direct jump) |
|---|---|
| "more casual" | "no 'dear crewmates', active voice" |
| "more natural" | "short sentences, no formalisms" |
| "better" | "no 'we kindly request' or 'thanking you in advance'" |
Vague requests make the model drop one notch from the dominant style. Specific requests put it where you want in a single turn.
Four pointed instructions, one protective line at the end. One turn, three levels of change.
4 criteria:
Max 6 turns.
Tip: think of tone as a dial with many clicks. A vague request = one click. A specific request that names 3 things = 3 clicks at once. When you know where you want to land, ask for the 3 clicks together.