Skip to content
← All free guides
Getting started Multi-tool 7 min read · free

Prompting basics: the anatomy of a great prompt

A simple structure that reliably turns mediocre answers into genuinely useful ones.

The short answer

Put four things in every request: a role ('act as an editor'), the task, the context it can't guess, and the format you want back. A missing one is why answers come out generic.

You don't need to be a 'prompt engineer' — that's mostly hype. You need a repeatable structure so you stop relying on luck. Almost every weak answer is missing one of four ingredients, and once you can name them you can fix any bad answer in seconds. Here's the structure, plus a pack of reusable prompt skeletons.

Beginner

The four parts of a great prompt

Role — who you want it to be (a blunt editor, a patient tutor, a careful analyst); this sets the lens. Task — the one concrete thing you want, stated plainly. Context — the background it can't guess: audience, goal, constraints, an example. Format — how you want the answer shaped: length, bullets or prose, tone. Role primes the thinking, context does the heavy lifting, and format saves you a round of cleanup.

Intermediate

Diagnose with the four parts

You don't have to label all four every time — that's exhausting. Use them as a checklist when an answer disappoints. Bland and generic? You skipped context. Right idea, wrong shape? You skipped format. Off-tone? You skipped role. This turns 'the AI is bad at this' into 'I under-specified part three', which is always fixable. Add just the missing part and re-send in the same chat.

Advanced

Show, don't describe

The single biggest upgrade above the four parts is examples. Describing a style with adjectives ('punchy and warm') is slow and unreliable, because those words mean different things to everyone. Pasting two or three examples of exactly what you want lets the model copy the real pattern — voice, length, structure — instead of guessing. Whenever quality matters, show a sample, don't describe a vibe.

  1. 1Role — 'Act as a blunt editor / a patient tutor / a careful analyst.'
  2. 2Task — say the one thing you want, plainly.
  3. 3Context — give the background it can't guess, plus an example.
  4. 4Format — say how you want it back: length, bullets or prose, tone.

Reusable prompt skeletons

promptAct as [role]. [Task]. Context: [who it's for, the goal, any constraints]. Format: [length, structure, tone].
promptAct as a careful copy editor. Tighten the paragraph below for clarity. It opens a landing page for [audience] who dislike hype. Return the rewrite, then 2 bullets on what you changed: [paste].
promptHere are 2–3 examples of the style I want [paste]. Study the voice, sentence length and structure, then write [new thing] in that exact style. Don't explain — just produce it.
promptBefore you answer, ask me up to 3 questions that would most change your response. Then answer.
promptGive me 3 options with a short recommendation, and end with what could go wrong with your pick.
promptThat wasn't quite right. The problem is [too long / too generic / wrong tone]. Here's the context I should have given: [...]. Try again as [specific format].
promptCritique this like a skeptic, list the 3 biggest weaknesses, then rewrite it to fix them: [paste].
💡 When an answer disappoints, ask which of the four parts you skipped, add just that one, and re-send. Nine times out of ten it's the context.

Want the prompts that go further?

Drop your email + WhatsApp — I'll send the weekly playbook and the full prompt vault.

Prefer to ask first? Message me on WhatsApp · see plans

More guides like this