🎯 The difference between prompting and prompt engineering
Prompting is asking. "Write me an email about the invoice." You get something. Maybe it's good.
Prompt engineering is designing. You define the role, constrain the output, give examples, and test variations until the result is reliably excellent — not just occasionally good. Then you save it so you never have to design it again.
The gap between these two approaches is large. A random prompt to an AI gets a random result. A well-engineered prompt to the same AI gets a consistent, high-quality result every time — one you can hand to anyone in your team and they'll get the same quality output.
Who this matters most to: Anyone who uses AI regularly for the same types of tasks — proposals, client emails, reports, social content, internal comms. The 30 minutes you spend engineering a prompt pays back every time you use it.
🧠 System prompts — shaping all responses
A system prompt is a set of instructions that runs before every conversation. When you chat with an AI normally, you're using a default persona. System prompts let you define a custom persona for a specific purpose — and it applies to every message in that session.
In Claude.ai, ChatGPT, and Google AI Studio, you can write a system prompt under "Custom instructions," "System instructions," or similar settings. You write it once. Every conversation inherits it.
Three types of system prompt to know:
Where to set system prompts: Claude.ai → Settings → Custom Instructions. ChatGPT → Customise ChatGPT. Google AI Studio → System instructions (top of a new chat). For Gemini.google.com, use the "Gems" feature to create persistent instructions.
🔗 Few-shot prompting — show, don't just tell
Few-shot prompting means giving the AI 2–3 examples of what you want before asking it to produce a new one. It's one of the most reliable ways to get consistent output — especially for tone, format, or style.
The AI learns from patterns in its training. When you show it a pattern in your prompt, it continues that pattern. This is especially useful for:
- Writing in a specific house style or brand voice
- Converting raw data into a consistent report format
- Generating content that matches examples you like from elsewhere
- Training the AI to follow a structure it wouldn't naturally choose
Why this works better than describing the style: "Write in a warm, casual, NZ coastal tone" is subjective. Showing three examples is objective. The AI pattern-matches to the examples directly — length, punctuation, vocabulary, structure. Show what you want; don't describe it.
🤔 Meta-prompting — make the AI think first
Meta-prompting is asking the AI to reason about a problem before answering it. Instead of "Write a solution," you say "Think through this step by step before giving me your answer." The output quality difference is significant for complex tasks.
Four meta-prompting techniques worth using:
⚖️ Claude vs Gemini vs ChatGPT — prompting differences
The same prompt can produce meaningfully different results from different models. Knowing each model's character helps you get better output faster.
Prompt tip: Be explicit about format and length. Claude can be verbose — "Keep this under X words" prevents sprawl.
Prompt tip: Use AI Studio for power use — temperature control and system prompts give you far more control than the consumer chat interface.
Prompt tip: More agreeable and less likely to push back than Claude. Good for creative tasks where you want more yes-and, less interrogation.
Practical strategy: Don't be loyal to one model. Claude for careful writing, Gemini for documents and research, ChatGPT for images and tool integrations. Switch based on the task. All the major models are free to try. The right prompt in the right model beats a great prompt in the wrong one.
📚 Build your personal prompt library
The highest-leverage thing you can do right now: collect your best prompts in a document you can reuse. A prompt library is a compounding asset — every prompt you engineer is leverage on every future use.
For each prompt you add, record:
- What it's for — one line describing the task
- The prompt itself — the full text, ready to copy-paste
- Best model — Claude / Gemini / ChatGPT (or "any")
- Example output — one example of a result you liked
- Last updated — models change; prompts that worked 6 months ago may need tweaking
Start simple: A Google Doc or Notion page with a table works fine. Dedicated prompt management tools (PromptLayer, FlowGPT) exist but add complexity. Start with what you'll actually use. The discipline of writing prompts down and noting which model they work best on is the skill — not the tool you store them in.
👇 Build your first prompt template
Pick one thing you regularly use AI for (or want to). Write a proper engineered version. Answer all five questions:
- Role: Who is the AI in this conversation? (expert, assistant, critic, translator...)
- Context: What do I always need the AI to know about my situation?
- Format: What does the output look like? (length, structure, tone, forbidden phrases)
- Examples: Can I show 1–2 examples of what "good" looks like for this task?
- Anti-patterns: What should it NOT do? (hedge, use jargon, start with "Certainly!"...)
Test it. Refine it until you'd use it without editing the output. Then save it as the first entry in your prompt library.
If you're not sure where to start: try engineering a prompt for writing emails in your organisation's voice, or for summarising meeting notes into action items with owners and deadlines.
Branch complete 🔥
Every hour you spend engineering prompts now is leverage on every task that follows. A good prompt library is one of the most genuinely useful professional assets you can build in 2026.