Most prompts are shapeless blobs of text — a vague request, maybe some context dumped in randomly, fingers crossed. There’s a better way. How to structure prompts for best results comes down to a simple 5-part framework I’ve refined over hundreds of hours of AI work. It works across ChatGPT, Claude, Gemini, and basically every model. Once you internalize it, good prompting becomes automatic.
The 5-Part Prompt Structure
Part 1: Role — Who Should the AI Be?
Start by telling the AI what expert to channel. “You are an experienced email copywriter” / “You are a senior data analyst” / “You are a patient math tutor.”
Does this actually work, or is it placebo? It works — modestly but measurably. It primes the model’s tone, vocabulary, and approach. Don’t overthink it; one sentence is enough. Skip it for simple tasks where role doesn’t matter.
Part 2: Context — What Does the AI Need to Know?
This is the part most people skip, and it’s the part that matters most. Background, audience, goal, constraints of the situation. The rule: include anything a smart human would need to do the job well.
Example: not “write a job post” but “we’re a 15-person SaaS startup hiring our first customer success manager; we need someone scrappy who can build the function from scratch; we’re remote-first, salary range $70-90k.”
Part 3: Task — What Exactly Should It Do?
One clear task per prompt. “Write,” “summarize,” “analyze,” “compare,” “brainstorm” — pick the verb and be specific about the deliverable. If you have three tasks, that’s three prompts (or one prompt with three clearly separated sections).
Part 4: Format — What Should the Output Look Like?
Length, structure, tone, style. “300 words, three sections with headers, bullet points for recommendations, professional but warm tone.” The more precise, the less editing you’ll do. AI is genuinely excellent at following format specs — take advantage.
Part 5: Examples — What Does “Good” Look Like?
One example beats a paragraph of description. Paste a sample of the tone, format, or quality you’re after. This is the highest-leverage part of the structure — if you only add one thing to your prompts, add this.
The Template in Action
Here’s a complete prompt using all five parts:
“You are an experienced B2B copywriter. [ROLE]
We’re launching a project management tool for architecture firms. Our buyers are firm principals, 40-60, who are skeptical of new software. [CONTEXT]
Write a landing page hero section: headline, subheadline, and three benefit bullets. [TASK]
Keep the total under 120 words. Tone: confident, plain-spoken, zero jargon. No exclamation marks. [FORMAT]
Here’s our voice from a recent email: [paste example]. [EXAMPLES]”
Compare that to “write landing page copy for our app” and tell me which gets the better result. It’s not close.
Adapting the Structure
You don’t need all five parts every time. Quick questions need just a task. But for anything important — content you’ll publish, analysis you’ll act on, code you’ll ship — run through all five. It takes 60 seconds and the quality jump is dramatic.
For Claude specifically, wrap parts in XML tags (<context>, <instructions>) — it responds especially well to that. Our Claude prompting guide covers the details.
Common Structure Mistakes
- Burying the task. Put the actual request somewhere findable — ideally after context, clearly stated. Don’t make the AI hunt for what you want.
- Context dumping without organization. A wall of pasted text with no labels is almost as bad as no context. Use headings or tags.
- Contradictory instructions. “Be concise but thorough” / “formal yet casual” — pick one. Contradictions produce mush.
- Forgetting constraints. Tell it what not to do. Constraints are free quality.
Keep Improving
Structure gets you 80% of the way. The last 20% comes from testing: how to test which prompt version works best shows you how to systematically improve. And our better-prompts guide has more advanced techniques.
How to Structure Prompts for Best Results: The 5-Part Template
After testing hundreds of prompts, I’ve converged on a five-part structure that works across tasks: 1. Role (“You are a senior email copywriter”), 2. Task (“write a cart-abandonment email”), 3. Context (product details, audience, constraints), 4. Format (length, structure, tone), 5. Quality bar (“avoid hype words; every claim must be specific”).
You won’t always need all five — simple tasks need two or three. But when output quality matters, running through the checklist catches the missing piece. Nine times out of ten, a disappointing result traces back to a skipped part, usually context or format.
Save your best-performing prompts as templates. The compounding effect is real: a library of 20 proven prompts is worth more than any single clever trick. For more on what separates effective prompts from weak ones, see our guide on what makes a good prompt vs a bad prompt, and the formal prompt engineering literature for deeper technique.
The Bottom Line
How to structure prompts for best results: Role, Context, Task, Format, Examples. Five parts, sixty seconds, dramatically better outputs. Internalize this structure and you’ll wonder how you ever prompted without it — it’s the closest thing to a universal prompting skill that exists.
