The trap with coding prompts is asking for the finished thing. Ask for options instead, then bring your taste to the edit.
Make the output reviewable
Treat the first output as a draft, not a verdict. The prompt does the typing; you keep the judgment about what ships.
Name the failure modes
Ask for the reasoning, then the result. When the model shows its steps you can see exactly where to push back.
- Ask for three angles, then cut to the one worth shipping
- Lower the reading level, then check what broke
- Compare two outputs instead of trusting one
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.
Ask for the reasoning, then the result. When the model shows its steps you can see exactly where to push back.