How to write a good prompt: a method, not a list of tricks
You've tried the lists of “magic prompts” you found online. You pasted in the formula, and the result was generic, off target, or technically fine but unusable. You concluded the tool was overrated.
The problem isn't the formula: it's that no formula can contain what the AI doesn't know — your situation. A good prompt isn't an incantation, it's a clear brief. And writing a clear brief is a skill you can learn in twenty minutes.
Why copied prompts disappoint
A prompt you find on the internet was written for someone else's situation. When you paste it in, the AI receives a precise request about a context it doesn't have. It fills in the gaps — which is exactly what it's good at — and produces a plausible answer for an imaginary situation.
That's why a short, precise prompt about your case almost always beats a long, impressive prompt written for a general one.
The four elements of a request that works
A useful request contains four things. None of them is technical.
| Element | The question to ask yourself | Example |
|---|---|---|
| The situation | Who's speaking, and in what setting? | “I'm a self-employed physiotherapist, working alone for the past six months.” |
| The task | What exactly do I want? | “Write a follow-up message to a patient who hasn't rebooked.” |
| The constraints | What's off limits or required? | “Six lines maximum, polite, without sounding like a sales pitch.” |
| The format | What form should the answer take? | “Give me two versions, one of them warmer.” |
All four fit in four sentences. That's shorter than most ready-made prompts, and far more effective.
Before and after, on a real case
Vague request: “Write a listing to sell my apartment.”
Result: a one-size-fits-all text full of “bright”, “quiet” and “close to all amenities”. Unusable, because nothing in it describes your property.
The same request, properly briefed: “I'm selling a 470 sq ft one-bedroom apartment on the third floor with no elevator, in a lively neighbourhood close to the city centre. Strengths: very bright, south-facing, kitchen renovated in 2024, low service charges. Weaknesses: no elevator, busy street. Write an honest 150-word listing that owns the weaknesses instead of hiding them. Factual tone, not salesy.”
Result: a text that couldn't describe any other property. The difference isn't a trick: it comes from information you provided and nobody else could have.
Iterate instead of starting over
The most time-consuming mistake is deleting everything and rewriting when the answer isn't right. The conversation keeps its context: use it.
- Correct the direction: “Too formal — redo it in a more direct tone.”
- Narrow it down: “Keep only the first two points and expand the second.”
- Ask it to explain: “Why did you choose this angle?” — useful for seeing what it misunderstood.
- Ask for options: “Give me three different angles before you write anything.” Choosing costs less than correcting.
That last technique is the most underused. Asking for options before drafting saves you from receiving a thousand words heading the wrong way.
Set the output format
By default, these tools produce long answers, structured with headings and subheadings, plus an introduction and a conclusion. That's rarely what you need.
One sentence is enough to fix it: “Answer in three bullet points”, “Give me a two-column table”, “One sentence, no introduction”, “Answer only yes or no, then one line of explanation”.
When you repeat the same task often, keep that format sentence with your standard request. It's the only part of a prompt worth reusing word for word.
Three common traps
Stacking contradictory instructions. “Be thorough but concise” produces something middling. Choose one.
Asking for several things at once. One request, one answer. Chain your requests rather than cramming everything into a single message.
Assigning a role without giving context. “You are a marketing expert” doesn't replace information about your business. The role steers the vocabulary; it adds no knowledge about your situation.
What's worth saving
Unlike prompt libraries, two things are worth keeping: your format instructions and your context description. The first explains how you want to receive answers; the second describes who you are and what you do.
Pasted at the start of a conversation, those two blocks outperform any list of formulas — because they contain what nobody else can write for you.
If you're brand new to these tools, start with our guide for complete beginners instead: phrasing comes after understanding how they work.
Frequently asked questions
Should prompts be long?
No. The right length is whatever covers your situation, your task, your constraints and the format you want. Four precise sentences beat a page of generic instructions.
Are ready-made prompt lists useful?
Not much, except as inspiration for structure. They fail because they don't contain your context — and context is exactly what separates a generic answer from a usable one.
Should I tell the AI it's an expert?
It steers the vocabulary and level of detail without adding any knowledge. Useful alongside real context, useless as a substitute for it.
What should I do when the answer is almost right?
Don't start over. Ask for a targeted fix: shorter, a different tone, remove this passage, expand that point. The conversation keeps the context — that's its main advantage.
Does the same prompt always give the same result?
No. These models involve some randomness, and two identical requests produce different answers. If you like a result, save it: you won't get exactly the same one again.
From trial and error to second nature
Level 2 of the AI Academy teaches a method for phrasing requests rather than a prompt library: structuring your thinking, giving the right context, iterating. Free sample available.
See the AI Academy