Prompt engineering basics: 7 patterns that actually work
Role, context, task, format, plus the four failure modes behind almost every disappointing answer.
A prompt is a brief, not a spell
There are no magic words. What looks like a magic phrase is usually just a clearer instruction: it narrows the space of acceptable answers, so the model has fewer ways to be vaguely right.
Treat every prompt as a brief to a fast, widely read colleague who has never met your client and cannot see your screen.
The four patterns you will use daily
These four cover most everyday work. Learn them properly before collecting anything more exotic.
Three patterns for harder work
When the task is longer than a paragraph or the stakes are higher, these three earn their keep.
The four failure modes
Almost every bad answer is one of these, and each has a fix that takes ten seconds.
A template you can reuse
Keep one template in a note app and adapt it. After a few weeks you will write it from memory, and that is the actual skill.
Role: you are <role>, writing for <audience>. Context: <paste the real material> Task: <one verb, one deliverable> Format: <length, structure, tone> Rules: do not invent facts. If something is missing, list it as missing instead of guessing. First ask me up to three questions if anything is unclear.