The Overlord's Lexicon
What is Prompt Engineering?
Also known as: Prompting, Prompt design
Prompt engineering is the practice of writing and structuring instructions for an AI model — context, task, examples, constraints and output format — so it reliably produces the result you want.
Prompt engineering is the craft of telling an AI exactly what you want. The model is capable; your instructions are usually the bottleneck. A vague prompt gets average output. A precise one gets output you can actually use.
The techniques that work
- Give context. Who is this for? What’s the goal? What does the model need to know that it can’t guess? “Write a product description” is weak. “Write a 120-word description of this standing desk for remote software developers, emphasising cable management, in a dry, witty tone” is strong.
- Show examples (“few-shot prompting”). One or two samples of the output you want beat paragraphs of description.
- Specify the format. Bullet list, table, JSON, 3 subject lines — say so.
- Set constraints. Length, reading level, words to avoid, sources to use.
- Break big tasks into steps or ask the model to reason first — see chain of thought. Modern reasoning models do much of this automatically.
- Use a system prompt for standing instructions that apply to every message.
- Iterate. Treat the first output as a draft and tell the model what to change.
An analogy for the meatbags
Briefing an AI is like briefing a very fast freelancer who has never met you. “Make me a logo” gets you something generic. A real creative brief — audience, competitors, colours, three logos you love — gets you something usable. The freelancer didn’t get smarter. You got clearer.
Why it matters for the Chosen
Prompting is the most transferable AI skill there is. Every tool in the Arsenal — writing, image, video, coding, automation — is steered by instructions. Good prompting means:
- Fewer rewrites, so you actually save the time AI promised.
- Reusable prompt templates that turn one-off wins into repeatable processes (see our Prompt Vault at /prompts).
- Better results inside automations and agents, where nobody’s around to fix a bad output by hand.
People sell prompt libraries, build prompt-driven tools, and charge for AI setup work that is, at its core, careful prompting plus domain knowledge.
What prompt engineering is not
It is not magic phrases. Old tricks like “you are a world-class expert” or threatening the model matter far less than clear context and examples. It also can’t fix a model’s fundamental limits: prompting reduces hallucinations, but doesn’t eliminate them. And deliberately crafting prompts to bypass safety rules is a different thing entirely — that’s a jailbreak.
Tools from the Arsenal
ChatGPT
AI WritingOpenAI's general-purpose assistant: writing, research, images, voice and agents in one chat box.
Claude
AI WritingAnthropic's assistant: the strongest long-form writer and careful reasoner in the consumer AI pack.
Gemini
AI WritingGoogle's assistant, wired into Gmail, Docs, Drive and the rest of your Google life.
Questions the Humans Keep Asking
Is prompt engineering still important with smarter models?
Yes, though it has changed. Newer models need fewer tricks, but they still can't read your mind. Giving clear context, goals, examples and a desired format remains the biggest lever on output quality.
Is prompt engineer a real job?
Dedicated 'prompt engineer' roles exist but are less common than the skill itself, which is now expected in many jobs — marketing, development, support, operations. The bigger opportunity is applying prompting to a specific domain.
What is a good prompt structure?
A reliable pattern: role or context, the task, relevant background or data, constraints (length, tone, what to avoid), examples of good output, and the exact output format you want.