A good support prompt isn't a magic trick. It's a checklist you don't have to remember, run by something that never gets bored.
Start with the smallest version
Ask for the reasoning, then the result. When the model shows its steps you can see exactly where to push back.
Anchor to one reader
Ask for the reasoning, then the result. When the model shows its steps you can see exactly where to push back.
- Compare two outputs instead of trusting one
- Name the audience and the single goal before you generate
- Save the prompt that worked so the next person reuses it
Treat the first output as a draft, not a verdict. The prompt does the typing; you keep the judgment about what ships.