Prompt Engineering·When Things Go Sideways·5 min read·Sep 5, 2026
The Quick-Reference Card
A one-page cheatsheet of one-line prompt upgrades, a 60-second audit, and emergency fixes for answers that are too long, short, or off-topic.
A one-page reference for when you don't need the full explanation, just the fix. Bookmark this chapter.
One-line upgrades
Add "for [specific audience]"
Turns a generic answer into one aimed at someone real.
Add "3 concrete examples"
Forces abstract advice into something actionable.
Add "exactly N words"
The single most reliable length control: beats "be brief" every time.
Add "focus only on X, ignore Y"
Stops the response from wandering into adjacent topics.
Add "think step by step"
Improves accuracy on anything involving math, logic, or trade-offs.
Add "if unsure, say so"
Cuts down on confidently wrong answers.
Add "in the style of [example]"
Sets tone and format faster than describing either in words.
Start with "You are a [role] who..."
Shapes depth and vocabulary before the task even starts.
The 60-second audit
- Task: is there a clear action verb (analyze, draft, compare, list)?
- Context: does it have the background it needs, and nothing it doesn't?
- Audience: did you say who this is for?
- Format: length, structure, and style all specified?
- Constraints: what should it include or leave out?
- Examples: would showing one clear up any ambiguity?
- Success criteria: could you tell a good answer from a mediocre one?
TASKS: a five-part shape for anything non-trivial
Task
The specific action you want performed.
Audience
Who reads the output, and what they already know.
Style
Tone, formality, voice.
Knowledge
The context the model can't infer on its own.
Success
What makes this a good answer versus a mediocre one.
Emergency fixes
Too long
"Maximum 100 words."
Too short
"Provide full detail, including at least 2 examples."
Off-focus
"Focus only on X. Ignore everything else."
Too complex
"Explain as if to someone with no background in this."
Too basic
"Give an expert-level answer with technical depth."