How to Write Prompts
That Actually Work
Most people talk to AI like it's a search engine. Type a few words, hope for magic, get mush, blame the tool.
Here is the shift: a prompt is not a magic spell. It's a brief. You're handing work to the smartest, fastest teammate you've ever had — one who will do exactly what you ask, and nothing you forgot to mention.
This playbook is the exact way I write prompts when I build AI systems for companies. No jargon. No theory you can't use tomorrow morning. Just the patterns that separate a prompt that ships from a prompt that wastes your afternoon.
The One Mental Shift
Before any technique, internalize this. It's worth more than every tip below combined.
A search engine takes keywords and hands back links. A teammate takes context and produces work. When you type three vague words, you're forcing the AI to guess everything you didn't say — who you are, what you're doing, what "good" looks like. It will guess. Sometimes wrong.
The whole game is simple: reduce the guessing. Every sentence of context you add is one less thing the AI has to invent. You already know how to do this — it's the same skill as briefing a new hire on their first day. You'd never say "write the thing" and walk away. You'd tell them who it's for, what it needs to do, and what done looks like.
And here's the freeing part: you don't need to be technical. The most valuable prompting skills — clarity, context, knowing what "good" looks like — are writing and thinking skills, not coding skills. If you can brief a colleague, you can prompt.
The 3-Sentence Formula
When you're moving fast, you don't need a template. You need a reflex. This is it — the pattern that works 80% of the time:
1. Describe who you are.
2. Describe what you want.
3. Describe how you want it formatted.
Three sentences, max. That's the difference between a reply you throw away and one you actually use. Watch what it does to a real request:
Same task. The second one gets used as-is. The first one gets rewritten by you, which means the AI saved you nothing.
Anatomy of a Great Prompt
When the task is bigger, the 3-sentence reflex expands into five building blocks. You won't always use all five — but knowing they exist means you'll never wonder "why is this output so off?" It's almost always a missing block.
Read them top to bottom and you have a complete brief. Notice the order isn't random — role and context go first, because they frame everything that follows. Put the most important instructions at the very top, and re-state any critical rule at the very end. The AI pays the most attention to the beginning and the end of what you give it.
The 7 Principles
These are the moves I come back to on every single build. Each one is a small habit with an outsized payoff.
Give it a role
Telling the AI who to be is the cheapest way to level up an answer. "You are an experienced onboarding specialist" instantly sets the tone, the depth, and the vocabulary. One sentence does the work of a paragraph of instructions.
Be specific — vague in, vague out
The AI can't read your mind, so it fills gaps with averages. "Make it better" means nothing. "Make it shorter, warmer, and cut the jargon" means everything. Specificity isn't extra work — it's the work.
Show an example, don't just describe
One good example beats three paragraphs of instructions. If you want a specific format or tone, paste a sample of it. The AI is brilliant at pattern-matching — give it a pattern to match.
Ask it to think step by step
For anything with reasoning — analysis, decisions, math, comparisons — tell it to work through the steps out loud before giving the answer. Accuracy jumps. "Think step by step" is a genuine cheat code for complex tasks.
Speak plain human
Write the prompt the way you'd actually talk to a sharp colleague. You do not need robotic keywords, ALL CAPS commands, or fake "act as an expert" incantations stacked ten deep. Natural, clear language works best. If it reads like a normal request, you're doing it right.
Give permission to say "I don't know"
The biggest fear people have — "what if it makes something up?" — has a one-line fix. Explicitly tell it that being unsure is allowed. This alone kills a huge share of confident-but-wrong answers.
One job per prompt
When you cram five unrelated tasks into one message, quality drops on all five. The AI, like a person, does its best work when it's focused. If you catch yourself writing "and also… and while you're at it…", split it into separate prompts. Tight scope = sharper output, less drift, fewer mistakes.
Do's & Don'ts
Pin this to the wall. It's the whole playbook compressed into two columns.
- Brief it like a teammate: who / what / how
- Give it a clear role or persona
- Say what "good" looks like — length, tone, format
- Paste an example of what you want
- Add context: the audience, the goal, the situation
- Ask it to think step by step on hard tasks
- Give permission to be unsure
- Keep one job per prompt
- Iterate — treat the first reply as a draft, then refine
- Type three vague words and expect magic
- Say "make it better" (better how?)
- Stack fake "elite genius expert" keywords
- Cram five tasks into one message
- Assume it knows context that's only in your head
- Blindly trust it — always check the output
- Add more and more rules when it drifts (split instead)
- Give up after one bad reply
- Paste confidential data you wouldn't email externally
Copy-Paste Recipes
Real prompts for real work. Swap the bracketed bits for your details and go. Each one already bakes in the principles above.
Turn a messy call into a follow-up
One idea, five channels
Summarize a long thread into decisions
Pressure-test your own thinking
Explain it like I don't have the background
When It Goes Wrong
It will, sometimes. The output misses, or the AI can't find what you meant. Here's the reflex that fixes 90% of it — and it's almost never "write a cleverer prompt."
- Add the missing context. Tell it what it couldn't have known — "this is for a non-technical audience," "look at the second attachment," "we're a healthcare company, so tone matters." Nine times out of ten, the gap was information, not phrasing.
- Say "explain it like I'm slow." If you're the one who's lost, ask it to re-explain the last step in plain language. No shame, no wasted time — it's the fastest way to unstick yourself.
- Show it broken vs. working. Stuck on something visual or structural? Paste an example of what it should look like and say "here's the target, here's what I got — help me close the gap." A comparison beats a description every time.
- One change at a time. Don't rewrite the whole prompt in frustration. Change one thing, run it, see what moved. Batch-changing means you never learn what actually worked.
- Split it if it's drifting. If the AI keeps wandering off-task, the answer is rarely "add more rules." It's usually "you asked for too much in one go." Break it into two focused prompts.
Trust, But Verify
This is the one habit that separates people who use AI safely from people who get burned by it.
Judge the output against reality — not against the AI's claim that it worked. The AI will always sound confident. Confidence is not correctness. Before you send, ship, or act on an answer, do the ten-second check: are the facts right? Do the numbers match the source? Would I stake my name on this?
For anything that matters, ask yourself two questions before trusting it: "What does a correct answer look like?" and "Have I actually checked this one against that?" If you can't define what "correct" looks like, you can't tell whether the AI got there.
This isn't fear — it's fluency. Use AI for the first draft, the heavy lifting, the blank-page problem. Keep your judgment for the final call. That combination — the AI's speed plus your accountability — is exactly where the value lives.
The Cheat Sheet
If you remember nothing else from this page, remember this table.
| The move | What to actually do |
|---|---|
| Reframe | Brief it like a teammate, not a search engine |
| The formula | Who you are · what you want · how you want it |
| Role | Start with "You are a…" — it sets everything |
| Specific | Vague in, vague out. Name the length, tone, format |
| Example | Show a sample instead of describing it |
| Reasoning | Say "think step by step" for hard tasks |
| Honesty | "If unsure, say so — don't invent" |
| Focus | One job per prompt. Split when it drifts |
| When stuck | Add context, not cleverness |
| Always | Verify the output against reality before trusting it |
None of this requires code. It requires clarity. You already have that skill — now you know how to point it at the most capable teammate you'll ever brief.
It's a result you can measure.
I build AI agent systems for companies — from mapping to full implementation. Thousands of builders are already in the community.
Grounded in patterns from real client builds, plus published prompting guidance from Anthropic's Claude documentation and prompt engineering best practices.