The Best Prompt For Anything: The 2026 Guide to Prompts That Actually Work
There is no single best prompt, but there is a best structure. Copy-ready templates for writing, coding, research, learning and marketing, plus the five-part formula behind them.
The best prompt for any task is not a magic phrase. It is a brief. Every serious guide ranking for this question in 2026 — Anthropic's own prompt engineering guide, MIT Sloan, The Oxford AI School, Coursiv, Zemith, Talaera — lands on the same conclusion from different angles: the model can only work with what you give it, so the best prompt is the one that hands over the context it can't guess.
In one line: tell the model what you want, who it's for, what it has to work with, what the limits are, and what shape the answer should take. Then review the first answer and push it once.
Everything below is that idea, made concrete.
Even Google's own AI Overview for this query gives the same answer: no single prompt wins, but role + context + task + constraints + format wins almost everywhere. Its suggested all-purpose template ends with the same move this guide recommends: ask up to three clarifying questions before answering.
Why "the best prompt" lists usually fail
Search "the best prompt for" and you'll find hundreds of copy-paste lists. Most underdeliver for one reason: a borrowed prompt carries none of your situation. A prompt that writes a brilliant cold email for a SaaS founder writes a mediocre one for a mango exporter, because the audience, offer, tone and constraints are different.
The pattern that separates weak prompts from strong ones is simple. A weak prompt asks a question. A strong prompt briefs a colleague. "Write me a marketing plan" is a question. "I run a two-person skincare brand, $3k monthly budget, selling to women 30–45 on Instagram; draft a 90-day plan as a table with channel, action, cost and the metric we'll judge it by" is a brief.
So instead of giving you another list to copy blindly, this guide gives you the formula first, then the best prompt for each common job — written as templates you fill with your own context.
The formula: five parts of a prompt that works
Across the top-ranking guides, the same building blocks appear again and again. Here they are, merged and ordered by impact.
| Part | What it does | Example |
|---|---|---|
| Task | One clear action verb. One job per prompt. | Draft, compare, critique, extract, plan, rewrite |
| Context | The facts the model can't guess: audience, goal, what exists already, what you've tried | "This is for first-time buyers who've never used a pen scanner" |
| Constraints | Length, tone, must-include, must-avoid | "Under 150 words. No exclamation marks. Keep every number." |
| Format | The shape of the output | Table, bullets, JSON, email with subject line, 3 options labelled A/B/C |
| Perspective (optional) | The lens or expertise to apply | "Review this as a skeptical CFO would" |
Two notes from the latest guidance change how you should use this:
Format is the cheapest upgrade. It's the part people skip most, and adding "as a table with these columns" or "in under 120 words" often improves the answer more than any clever wording.
Roles matter less than they used to. "Act as a world-class expert" was the default advice for years. Anthropic's current guide says elaborate personas are often unnecessary with modern models, and can even narrow the answer. Stating the perspective you need ("evaluate this for regulatory risk") usually works better than inventing a character.
Other frameworks you'll see (they're the same idea)
| Framework | Parts | Best for |
|---|---|---|
| Role–Context–Task–Format | Role, context, one task, format | Everyday prompting (Oxford AI School) |
| Five-part brief | Role, context, task, constraints, format | Professional work (Coursiv) |
| RTFD | Role, Task, Format, Details | Business writing and email (Talaera) |
| Three Ps | Purpose, Process, Preparation | Meeting agendas (Talaera) |
| Six-element authoring prompt | Audience, objectives, context, format, tone/accessibility, assessment | Training and course content (5app) |
| Prompt-as-workflow | Context, audience, constraints, output, verification step | Research, code, marketing (Zemith) |
| Three core strategies | Provide context, be specific, build on the conversation | Beginners (MIT Sloan) |
Pick whichever acronym you'll actually remember. They all force the same discipline: say what you want, for whom, with what, within what limits, in what shape.
Explain the why
The single most underused move: say why you want something. "Don't use bullet points" is a rule the model follows mechanically. "Write in flowing prose because this will be read aloud" is a reason the model can apply to dozens of decisions you never spelled out. Motivation travels further than instructions.
Show, don't just tell
When the format or voice is hard to describe, paste an example. Start with one (one-shot) and add more only if results stay inconsistent. Modern models copy examples closely — including their flaws — so make sure your example shows only what you want.
Give it permission to say "I don't know"
Adding "If the information isn't in the material I gave you, say so instead of guessing" measurably reduces invented facts. It's one sentence and it belongs in every research, legal, medical or data prompt.
For a worked rewrite of a weak prompt using these parts, see How to Write a Good AI Prompt. For more on examples, see the guide to few-shot prompting.
The master template
Copy this, fill the brackets, delete what you don't need:
Task: [one verb + what you want]
Context: [who it's for, why it matters, what already exists, what I've tried]
Source material: """[paste notes, draft, data, code]"""
Constraints: [length, tone, must include, must avoid]
Format: [table / bullets / JSON / email / N options]
If anything important is missing, ask me up to 3 questions before you start.
That last line is, by broad agreement across the guides, the strongest single add-on you can attach to any prompt.
How to use the master template
- Write the Task line first: one action verb and one outcome.
- Add the Context the model cannot guess: who it is for, why it matters, what already exists.
- Paste your notes, draft, data or code between the triple quotes so instructions and material stay separate.
- Set the Constraints and the Format, and delete any line you do not need.
- Send it, answer the questions it asks, then review the first answer and push it once.
The best prompt for writing
Rewrite in your own voice
Here are two samples of how I write: """[samples]"""
Rewrite the text below so it sounds like me. Keep every fact. Cut corporate phrasing and filler.
Text: """[text]"""
A real sample of your writing teaches rhythm far better than adjectives like "conversational" or "punchy".
Cut it down without losing anything
Cut this by a third. Keep every fact, number and name. After the edit, list what you removed so I can put anything back.
"""[text]"""
Asking for the cuts to be listed keeps you in control of the edit.
The difficult email
I need to tell [person/role] that [bad news]. Our relationship: [context]. What I need from them: [outcome].
Write three versions under 120 words: firm, warm, and brief. Apologise at most once.
Headlines and hooks
Write 12 headlines for [piece] aimed at [audience]: 4 plain, 4 curiosity-driven, 4 playful. Then pick the two strongest and say why in one line each.
From the library: Professional Email Prompt, Editing and Proofreading Prompt, Headline Writing Prompt and Brand Voice Guide Prompt, or browse all content writing prompts.
The best prompt for thinking and decisions
Devil's advocate
Here is my plan: """[plan]"""
Argue hard against it. Give the three strongest objections, and for each, the evidence that would settle whether it's right.
Pre-mortem
Assume it's one year from now and [project] has failed. List the most likely causes, ranked by probability, and one preventive step for each I could take this month.
Decision matrix
I'm choosing between [A], [B], [C]. My priorities, most important first: [list].
Score each option against each priority in a table (1–5), weight by priority, and name the winner. Flag where the scores are guesses.
Find your blind spots
Here's my situation and my reasoning: """[text]"""
What am I not asking? List the assumptions I haven't examined and the questions that would most change my decision. Don't give a recommendation.
From the library: Structured Decision-Making Prompt and Evidence-Based SWOT Analysis Prompt, or browse all productivity prompts.
The best prompt for learning
Explain it properly
Explain [topic] to someone smart with no background in it. Use one analogy and one worked example. Then name the most common misconception and why people fall for it. End with 3 questions to test my understanding.
Teach me by asking
Teach me [topic] Socratically. Ask me one question at a time, wait for my answer, and adjust difficulty based on how I do. Correct mistakes briefly before moving on.
Seven-day plan
Build a 7-day plan to learn [skill], 20 minutes a day, starting from [my level]. For each day: one task, one resource, and one check that proves I learned it. End goal: I can [observable outcome].
Defining the end goal as something you can demonstrate — not "understand X" but "build Y" or "explain Z without notes" — is what makes learning prompts work.
From the library: Study Guide from Your Notes Prompt and Quiz Generator Prompt, or browse all education prompts.
The best prompt for training and L&D
If you build courses or train people, the strongest prompts spell out six things: the audience and their experience, the learning objective, the real workplace context, the format (course, microlearning, quiz, activity), tone and accessibility, and how understanding will be assessed.
Course or microlearning module
Create a [5-minute microlearning module] on [topic] for [audience + experience level].
Objective: after this, learners can [observable behaviour].
Context: [processes, challenges, real scenarios to reflect].
Include: a short intro, one interactive activity, realistic examples, and a [10]-question knowledge check with feedback on each answer.
Tone: [plain, friendly, accessible]. Flag any safety or compliance content I must verify with an SME.
Quiz with real distractors
Write a 10-question multiple-choice quiz on [topic] for [audience]. Each question gets 3 plausible wrong answers based on common misconceptions, and one line of feedback explaining the right answer.
Branching scenario
Write a branching scenario where a [role] faces [situation]. Give 3 decision points, each with 2–3 choices, realistic consequences, and feedback on what a strong choice looks like.
Adapt for every level
Adapt this content for beginner, intermediate and advanced learners: """[content]""" Then write a 5-question placement check that tells each learner which version to start with.
Reflective coach
Act as a coach helping me improve at [skill]. Ask one reflective question at a time. Don't give me answers — help me arrive at 2–3 practical actions I'll try this week.
Analyse learning data (without fooling yourself)
Here is anonymised LMS data: """[data]""" Identify significant patterns and changes. Separate what the data shows from your assumptions, suggest explanations I could test, and flag where correlation could be mistaken for causation.
Other high-value L&D prompts worth templating: course descriptions with learning objectives, search tags and metadata for your LMS, a 150-character search snippet, a blended-learning strategy under time and budget limits, and an impact framework with baselines plus leading and lagging indicators. Rule of thumb: AI writes the first draft, a subject-matter expert signs it off, and nothing reaches learners unreviewed. Anonymise employee data first.
From the library: Single-Lesson Plan Prompt and Quiz Generator Prompt.
The best prompt for research
Research question: [specific question].
Scope: [date range, geography, definitions].
For each finding give: the claim, the source, how credible the source is, and the evidence for and against.
Separate what sources say from your own inference.
End with a 3-sentence answer, the open questions, and a source list. If evidence is insufficient, say so.
The two rules that matter most: never ask for "everything about" a topic, and always separate what a source actually says from what the model concludes. Where accuracy matters, paste the source text instead of asking the model to recall facts from memory.
From the library: Research Paper and Report Summary Prompt, Source-Bound Literature Review Prompt and Desk Market Research Brief Prompt, or browse all research prompts.
The best prompt for coding
Bug: [what happens] vs [what should happen].
Error: """[stack trace]"""
Code: """[relevant files]"""
Environment: [language, versions, framework].
Diagnose before rewriting: likely root cause, alternatives you considered, the smallest safe fix, a test that proves it, and anything you couldn't verify. Don't change the public interface unless you justify it.
Asking for diagnosis first stops the model from rewriting half your codebase to fix a one-line bug. A reproducible problem and a test to confirm the fix beat any amount of clever phrasing.
From the library: Bug Diagnosis Prompt, Behavior-Preserving Refactoring Prompt and Unit Test Writing Prompt, or browse all coding prompts.
The best prompt for marketing and content
Repurpose one piece into many
Source: """[article/transcript]"""
Extract the core argument, the evidence and the best examples. Turn them into: a LinkedIn post, 3 X posts, a newsletter intro and a 60-second video script. Each asset gets its own audience and hook. Don't add claims that aren't in the source.
Email sequence
Product: [what it is]. Audience: [who]. Goal: [action].
Top objections: [list].
Write a 5-email sequence. For each: the objective, 2 subject lines, body, CTA, and which objection it handles. No invented testimonials, results, prices or fake urgency.
The rule across every marketing prompt that ranks: give real audience detail and your actual brand or policy text, because the model can only guess at standards you don't provide.
From the library: Email Sequence Prompt, Ad Copy Prompt and Social Media Content Calendar Prompt, or browse all marketing prompts.
The best prompt for content creators: a 10-step workflow
Prompts for creators work best as a sequence rather than a pile. Here is the full chain, run in order for each piece: plan, hook, draft, voice, proof, platform, objections, CTA.
- Idea generation. "Give me 10 content ideas for [audience] built around their real pain points: [list]. For each: the angle, the best format, and a hook." Ideas tied to a pain point beat generic topics.
- Hook generator. "Write 15–20 opening lines for [topic]. Conversational, curiosity-driven, no template phrases like 'In today's world'."
- Voice lock. "Interview me about how I write: tone, pacing, phrases I use. Then rewrite this draft in that voice, three ways." Re-run it every month or so, because your voice drifts.
- Simplification. "Explain [complex idea] with no jargon and one relatable analogy. Keep it accurate."
- Proof and personality. "Add one short personal story, two concrete numbers, and one honest limitation to this draft. Human, not promotional."
- Story extraction. "Turn this experience into a story: setup, turning point, lesson. Add specific details and one line of dialogue, then connect it to a broader principle."
- Controversial take. "Give me 5 contrarian but defensible angles on [topic] that would spark discussion without being rage bait."
- Platform adapter. "Reshape this piece for [LinkedIn / X / newsletter]: adjust length, line breaks and CTA. Keep the core message."
- Objection handler. "List the 5–7 doubts a reader will have about this. Acknowledge each as fair and answer it honestly."
- CTA constructor. "Replace my vague call to action with three concrete next steps, each doable in about 10 minutes and tied to what the piece delivered."
Keep a small core set you actually use rather than a folder of 500 prompts you never open, and track which outputs need the least editing.
The best prompt for meetings and presentations
Agenda
Meeting: [length], attendees and roles: [list], goal: [decision/outcome].
Write a timed agenda with one owner per item, in plain language.
Rehearse the hard questions
I'm presenting [topic] to [audience] who care about [priorities].
List the 10 hardest questions they'll ask. For the top 3, add the likely follow-up. Then draft a 30-second answer for each using Point, Reason, Example, Point.
Meeting notes → follow-up
Notes: """[notes]"""
Write a follow-up email under 200 words: decisions made, owners, deadlines, open questions. Neutral tone — flag anything that could read as demanding.
From the library: Meeting Notes to Decisions and Actions Prompt and Weekly Planning Prompt.
The best prompt for managers, sales, HR and everyday work
These templates use the RTFD pattern (Role, Task, Format, Details) and cover the jobs professionals ask AI for most.
Executive summary
Summarise this report for a busy executive: """[report]""" Give the main point in one sentence, the three decisions required, and anything that looks wrong or missing. Max 150 words.
Decision analysis
Compare [option A] and [option B] for [goal]. Think through it step by step: costs, risks, best case, worst case. Then give a recommendation in a table with the reasoning.
Prioritise your week
Here are my tasks: [list]. Sort them into do now, schedule, delegate and drop. Then build a time-blocked plan for [day], with deep work in the morning.
Hard management conversation
I manage [person/role] who has [missed three deadlines / disengaged]. Help me plan a feedback conversation: opening line, specific examples to raise, questions to understand the cause, and an agreed next step. Tone: direct but supportive.
Sales follow-up
Write a follow-up to [prospect] after our demo on [date]. They cared about [priorities] and raised [objection]. Under 120 words, one clear next step, no pressure tactics.
HR: bias-checked job description
Write a job description for [role] at [company]. Then review it for gendered or exclusionary language and requirements that aren't truly essential, and suggest neutral replacements.
Onboarding plan
Build a 30-60-90 day onboarding plan for a new [role]: goals, key people to meet, deliverables, and how we'll judge success at each stage.
IT troubleshooting
My [laptop / Teams / OneDrive sync] is [symptom] on [OS + version]. I've already tried [steps]. Walk me through the most likely fixes, one at a time, starting with the safest.
Two extra rules for work prompts: two words of audience ("for engineers", "for the board") change the output dramatically, and anything people-related from HR or management needs a human check for bias before it's used.
From the library: Job Description Prompt and OKR Drafting and Review Prompt, or browse all business prompts.
The best prompt for personal life
Some of the most-loved prompts on Reddit's r/ChatGPT aren't about work at all. The top-voted answer in one long-running thread was a prompt asking the AI to help the user work out their own personal philosophy through questions and answers. The pattern generalises: when the problem is fuzzy, ask the model to interview you rather than advise you.
Help me figure out [decision / what I want from X] by asking me questions one at a time. Don't give advice until I say "summarise". Then reflect back what you heard, and the tensions you noticed.
Five add-ons that upgrade any prompt
Attach these to the end of almost any prompt above:
- Ask me questions first. "Before answering, ask up to 5 questions that would most improve your answer."
- What's missing? "Tell me what information would make this better — then answer anyway with what you have."
- Critique, then rewrite. "Review your answer like a harsh editor, list the weaknesses, then fix them."
- Three versions. "Give me a safe, a bold and an unexpected version."
- Check yourself. "List the factual claims you made with a confidence level for each, and flag what I should verify from a primary source."
Advanced techniques (when the basics aren't enough)
Most people never need these. Use them to solve a specific problem, not by default.
- Step-by-step reasoning. For logic, maths or multi-factor analysis, ask the model to reason through the problem before answering — or better, spell out the stages you want it to work through. Many models now have a built-in extended thinking mode; switch it on for hard problems.
- Prompt chaining. Break a big job into stages — summarise, then critique the summary, then revise — with each output feeding the next. Slower, but far more reliable than one giant prompt.
- Prefilling. If you're on the API, start the model's response for it (for example with
{) to force JSON or kill preambles. In chat, tell it exactly how to begin. (On newer Claude models the API no longer accepts a prefilled last turn, so use structured outputs or explicit format instructions there.) - Delimiters and structure. Wrap pasted material in quotes or tags so instructions and content don't blur. Clear headings and whitespace now do much of what heavy XML tagging used to.
- Put the important parts at the edges. In long inputs, the most critical instructions belong at the start or the end, not buried in the middle.
Two of these have their own guides: prompt chaining and few-shot prompting.
Troubleshooting: if the answer is bad, fix the prompt
| Symptom | Fix |
|---|---|
| Generic, bland answer | Add specifics: audience, numbers, constraints, an example |
| Off-target answer | State the goal and why you're asking |
| Inconsistent format | Paste an example of the exact output you want |
| Falls apart on complex tasks | Split into a chain of smaller prompts |
| Rambling intro | Ask for the answer directly, or tell it how to start |
| Made-up facts | Supply source text and allow "I don't know" |
| Suggests instead of doing | Ask for the change itself, not ideas about it |
The seven most common prompting mistakes
- Asking one vague question and judging the whole tool by the answer.
- Pasting text with no instruction about what to do with it.
- Not saying who the output is for.
- Cramming several tasks into one prompt.
- Accepting the first draft — the second pass is almost always better.
- Mistaking confident wording for accuracy.
- Over-engineering: stacking every technique at once instead of the shortest prompt that reliably works.
And one non-negotiable: don't paste confidential client, financial or personal data unless your organisation's policy allows it.
Does this work on ChatGPT, Claude and Gemini?
Yes. The principles — clarity, context, constraints, format, examples — hold across every major model. Differences are at the margins: Claude responds especially well to clearly labelled sections and explicit instructions; newer models of every family follow instructions more literally than older ones, so say exactly what you want rather than hoping they'll infer it. When a model gets something wrong, change the prompt before you change the model.
Model-specific notes and starter prompts: ChatGPT, Claude and Gemini.
People also ask: Claude, OpenAI and prompt best practices
The searches that sit next to "the best prompt for" are mostly about specific models and official guides. Here are the answers.
Best prompts for Claude and Claude prompting best practices
Anthropic's own documentation says to treat Claude like a brilliant new employee who has none of your context. Its test: if a colleague with minimal context would be confused by your prompt, Claude will be too. The core practices:
- Be explicit and ask for the extra mile. "Create an analytics dashboard" gets a basic one. "Create an analytics dashboard. Include as many relevant features and interactions as possible. Go beyond the basics" gets a full one.
- Give the reason behind rules. "Never use ellipses" works less well than "This will be read aloud by a text-to-speech engine, so never use ellipses — it can't pronounce them."
- Use 3–5 examples that are relevant, varied, and wrapped in
<example>tags. - Structure with XML tags like
<instructions>,<context>and<input>when a prompt mixes several kinds of content. - Long documents go first. Put 20k+ token inputs at the top and the question at the end; Anthropic reports up to 30% better answers on complex multi-document tasks. Ask Claude to pull out relevant quotes before answering.
- Say what to do, not what to avoid. "Write in flowing prose paragraphs" beats "Don't use markdown".
- Ask for action, not suggestions. "Can you suggest changes?" gets suggestions. "Change this function to improve performance" gets edits.
- Don't over-shout. On recent models, "CRITICAL: You MUST use this tool" can cause over-triggering. "Use this tool when…" works better.
For the full walkthrough with a checklist, see Claude prompting best practices.
Claude prompt examples
<documents>
<document index="1">
<source>annual_report.pdf</source>
<document_content>[paste]</document_content>
</document>
</documents>
<instructions>
First quote the passages relevant to revenue growth, then summarise them in 5 bullets for a CFO.
If the documents don't contain the answer, say so.
</instructions>
Write in clear, flowing prose using complete paragraphs. Use lists only for truly discrete items.
Only make changes that are directly requested or clearly necessary. Keep the solution simple and focused.
Develop several competing hypotheses, track your confidence in each as you research, and critique your own approach before giving a final answer.
Anthropic prompt engineering best practices (the short version)
Anthropic's 2026 guide comes down to: clear communication first, advanced techniques only to fix a specific problem, and the shortest prompt that reliably works. Elaborate role-play and heavy XML are now less necessary than they were. Thinking is now built into recent Claude models (adaptive thinking controlled by an effort setting), so ask for thoroughness in general terms instead of scripting every step. One change for API users: prefilling the assistant's last turn is no longer supported on newer models, so use structured outputs or explicit format instructions instead.
Claude prompt generator
Yes, there is an official one. The Claude Console has a prompt generator: describe your task and it writes a ready-to-use prompt template with variables, built on Anthropic's own best practices. It's designed to solve the blank-page problem, and the more detail you give it about the task and output format, the better the result. There's also a prompt improver, which takes an existing prompt (plus optional feedback and example outputs) and rewrites it with step-by-step reasoning instructions and richer examples. It can also adapt prompts written for other models to Claude. Its prompts produce more thorough but slower answers, so for speed- or cost-sensitive uses keep prompts simpler. No Console? Ask Claude directly: "Write a prompt template for [task], with {{variables}} for anything that changes between uses."
Claude prompt guide PDF
Anthropic doesn't publish one official PDF. The canonical guides are the Prompting best practices page in the Claude Platform docs and the "Best practices for prompt engineering" article on claude.com. Both pages can be saved as a PDF from your browser (Print → Save as PDF). This article also works as a one-page cheat sheet.
OpenAI prompting best practices
OpenAI's official guidance overlaps almost entirely with Anthropic's:
- Use the latest model; newer models are easier to prompt.
- Put instructions at the start and separate them from context with
###or""". - Be specific about context, outcome, length, format and style. "Write a poem about OpenAI" becomes a short inspiring poem about a specific launch, in a named style.
- Show the output format with examples, so results are consistent and easy to parse.
- Start zero-shot, then few-shot, then fine-tune only if needed.
- Cut fluffy descriptions ("fairly short" → "3–5 sentences").
- Say what to do instead of only what not to do.
- For code, use leading words (like starting with
import) to nudge the pattern. - For factual extraction, use temperature 0.
Reasoning models (the o-series and newer) need less step-by-step instruction than GPT models: give the goal and the constraints, and let them reason.
For the full walkthrough, including reasoning models and settings, see OpenAI prompting best practices.
Prompt best practices: the universal checklist
Whatever the model, run your prompt past these before you hit enter:
- One clear task with an action verb
- The context it can't guess, including who it's for
- The reason behind any rule
- Source material in delimiters (quotes or tags)
- Constraints: length, tone, must-include, must-avoid
- Output format stated, or shown with an example
- Permission to say "I don't know" or "not in the source"
- "Ask me questions first" when stakes are high
- A review pass: critique, then rewrite
- Facts, numbers, legal and medical points verified by you
The bigger point: problems matter more than prompts
MIT Sloan's guide makes an argument worth ending on. As AI improves, wording tricks matter less, and the durable skill is defining the problem itself — its focus, scope and boundaries. If you can't say clearly what you want, no prompt will rescue it. If you can, almost any reasonable prompt will work.
That's the real answer to "what's the best prompt for…": the best prompt is a clear thought, written down with enough context that someone smart — human or machine — could act on it without coming back to ask.
FAQ
What is the single best prompt?
There isn't one. The most reliable pattern is task + context + constraints + format, with "ask me questions first" as the strongest add-on.
How long should a prompt be?
As long as the task needs. Two sentences can be enough for a simple request; professional work usually benefits from four to eight lines of context plus any source material.
Do I still need to write good prompts with newer models?
Yes. Newer models cope better with vague requests, but a clear brief still gets a more specific answer in fewer rounds.
Should I start prompts with "Act as…"?
Only when a specific perspective genuinely changes the answer. With current models, stating the lens you want usually beats an elaborate persona.
What's the best prompt for getting accurate facts?
Give the model the source text, ask it to cite where each claim comes from, and explicitly allow it to say the information isn't there.
Can I copy prompts from lists like this one?
Yes — as templates. Replace every bracket with your real context. The context is what makes the prompt work.
Sources reviewed
- Best practices for prompt engineering — Claude
- Prompting best practices — Claude Platform Docs
- Prompt generator — Claude Platform Docs
- Best ChatGPT Prompts: 20 That Actually Work — The Oxford AI School
- 10 Best AI Prompts for Work, Research, and Marketing — Zemith
- Best AI Prompts for Learning & Training — 5app
- Effective Prompts for AI: The Essentials — MIT Sloan
- The First 10 Prompts You Should Save — R Dilip Kumar, Medium
- 150+ Best AI Prompts for Professionals — Talaera
- The Best ChatGPT Prompts for 2026 — Coursiv
- Best practices for prompt engineering with the OpenAI API — OpenAI
- Which prompt has helped you level up? — r/ChatGPT
- Google AI Overview for "the best prompt for" (November 2026)
Prompts that put this into practice
Professional Email Prompt
Drafts a single work email that leads with the ask, suits the relationship, and leaves bracketed blanks for any detail you did not provide.
# Role
You are helping me write one professional email. Write it as I would send it: from me, in the first person, ready to paste.
# Situation
- Who I am writi…Structured Decision-Making Prompt
A two-round prompt: the model questions you first, then weighs your options against your criteria and argues against the one you already favor.
# Role
You are a thinking partner helping me make a decision. You are not here to reassure me. Your value is in structure, in noticing what I left out, and in a…Bug Diagnosis Prompt
Give the model the error, the code and what you expected. It ranks likely causes by evidence, tells you how to confirm each, and proposes a minimal fix.
# Role
You are an experienced engineer helping me find the cause of a bug. Diagnose first and fix second. Do not rewrite code that is not part of the problem.…Research Paper and Report Summary Prompt
Summarizes a paper or report for a named reader: bottom line, method, key findings with exact figures, limits of the evidence, and what it means for them.
# Role
You are a careful analyst who summarizes research for people who will not read the original. Accuracy to the document matters more than fluency.
# What…Keep reading
Guide
How to Write a Good AI Prompt
The five parts of a complete prompt (goal, context, task, constraints, output format), with a worked rewrite and a pre-send checklist.
Guide
What Is Prompt Engineering? Core Techniques Explained
What prompt engineering is, the techniques the major model vendors agree on, the working loop behind them, and what prompting cannot fix.
Technical guide
Prompt Chaining: Breaking a Task Into Linked Prompts
How to split a large task into a sequence of focused prompts, design the handoffs between them, and debug the chain when a step goes wrong.
Technical guide
Few-Shot Prompting: How to Use Examples in a Prompt
How to include worked examples in a prompt so the model follows a format, label set or style, and how to choose examples that generalize.