The difference between a useless AI answer and a brilliant one is almost always the prompt. Here are ten patterns that consistently lift quality, no matter which model you use.
1. Set the role
"Act as a senior tax accountant reviewing my return." Roles narrow the model's voice and expertise.
2. Specify the audience
"Explain this for a smart 14-year-old" produces clearer answers than any "explain like I'm five" cliché.
3. Ask for the failure mode first
"Before answering, list three ways this question could be misinterpreted." Forces the model to clarify before committing.
"A great prompt is half the answer."
4. Constrain the format
"Reply in exactly three bullet points, each under 15 words." Specificity beats hope.
5. Use examples
Show one or two examples of the output you want. This is the single highest-leverage prompting technique.
6. Ask for the opposite
"Now argue the other side." AI is great at steelmanning when you ask explicitly.
7. Chain of thought
"Think step by step before answering." Adds latency, slashes errors on math, logic, and planning.
8. Iterate, don't restart
If the answer is close, say "Refine the second paragraph to be more concrete." Don't start a new chat.
9. Provide your own data
Paste your transactions, your draft, your notes. AI is far better at analysing your specifics than producing generic advice.
10. Ask it to grade itself
"Score this answer on accuracy, clarity, and usefulness. Then improve it." Free quality boost.
Putting them together
Individually these are tricks. Combined, they are a template. A prompt using several at once looks less like a question and more like a brief:
You are reviewing a technical blog draft for a developer audience.
Here is the draft:
<draft>
...paste the actual text...
</draft>
Here is an example of the tone I want:
<example>
...paste two paragraphs you like...
</example>
Before rewriting, list the three weakest paragraphs and why.
Then rewrite only those three. Keep every code block unchanged.
Reply with the numbered critique first, then the rewrites.
That prompt sets a role, supplies real material, gives an example, asks for analysis before output, and constrains the format — five patterns in one. It takes ninety seconds to write and saves three rounds of "no, not like that."
What does not work
A fair amount of popular prompting advice is folklore that persisted past the models it was written for:
- Flattery. "You are a world-class expert" does not measurably improve modern models. It costs tokens and buys tone at best.
- Threats and bribes. Offering a tip or warning about consequences was always more meme than method.
- Over-long system prompts. Past a point, extra instruction dilutes rather than sharpens. When a prompt stops working, the fix is usually deleting half of it, not adding more.
- Restating the same instruction three ways. Models are not more convinced by repetition; you have just spent context window on redundancy.
FAQ
Do these work the same across ChatGPT, Claude, and Gemini?
The structural ones — examples, format constraints, supplying real context — transfer cleanly because they are about information, not phrasing. Model-specific quirks exist but matter far less than people assume.
Is "think step by step" still necessary?
Less than it used to be. Reasoning models do it internally, and asking explicitly can be redundant. On non-reasoning models and on genuinely multi-step problems, it still helps. Try without it first.
How long should a prompt be?
As long as the context requires and no longer. A prompt that is mostly your actual material with a few lines of instruction is usually right. A prompt that is mostly instruction with no material is usually the problem.
Where do I go deeper for a specific job?
The patterns are general, but worked examples help. Prompts for developers and prompts for data analysis apply the same ideas to concrete tasks.
The meta-lesson
Prompting is editing. Treat your first prompt as a draft — because that is what it is. When the answer disappoints, the instinct is to argue with the model in the next message. The faster move is to go back and fix the prompt, since the flaw is nearly always missing context rather than a misunderstood instruction.
None of this is a skill that takes months. Within a week of deliberately applying these patterns, the gap between your output and the average will be obvious, and it will have almost nothing to do with knowing secret phrases.