Quick answer: How do I write good prompts for AI?
- Be specific — task, audience, goal, constraints.
- Give context — documents, data, background.
- Show examples — one or two of what 'good' looks like.
- Specify format — length, structure, tone.
- Iterate — critique the output and refine.
Key takeaways
- Most bad outputs come from missing context, not a missing magic phrase.
- Examples are the fastest way to communicate quality and style.
- Breaking big tasks into steps improves reliability.
- Ask for sources and uncertainty when facts matter — then verify.
- Save prompts that work as templates for your team.
There's no secret phrase that unlocks great AI output. The best prompts read like a good brief to a smart new colleague who knows nothing about your situation. Anthropic, OpenAI and Google all publish prompting guides, and they converge on the same handful of principles123. Learn those, use a template, and keep the examples below as a starting library.

Seven principles

- State the task clearly — what you want, in one sentence.
- Give context — background, audience, purpose, constraints.
- Provide material — paste the document, data or notes to work from.
- Show an example of good output (few-shot prompting).
- Specify the format — length, structure, tone, language.
- Break big tasks into steps — or ask the model to plan first.
- Iterate — tell it what to change and why.
A reusable template

Role and goal
"You're helping a [role] to [goal] for [audience]."
Context and material
"Here's the background: … Use only this material: …"
Task and constraints
"Write/analyse/compare … Keep it under … Avoid …"
Format and check
"Return as a table with columns … If unsure, say so and list what you'd need."
50 examples
Writing and communication (1–10)
- "Rewrite this email to be clear and friendly in under 120 words. Keep the deadline and the ask."
- "Turn these meeting notes into decisions, owners and due dates in a table."
- "Draft three subject lines for this newsletter, each under 50 characters, for busy founders."
- "Explain this policy to a new employee in plain language with three examples."
- "Edit this paragraph for clarity; show changes and explain the two most important ones."
- "Write a polite reminder to a client about an overdue invoice of ₹45,000, firm but warm."
- "Summarise this 20-page report in five bullet points for a CEO, then three risks."
- "Translate this message into Hindi for a WhatsApp audience; keep it conversational."
- "Give me three ways to say no to this request while keeping the relationship strong."
- "Turn this outline into a 600-word LinkedIn post with a strong first line."
Analysis and research (11–20)
- "From this CSV, find the top three reasons for refunds and show counts."
- "Compare these two vendor proposals in a table: cost, timeline, risks, gaps."
- "List assumptions in this business plan and rate how risky each is."
- "What questions should I ask before deciding between these options? Group them."
- "Explain this chart to a non-technical audience in four sentences."
- "Identify contradictions between these two documents and quote the lines."
- "Create a pros-and-cons analysis of launching in Pune first versus Bengaluru."
- "Suggest five hypotheses for why sign-ups dropped last week, and how to test each."
- "Summarise customer reviews into themes with example quotes and frequency."
- "Answer only from the attached document; if the answer isn't there, say so."
Product management (21–28)
- "Write a one-page PRD for this feature: problem, goals, non-goals, metrics, risks."
- "Generate user stories with acceptance criteria for this flow."
- "Score these ten ideas with RICE; show your assumptions."
- "Draft ten interview questions about how people last solved this problem."
- "Turn this interview transcript into insights, quotes and opportunities."
- "Suggest guardrail metrics for an experiment that increases notifications."
- "Write release notes for these changes for end users, not engineers."
- "Play a sceptical CFO and challenge this roadmap; list your top five objections."
Design and UX (29–34)
- "Critique this onboarding flow against Hick's law and the peak–end rule."
- "Write microcopy for an empty state, an error and a success message for this screen."
- "Suggest three alternative layouts for this settings page, with trade-offs."
- "List accessibility issues in this screen description against WCAG 2.2 AA."
- "Create a usability test script with five tasks for this prototype."
- "Write alt text for these five product images."
Coding (35–42)
- "Explain what this function does, line by line, for a junior developer."
- "Write unit tests for this function covering edge cases; list the cases first."
- "Find bugs and security issues in this code; rank by severity."
- "Refactor this component for readability without changing behaviour."
- "Write a SQL query for monthly active users by city from this schema."
- "Convert this API response into a TypeScript type."
- "Suggest how to make this screen work offline; outline the approach first."
- "Write a regex for Indian mobile numbers and explain each part."
Marketing and growth (43–47)
- "Write five app store screenshot captions for this app, each under six words."
- "Draft a referral message users can share on WhatsApp, under 40 words."
- "Create a content calendar of 12 blog topics for this audience, with search intent."
- "Write three ad variants for this offer for first-time investors; avoid hype."
- "Rewrite this landing page headline five ways for different motivations."
Learning and thinking (48–50)
- "Teach me this concept with an analogy, then quiz me with three questions."
- "Make a 30-day learning plan for SQL for a product manager, 30 minutes a day."
- "Steelman the opposite view of my argument, then tell me where I'm weakest."
Make outputs trustworthy

- Provide source material and ask the model to stay within it
- Ask for uncertainty: "If you're not sure, say so"
- Request citations or quotes for factual claims — then check them
- Review numbers and calculations independently
- Keep confidential and personal data out unless your tool and policy allow it
Choosing a tool? See ChatGPT vs Claude vs Gemini. For product work, see AI tools for product managers.
Key terms, defined
Prompt — instructions and context given to an AI. Few-shot prompting — including examples in the prompt. Context — background information the model needs. Hallucination — a confident but false output. Template — a reusable prompt structure.
Frequently asked questions
What is prompt engineering?
The practice of writing instructions and context for AI models so they produce useful, accurate results — including how you frame the task, what information you include, examples, constraints and output format.
What makes a good prompt?
A clear task, relevant context, the intended audience and goal, constraints, an example of good output, and a specified format. Treat the AI like a smart colleague who knows nothing about your situation.
Is prompt engineering still important with better models?
Yes, though less about tricks. Better models follow clear instructions well, so the skill shifts to giving good context, defining success and evaluating results.
What is few-shot prompting?
Including a few examples of input and desired output in the prompt so the model can infer the pattern, style or format you want.
How do I stop AI from making things up?
Provide source material and ask it to answer only from that, ask it to say when it doesn't know, request citations, and verify important facts yourself.
Do prompts work the same in ChatGPT, Claude and Gemini?
The core principles transfer across models. Each vendor publishes its own prompting guide with model-specific tips worth reading.
Sources
- Anthropic — Prompt engineering overview
- OpenAI — Prompt engineering guide
- Google — Gemini API prompt design strategies
- Checked October 23, 2026. Figures that change — fees, salaries, prices — are reviewed every six months; if something is out of date, tell us.
Where to go from here
- ChatGPT vs Claude vs Gemini — which assistant for which work
- AI tools for product managers — prompts in a PM workflow
- AI & vibe coding200 AI skills for ChatGPT, Claude and Gemini, sorted by job200 free copy-paste AI skills for ChatGPT, Claude and Gemini across 16 jobs, each with the problem it solves, an output preview and the exact install text.
- AI & vibe coding12 copy-paste AI skills for customer support teams, for ChatGPT, Claude and Gemini12 free copy-paste AI skills for customer support teams — empathetic reply writer and more — each with an output preview and the exact text to paste.
- AI & vibe coding10 copy-paste AI skills for legal and compliance teams, for ChatGPT, Claude and Gemini10 free copy-paste AI skills for legal and compliance teams — contract risk summary and more — each with an output preview and the exact text to paste.
- AI & vibe coding8 copy-paste AI skills for writers and communications teams, for ChatGPT, Claude and Gemini8 free copy-paste AI skills for writers and communications teams — executive summary and more — each with an output preview and the exact text to paste.
- AI & vibe coding20 copy-paste AI skills for software engineers, for ChatGPT, Claude and Gemini20 free copy-paste AI skills for software engineers — stack trace debugger and more — each with an output preview and the exact text to paste.
- AI & vibe coding14 copy-paste AI skills for product managers, for ChatGPT, Claude and Gemini14 free copy-paste AI skills for product managers — one-page PRD and user story writer and more — each with an output preview and the exact text to paste.
Get the ideas, not the noise.
Sign up with Google and we’ll send you short UX psychology tips by email — why people tap, stall and leave, and what to do about it. Unsubscribe anytime. Prefer something to keep? Get the free Laws of UX guide as a PDF.
Make your AI feature something users trust.
A behavioral UX audit of your app or SaaS product: why users hesitate, stall and leave, and a prioritized fix list. Fixed price, 2–4 weeks.





