Prompting, Without the Mystique
Every 'prompt engineering' article you've read is overcomplicating it. Prompting is just clear communication — and there's a four-line pattern that works on any model.
The big secret
There isn’t one.
“Prompt engineering” is a word people use to make a chat box sound technical. What it actually is: clear communication. If you can write a good email to a smart new hire, you can prompt an AI.
That’s the whole skill. Now let’s get you better at it.
The four-line pattern
Use this. It works on ChatGPT, Claude, Gemini, anything.
ROLE: [who is the AI being, for this task]
TASK: [what you want, specifically]
CONTEXT: [what they need to know to do it well]
FORMAT: [how the answer should look]
That’s it. Memorize it. You’ll outperform 90% of people inside a week.
A bad prompt
“Write me a marketing email.”
This is what most people start with. It’s also why most people walk away unimpressed.
A good prompt
Role: You’re an email copywriter for a small Brooklyn coffee roastery. Task: Write a launch email for our new Ethiopian single-origin. Context: Our voice is warm, slightly sarcastic, never preachy. The roast is bright, citrus-y, $22/bag. Audience: subscribers who’ve bought from us before. Format: Subject line + 100-word body + clear CTA. No emojis. Don’t use the word “passion.”
The difference isn’t IQ. The difference is detail.
Why “act as an expert” is wasted
You’ll see this in every “best prompts” listicle: “You are an expert marketing strategist with 20 years of experience…”
It does almost nothing. The model is already capable; what it needs from you is the specifics of the situation, not a hyped-up backstory.
Spend that line on context instead.
When to give examples
Examples are a power move. But only when:
- The output has a specific shape (a JSON schema, a particular tone, a recurring pattern).
- The model keeps getting close but not quite right.
For a single email or a one-off question, examples are usually overkill. For anything you’ll re-run, examples turn the model into a reliable engine.
The single best habit
After every response: react.
If it’s wrong, say what’s wrong and ask again. If it’s close, say what to keep and what to change. The first answer is rarely the best one. The third answer almost always is.
This is the part most people skip. It’s also the part that separates “AI is overhyped” from “I save 6 hours a week.”
Want more like this? Drop your email below — we send one guide a month, no fluff.
Common questions
- What is prompt engineering?
- Prompt engineering is the practice of writing instructions to AI models so they consistently produce useful output. In 2026, modern models (Claude, ChatGPT, Gemini) are good enough that 'engineering' is overstated — clear writing with four elements (role, task, context, constraints) gets you most of the way. Anything labeled 'advanced prompting' that doesn't include these four is usually noise.
- Do prompts work the same on Claude, ChatGPT, and Gemini?
- Mostly yes. The same four-element prompt (role, task, context, constraints) works reliably on all three. Subtle differences: Claude tends to follow detailed multi-step instructions slightly more literally; ChatGPT is slightly more proactive with format guesses; Gemini is slightly stronger with multi-modal inputs. For 95% of prompts you write, the same wording works across all three models.
- Should I tell the AI to 'act as an expert'?
- Usually no. Saying 'act as an expert copywriter' or 'you are a senior consultant' rarely changes output quality on modern models. What does change output: giving real context (what the document is, who it's for, what tone you want, what to avoid). Roles can help when you need a specific voice (e.g., 'write like a no-nonsense plumber explaining to a customer') but generic 'expert' framing is mostly placebo.
- What's the four-line prompt pattern?
- The four-line pattern: (1) Role — who the AI is responding as, if it matters; (2) Task — what you want done, as a verb; (3) Context — what the AI needs to know about your situation, audience, format; (4) Constraints — what not to do, how long the output should be, what voice to avoid. Write each as one short sentence. Most prompts under 100 words that include all four produce better output than 500-word prompts missing any one of them.
- When should I give the AI examples?
- Give examples when you want a specific format or voice you can't easily describe in words — e.g., 'write the email like this previous one I wrote.' Don't give examples when the task is well-known (the AI has seen thousands of examples in training) or when your examples are mediocre (you'll anchor the output to mediocrity). Two strong examples beat one weak example by a wide margin.
- Why does the same prompt give different results sometimes?
- Modern AI models are non-deterministic by default — slight variation is expected. For consistency, you can set 'temperature' to 0 in API tools, but most chat interfaces don't expose this. If your prompt produces wildly different results across attempts, the prompt is probably underspecified — add constraints, context, or examples to narrow the range.
- Is prompting still a useful skill in 2026, or are models smart enough now?
- Models are smart enough now that bad prompts still produce mediocre output, but good prompts produce extraordinary output. The skill has shifted from 'how to talk to AI' (which mostly doesn't matter) to 'how to specify what you want clearly' (which matters more than ever). Anyone who can write a clear paragraph can be a 90th-percentile prompter — there's no specialized vocabulary or technique you're missing.
Let's talk it through.
Book a 30-minute strategy call or send us a message. We'll figure out how to apply this to your specific situation.