The Claude prompt library

How to use this library

This library removes the blank-page problem. Each recipe is a tested prompt template you copy, paste, and customize. The workflow is simple:

Find the recipe that matches your task using the categories below (or your editor's search).
Copy the fenced template block.
Replace every [BRACKETED] placeholder with your own details. Delete any line that doesn't apply.
Paste the attachment, document, or data the prompt refers to (Claude reads PDFs, images, spreadsheets, and screenshots).
Run, then refine. If the first answer isn't right, tell Claude what to change. Conversation beats a perfect first prompt.

The pattern behind every recipe

Strong prompts share five ingredients. Every template here follows this shape:

Ingredient	What it does	Example
Role	Sets the perspective and expertise	"You are a financial analyst…"
Context	Gives the background and source material	"Here is last quarter's report…"
Task	States the single, clear job	"Summarize the three biggest risks…"
Format	Describes the shape of the output	"…as a 5-row table."
Constraints	Sets the limits and rules	"Use only the attached source. Keep it under 200 words."

You don't need all five every time, but a prompt that's vague usually skipped one. When an answer disappoints, ask which ingredient was missing.

Which model?

Most recipes run well on Sonnet 4.6 (claude-sonnet-4-6), the everyday default. Reach for Opus 4.8 (claude-opus-4-8) on the hardest reasoning, analysis, and coding tasks. Use Haiku 4.5 (claude-haiku-4-5) for fast, high-volume, lightweight jobs like quick classification or short rewrites.

Summarize

1. Executive summary (TL;DR)

When to use: You have a long document and need the gist for a busy decision-maker.

You are a chief of staff briefing a busy executive.
Summarize the attached [DOCUMENT TYPE] for [AUDIENCE].
Give me:
1. A one-sentence TL;DR.
2. The 3–5 most important points as bullets.
3. Any decision or action the reader must take.
Use only the attached source. Keep the whole thing under [WORD COUNT] words.

Filled example: "You are a chief of staff briefing a busy executive. Summarize the attached vendor contract for our COO. Give me a one-sentence TL;DR, the 3–5 most important points as bullets, and any decision the reader must take. Use only the attached source. Keep it under 150 words."

2. Layered summary (short → long)

When to use: Different readers need different depth from the same material.

Summarize the attached [DOCUMENT] at three levels of detail:
- Headline: one sentence.
- Standard: one paragraph.
- Detailed: one page with section headers.
Keep the facts identical across all three; only the depth changes.

Filled example: "Summarize the attached research paper at three levels of detail: a one-sentence headline, a one-paragraph standard summary, and a one-page detailed version with section headers."

3. Summarize a long thread or chat

When to use: A long email chain or chat log and you need to catch up fast.

Below is a [EMAIL THREAD / CHAT LOG]. Summarize it as:
- What is being decided or discussed.
- Each participant's position.
- Open questions still unresolved.
- Who owes what next, with any dates mentioned.
[PASTE THREAD]

Filled example: "Below is an email thread. Summarize what's being decided, each participant's position, open questions, and who owes what next with any dates mentioned. [pasted thread]"

4. Notes → action items

When to use: Turn messy notes into a clean to-do list.

Turn the messy notes below into a clean action list.
For each item give: the task, the owner (if named), and the due date (if named).
List anything ambiguous under a separate "Needs clarification" heading.
Notes:
[PASTE NOTES]

Filled example: "Turn the messy notes below into a clean action list with task, owner, and due date for each, plus a 'Needs clarification' section. [pasted notes]"

Draft & Write

5. First draft from a brief

When to use: You know what you want to say but need a starting structure.

You are a [ROLE, e.g. marketing writer].
Write a draft [DOCUMENT TYPE] about [TOPIC] for [AUDIENCE].
Goal: [WHAT IT SHOULD ACHIEVE].
Must cover: [KEY POINTS].
Tone: [TONE]. Length: about [LENGTH].
End with a clear [CALL TO ACTION / NEXT STEP].

Filled example: "You are a marketing writer. Write a draft blog post about our new expense-tracking feature for small-business owners. Goal: drive sign-ups. Must cover: time saved, automatic categorization, mobile access. Tone: friendly and practical. Length: about 500 words. End with a clear call to action to start a free trial."

6. Outline before drafting

When to use: A big piece you want to structure before writing a word.

Create a detailed outline for a [DOCUMENT TYPE] on [TOPIC] for [AUDIENCE].
Use nested headings and a one-line note under each on what it should cover.
Don't write the full text yet — outline only.
Target length when written: [LENGTH].

Filled example: "Create a detailed outline for a white paper on supply-chain resilience for operations leaders. Use nested headings with a one-line note under each. Outline only. Target length: 3,000 words."

7. Talking points / speaker notes

When to use: You're presenting and need crisp points, not paragraphs.

I'm presenting [TOPIC] to [AUDIENCE] for [DURATION].
Write speaker talking points as short bullets I can glance at.
Cover: [KEY MESSAGES]. Lead with the most important point.
Add one memorable opener and one strong closing line.

Filled example: "I'm presenting our Q3 roadmap to the sales team for 10 minutes. Write speaker talking points as short bullets. Cover: three new features, timeline, what to tell customers. Add a memorable opener and a strong closing line."

8. Policy or process document

When to use: You need a clear, structured internal document from scratch.

You are a [ROLE]. Draft a [POLICY / PROCESS / SOP] for [TOPIC].
Audience: [WHO MUST FOLLOW IT].
Include: purpose, scope, step-by-step procedure, roles & responsibilities,
and exceptions. Use numbered steps and plain language.
Flag anything that needs a human decision as "[DECISION NEEDED]".

Filled example: "You are an HR operations lead. Draft an SOP for onboarding a new remote employee. Audience: hiring managers. Include purpose, scope, step-by-step procedure, roles, and exceptions. Use numbered steps and flag decisions as [DECISION NEEDED]."

9. Few-shot: match my style

When to use: You have examples of the voice you want and need more in the same style. (Power recipe)

Here are 2 examples of the style I want. Study the tone, sentence length,
and structure, then write a new one for [NEW TOPIC] that matches.

Example 1:
[PASTE EXAMPLE 1]

Example 2:
[PASTE EXAMPLE 2]

Now write the new piece. Match the style, not the content.

Filled example: "Here are 2 examples of the product announcements we send. Study the tone and structure, then write a new one for our calendar-sync feature. Match the style, not the content. [pasted examples]"

Rewrite & Tone

10. Adjust the tone

When to use: The content is right but the voice is off.

Rewrite the text below to be [TARGET TONE, e.g. warmer / more formal /
more direct]. Keep the meaning and all facts identical.
Don't add new information. Return only the rewritten text.
Text:
[PASTE TEXT]

Filled example: "Rewrite the text below to be warmer and less corporate. Keep the meaning and all facts identical. Return only the rewritten text. [pasted text]"

11. Make it shorter (tighten)

When to use: Something is too long or too wordy.

Tighten the text below to about [TARGET LENGTH] without losing any
key point. Cut filler, redundancy, and hedging. Keep the original tone.
Text:
[PASTE TEXT]

Filled example: "Tighten the text below to about half its length without losing any key point. Cut filler and hedging. Keep the tone. [pasted text]"

12. Make it clearer (plain language)

When to use: Jargon-heavy or convoluted text that readers struggle with.

Rewrite the text below in plain language a [AUDIENCE, e.g. general reader]
can understand on the first pass. Replace jargon with everyday words,
break long sentences up, and explain any term that must stay.
Text:
[PASTE TEXT]

Filled example: "Rewrite the text below in plain language a new customer can understand on the first pass. Replace jargon, break up long sentences, explain any term that must stay. [pasted text]"

13. Proofread and fix

When to use: Final polish for grammar, spelling, and consistency.

Proofread the text below. Fix grammar, spelling, punctuation, and
inconsistent style. Don't change the meaning or voice.
Return: (1) the corrected text, then (2) a short list of what you changed.
Text:
[PASTE TEXT]

Filled example: "Proofread the text below. Fix grammar, spelling, punctuation, and inconsistent style without changing the voice. Return the corrected text, then a short list of changes. [pasted text]"

14. Reframe for a different audience

When to use: You wrote for one group and now need it for another.

The text below was written for [ORIGINAL AUDIENCE].
Rewrite it for [NEW AUDIENCE], whose priorities are [WHAT THEY CARE ABOUT]
and whose knowledge level is [LEVEL]. Adjust examples and emphasis,
keep the core message true.
Text:
[PASTE TEXT]

Filled example: "The text below was written for engineers. Rewrite it for executives, who care about cost and risk and aren't technical. Adjust examples and emphasis, keep the core message true. [pasted text]"

Extract & Structure

15. Extract to a table

When to use: Pull scattered details into rows and columns.

Read the attached [SOURCE] and extract every [ITEM TYPE] into a table.
Columns: [COLUMN 1] | [COLUMN 2] | [COLUMN 3].
If a value isn't stated in the source, write "Not stated" — do not guess.
Use only the attached source.

Filled example: "Read the attached invoices and extract every line item into a table with columns Vendor | Item | Amount | Due date. If a value isn't stated, write 'Not stated' — do not guess. Use only the attached source."

16. Extract to JSON

When to use: You need structured data to feed another system. (Power recipe)

Extract the following fields from the text below and return ONLY valid JSON,
no commentary. Use this exact schema:
{
  "[field1]": "string",
  "[field2]": "number or null",
  "[field3]": ["array", "of", "strings"]
}
If a field is missing in the source, use null. Use only the source provided.
Text:
[PASTE TEXT]

Filled example: "Extract these fields and return ONLY valid JSON: {"company": string, "contract_value": number or null, "renewal_date": string or null, "parties": [strings]}. If missing, use null. Use only the source. [pasted contract]"

17. Categorize / classify

When to use: Sort a list of items into defined buckets.

Classify each item below into exactly one of these categories:
[CATEGORY A], [CATEGORY B], [CATEGORY C], or "Other".
Return a table: Item | Category | One-line reason.
Items:
[PASTE LIST]

Filled example: "Classify each support ticket below into exactly one of: Billing, Bug, Feature request, or Other. Return a table with Item | Category | One-line reason. [pasted tickets]"

18. Build a comparison matrix

When to use: Turn prose about several options into a side-by-side grid.

From the source(s) below, build a comparison table.
Rows = [OPTIONS]. Columns = [CRITERIA].
Fill each cell from the source only; write "Not stated" where silent.
Add a final row summarizing the standout strength of each option.
Sources:
[PASTE / ATTACH]

Filled example: "From the attached spec sheets, build a comparison table. Rows = the three laptops. Columns = price, weight, battery life, ports. Write 'Not stated' where silent. Add a final row on each one's standout strength."

19. Tag and prioritize a backlog

When to use: A raw list of tasks or ideas that needs structure and ranking.

For each item below, add: a category tag, an effort estimate (S/M/L),
and an impact estimate (Low/Med/High). Then sort the table by impact,
high to low. Items:
[PASTE LIST]

Filled example: "For each feature idea below, add a category tag, effort (S/M/L), and impact (Low/Med/High). Sort by impact, high to low. [pasted list]"

Analyze & Compare

20. Pros, cons, and recommendation

When to use: You need a balanced read on a single option or proposal.

You are an impartial analyst. Evaluate [SUBJECT] for [GOAL / CONTEXT].
Give: the strongest arguments for, the strongest against, the key risks,
and a clear recommendation with your reasoning.
Be specific and avoid hedging. Base it only on [SOURCE / WHAT I'VE GIVEN].

Filled example: "You are an impartial analyst. Evaluate moving our team to a four-day week for a 30-person support org. Give the strongest arguments for, against, the key risks, and a clear recommendation with reasoning. Be specific."

21. Compare options against criteria

When to use: Choosing between alternatives on factors that matter to you.

Compare [OPTION A], [OPTION B], and [OPTION C] against these criteria,
weighted by importance: [CRITERION 1 (high)], [CRITERION 2 (med)],
[CRITERION 3 (low)].
Show a scored table, then name the best fit for [MY SITUATION] and explain why.

Filled example: "Compare Tool A, Tool B, and Tool C against these weighted criteria: integration depth (high), price (med), learning curve (low). Show a scored table, then name the best fit for a 10-person finance team and explain why."

22. Find the gaps and risks

When to use: Stress-test a plan or document for what's missing.

Review the attached [PLAN / PROPOSAL / DOCUMENT].
Identify: gaps, unstated assumptions, risks, and anything a skeptical
[STAKEHOLDER] would challenge. Rank by severity.
For each, suggest one way to address it. Use only the attached source.

Filled example: "Review the attached launch plan. Identify gaps, unstated assumptions, risks, and what a skeptical CFO would challenge. Rank by severity and suggest one fix for each. Use only the attached source."

23. Reason step by step (chain-of-thought)

When to use: A problem with multiple steps where the reasoning matters. (Power recipe)

Solve the problem below. Think step by step: show your reasoning as
numbered steps before giving the final answer. If an assumption is needed,
state it. End with a line that begins "Answer:".
Problem:
[PASTE PROBLEM]

Filled example: "Solve the problem below. Think step by step, show numbered reasoning, state any assumptions, end with a line beginning 'Answer:'. Problem: If we onboard 12 clients a month at 80% retention, how many active clients will we have after a year starting from zero?"

24. Trend and pattern read

When to use: You have data or a series of events and want the story in it.

Here is [DATA / A SET OF EVENTS]. Identify the main trends and patterns.
For each: describe it, give the supporting evidence from the data,
and note one plausible explanation (labelled as a hypothesis, not fact).
Flag anything that looks like an anomaly. Use only the data provided.
[PASTE / ATTACH DATA]

Filled example: "Here is our monthly churn data for the past two years. Identify the main trends and patterns, with supporting evidence and a labelled hypothesis for each, and flag any anomalies. Use only the data provided. [attached spreadsheet]"

Brainstorm & Decide

25. Generate a wide range of ideas

When to use: You want quantity and variety before narrowing down.

Brainstorm [NUMBER] distinct ideas for [GOAL / PROBLEM].
Push for variety: include safe, ambitious, and unconventional options.
For each, give a one-line description and a one-line "why it could work".
Don't evaluate yet — just generate.

Filled example: "Brainstorm 20 distinct ideas for boosting webinar attendance. Include safe, ambitious, and unconventional options. One-line description and one-line 'why it could work' for each. Don't evaluate yet."

26. Narrow ideas down to a shortlist

When to use: You have many ideas and need to choose.

From the list below, pick the top [NUMBER] for [GOAL], judged on
[CRITERIA, e.g. impact, effort, fit]. Show a short scored table,
explain why each made the cut, and note one you'd revisit later.
List:
[PASTE IDEAS]

Filled example: "From the list below, pick the top 3 for next quarter, judged on impact, effort, and brand fit. Show a scored table, explain each pick, and note one to revisit later. [pasted ideas]"

27. Decision framework (weigh a choice)

When to use: A real decision where you want structure, not a coin flip.

Help me decide: [THE DECISION].
My goal is [GOAL]. My constraints are [CONSTRAINTS].
Lay out the options, the key trade-offs, and a recommended choice.
Then list what would make you change that recommendation.
Ask me up to 3 clarifying questions first if they'd change the answer.

Filled example: "Help me decide whether to build a feature in-house or buy it. Goal: ship within two quarters. Constraints: one engineer free, fixed budget. Lay out options, trade-offs, a recommendation, and what would change it. Ask up to 3 clarifying questions first."

28. Pre-mortem (imagine it failed)

When to use: Surface hidden risks before committing to a plan.

Imagine it's [FUTURE DATE] and [PLAN / PROJECT] has clearly failed.
Working backwards, list the most likely reasons it went wrong, ranked
by probability. For the top 3, suggest a preventive action I can take now.
Context:
[DESCRIBE PLAN]

Filled example: "Imagine it's December and our office relocation has clearly failed. Working backwards, list the most likely reasons, ranked by probability, and suggest a preventive action for the top 3. [plan description]"

Meeting & Prep

29. Build a meeting agenda

When to use: You're running a meeting and want it focused.

Create an agenda for a [DURATION] meeting about [TOPIC] with [ATTENDEES].
Goal of the meeting: [DESIRED OUTCOME].
For each item give a time box, the owner, and the decision or output expected.
End with a "decisions made / next steps" placeholder.

Filled example: "Create an agenda for a 45-minute meeting about the Q3 budget with the leadership team. Goal: approve the final number. Time box, owner, and expected output per item, ending with a decisions/next-steps placeholder."

30. Prep me for a meeting

When to use: You walk in ready, with questions and likely objections in hand.

I have a [MEETING TYPE] with [WHO] about [TOPIC].
My objective is [OBJECTIVE]. Background: [CONTEXT / ATTACHMENT].
Prepare me: likely questions they'll ask, points I should raise,
objections to expect with a response to each, and 3 smart questions I can ask.

Filled example: "I have a renewal call with a key client about pricing. Objective: keep them and avoid a discount. Background attached. Prepare likely questions, points to raise, objections with responses, and 3 smart questions I can ask."

31. Minutes from raw notes

When to use: Turn rough meeting notes into clean, shareable minutes.

Turn the raw notes below into formal meeting minutes.
Include: date, attendees (if listed), key discussion points, decisions made,
and action items with owners and due dates.
Keep it factual — don't invent anything not in the notes.
Notes:
[PASTE NOTES]

Filled example: "Turn the raw notes below into formal minutes with date, attendees, discussion points, decisions, and action items (owner + due date). Don't invent anything not in the notes. [pasted notes]"

Email & Comms

32. Draft an email from intent

When to use: You know what you want to say; you need it written well.

Write an email to [RECIPIENT] about [TOPIC].
Purpose: [WHAT I WANT TO HAPPEN]. Tone: [TONE].
Key points: [POINTS]. Keep it [LENGTH] and end with a clear ask.
Suggest 2 subject lines.

Filled example: "Write an email to a supplier about a late shipment. Purpose: get a firm new delivery date without damaging the relationship. Tone: firm but cordial. Key points: order #4821, promised last Friday, holding up production. Keep it short, end with a clear ask. Suggest 2 subject lines."

33. Reply to an email

When to use: You have an incoming message and want a strong response.

Below is an email I received. Draft a reply that [GOAL].
Tone: [TONE]. Address every question they raised.
Where I need to supply a fact I don't have, leave a [BRACKETED] placeholder.
Incoming email:
[PASTE EMAIL]

Filled example: "Below is an email I received. Draft a reply that declines the request but offers an alternative. Tone: warm and professional. Address every question. Use [bracketed] placeholders for facts I need to add. [pasted email]"

34. Difficult / sensitive message

When to use: Bad news, a complaint, or a delicate situation.

Help me write a [MESSAGE TYPE] to [RECIPIENT] about [SENSITIVE TOPIC].
Goals: [BE CLEAR / STAY RESPECTFUL / PRESERVE RELATIONSHIP / etc.].
Acknowledge their perspective, be honest, and offer a constructive path forward.
Avoid blame and corporate cliché. Give me two versions: direct and softer.

Filled example: "Help me write a message to a teammate about repeatedly missing deadlines. Goals: be clear, stay respectful, keep the working relationship. Acknowledge their perspective, be honest, offer a path forward. Give me a direct version and a softer one."

35. Announcement / update

When to use: Sharing news with a team, customers, or stakeholders.

Write a [CHANNEL, e.g. Slack post / company email] announcing [NEWS].
Audience: [WHO]. They'll mainly care about [WHAT MATTERS TO THEM].
Lead with the headline, explain what's changing and why, say what they
need to do, and where to get help. Tone: [TONE]. Length: [LENGTH].

Filled example: "Write a company email announcing our new expense system going live Monday. Audience: all staff. They care about how to submit expenses. Lead with the headline, explain what's changing and why, what to do, and where to get help. Tone: upbeat and clear. Length: short."

Research & Explain

36. Explain it simply (ELI-level)

When to use: You need to understand a concept fast, at your level.

Explain [CONCEPT] to me as a [AUDIENCE LEVEL, e.g. smart beginner].
Use a plain-language definition, one everyday analogy, and one concrete
example. Then list 3 things people commonly get wrong about it.

Filled example: "Explain how a bond yield curve works to a smart beginner. Plain-language definition, one everyday analogy, one concrete example, then 3 common misconceptions."

37. Brief me on a topic

When to use: You need to get up to speed quickly before a discussion.

Give me a briefing on [TOPIC] for [PURPOSE].
Cover: what it is, why it matters now, the key players or factors,
the main points of debate, and what I should watch next.
Note where your knowledge may be out of date — I'll verify current facts.

Filled example: "Give me a briefing on data residency rules for SaaS in the EU, to prep for a vendor call. Cover what it is, why it matters now, key factors, points of debate, and what to watch. Note where your knowledge may be out of date."

38. Answer only from the source

When to use: You must not let the model add outside or invented information. (Power recipe)

Using ONLY the attached [SOURCE], answer the question below.
Do not use outside knowledge. Quote or cite the part of the source that
supports each point. If the source does not contain the answer, reply
exactly: "The source does not address this." Do not guess.
Question: [YOUR QUESTION]

Filled example: "Using ONLY the attached policy PDF, answer: how many days of notice are required to cancel? Cite the supporting section. If the source doesn't address it, reply exactly: 'The source does not address this.' [attached PDF]"

39. Generate questions to investigate

When to use: You're starting research and want to map the territory.

I'm researching [TOPIC] to [GOAL].
Generate the [NUMBER] most important questions I should answer,
grouped by theme. For each, note why it matters and what kind of source
would answer it. Don't answer them yet.

Filled example: "I'm researching whether to enter the Brazil market, to brief our board. Generate the 15 most important questions, grouped by theme, with why each matters and what source would answer it. Don't answer them yet."

Quality, Critique & Red-team

40. Self-critique and improve

When to use: Push the model to find its own weaknesses and fix them. (Power recipe)

[YOUR TASK AND CONTENT HERE]

Now critique your own answer above. List its weakest points, anything
unclear, unsupported, or missing. Then produce an improved version
that fixes them. Label the two sections "Critique" and "Improved version".

Filled example: "Write a value proposition for our app. … Now critique your own answer: weakest points, anything unclear or unsupported, anything missing. Then produce an improved version. Label them 'Critique' and 'Improved version'."

41. Red-team / poke holes

When to use: You want a tough, skeptical review before going public.

Act as a skeptical [ROLE, e.g. reviewer / customer / opposing counsel].
Attack the [DOCUMENT / ARGUMENT / PLAN] below: find every weak claim,
logical gap, missing evidence, and likely objection.
Be harsh but specific. Then suggest the single most important fix.
[PASTE / ATTACH]

Filled example: "Act as a skeptical investor. Attack the attached pitch: find every weak claim, logical gap, and missing evidence. Be harsh but specific, then name the single most important fix. [attached deck]"

42. Fact-check and flag claims

When to use: You want every factual claim surfaced so you can verify it.

Review the text below and list every factual claim it makes
(numbers, dates, names, statistics, attributions).
For each, mark it: Verifiable in source / Needs external check / Looks risky.
Do not assert any of them as true — I will verify. Flag anything that
reads like it could be fabricated.
Text:
[PASTE TEXT]

Filled example: "Review the draft below and list every factual claim. Mark each as Verifiable in source / Needs external check / Looks risky. Don't assert any as true — I'll verify. [pasted draft]"

43. Check against a rubric / requirements

When to use: Confirm a deliverable meets a defined standard.

Check the attached [DELIVERABLE] against these requirements:
1. [REQUIREMENT 1]
2. [REQUIREMENT 2]
3. [REQUIREMENT 3]
For each, say Met / Partly met / Not met, with the evidence and a fix
if it falls short. End with an overall pass/fail and the top priority.

Filled example: "Check the attached proposal against: (1) under 5 pages, (2) includes pricing, (3) addresses security. Say Met / Partly / Not met with evidence and a fix for each. End with pass/fail and the top priority. [attached proposal]"

Translate & Localize

44. Translate accurately

When to use: Convert text to another language, faithfully.

Translate the text below from [SOURCE LANGUAGE] into [TARGET LANGUAGE].
Preserve meaning, tone, and formatting. Keep names, product names, and
numbers unchanged. Where a phrase has no direct equivalent, choose the
closest natural wording and add a brief [translator note].
Text:
[PASTE TEXT]

Filled example: "Translate the text below from English into Brazilian Portuguese. Preserve meaning, tone, and formatting; keep product names and numbers unchanged; add a [translator note] where there's no direct equivalent. [pasted text]"

45. Localize for a market

When to use: Not just translate, but adapt for local norms.

Localize the text below for [TARGET MARKET / LOCALE], not just translate it.
Adapt idioms, examples, currency, dates, units, and cultural references
so it reads as if written locally. Keep the core message and brand voice.
Note any change that might need a local reviewer's sign-off.
Text:
[PASTE TEXT]

Filled example: "Localize the text below for the German market. Adapt idioms, examples, currency, dates, and units to read as if written locally. Keep the message and brand voice. Flag anything needing a local reviewer. [pasted text]"

46. Simplify into another language for learners

When to use: Reach an audience reading in their second language.

Rewrite the text below in [TARGET LANGUAGE] at a [LEVEL, e.g. B1]
proficiency level. Use simple sentences and common vocabulary.
Keep all key facts. After the rewrite, list any specialized terms
with a one-line definition.
Text:
[PASTE TEXT]

Filled example: "Rewrite the text below in Spanish at a B1 level. Simple sentences, common vocabulary, all key facts kept. After, list specialized terms with a one-line definition. [pasted text]"

Coding & Technical

For larger or repository-wide work, use Claude Code (the developer coding agent) so Claude can read and edit files directly. The recipes below work in chat or in Claude Code.

47. Explain unfamiliar code

When to use: You inherited code and need to understand what it does.

Explain what the code below does, step by step, for a [LEVEL] developer.
Cover: its overall purpose, the key logic, any inputs and outputs,
and anything surprising or risky. Don't rewrite it — just explain.
Code:
[PASTE CODE]

Filled example: "Explain what the code below does, step by step, for a junior developer. Cover purpose, key logic, inputs/outputs, and anything risky. Don't rewrite it. [pasted code]"

48. Write a function from a spec

When to use: You know the behavior you want; you need the implementation.

Write a [LANGUAGE] function that [WHAT IT SHOULD DO].
Inputs: [INPUTS]. Output: [OUTPUT]. Edge cases to handle: [EDGE CASES].
Follow [STYLE / CONVENTIONS]. Include brief comments and a couple of
example calls. Explain any non-obvious choice.

Filled example: "Write a Python function that validates an email address. Input: a string. Output: True/False. Handle empty strings and missing @. Follow PEP 8. Include comments and example calls. Explain any non-obvious choice."

49. Debug an error

When to use: Something is broken and you have an error message.

I'm getting this error: [PASTE ERROR].
Here is the relevant code: [PASTE CODE].
What I expected: [EXPECTED]. What happens instead: [ACTUAL].
Identify the likely cause, explain why, and give the corrected code.
If you're unsure, list the top 2 possibilities and how to test each.

Filled example: "I'm getting this error: 'TypeError: cannot read property map of undefined'. Here is the code … I expected a list to render; instead the page is blank. Identify the likely cause, explain why, and give the corrected code."

50. Review code for quality

When to use: You want a second set of eyes before merging.

Review the code below as a senior engineer.
Check for: bugs, edge cases, security issues, readability, and performance.
For each finding give the severity, the line/area, why it matters,
and a suggested fix. Be concrete. Don't rewrite the whole thing.
Code:
[PASTE CODE]

Filled example: "Review the code below as a senior engineer. Check bugs, edge cases, security, readability, performance. Severity, location, why it matters, and a fix for each. Be concrete. [pasted code]"

51. Write tests

When to use: You need test coverage for a function or feature.

Write [TEST FRAMEWORK] tests for the code below.
Cover the happy path, edge cases, and error conditions.
Name each test clearly for what it checks. Note any case you couldn't
test and why. Code:
[PASTE CODE]

Filled example: "Write pytest tests for the code below. Cover the happy path, edge cases, and error conditions. Name each test for what it checks. Note any case you couldn't test. [pasted code]"

52. Translate code between languages

When to use: Port logic from one language or framework to another.

Convert the code below from [SOURCE LANGUAGE] to [TARGET LANGUAGE].
Preserve behavior exactly. Use idiomatic [TARGET LANGUAGE] conventions,
not a literal line-by-line copy. Flag anything that doesn't map cleanly
and explain your choice. Code:
[PASTE CODE]

Filled example: "Convert the code below from Python to TypeScript. Preserve behavior exactly, use idiomatic TypeScript, and flag anything that doesn't map cleanly. [pasted code]"

53. Explain a technical concept to a non-engineer

When to use: Bridge a technical topic for a business audience.

Explain [TECHNICAL CONCEPT] to a [NON-TECHNICAL AUDIENCE].
Skip the jargon, use one analogy, and focus on what it means for
[THEIR DECISION / WORK]. Keep it under [LENGTH]. End with the one
thing they actually need to remember.

Filled example: "Explain what an API is to our sales team. Skip the jargon, use one analogy, focus on what it means for selling integrations. Under 150 words. End with the one thing they need to remember."

A few habits that make every recipe work better

Habit	Why it helps
State the audience and goal	Claude tailors tone, depth, and emphasis when it knows who's reading and why.
Give an example of "good"	One or two samples (few-shot) beat a paragraph of description.
Ask for the format you want	Say "as a table," "as JSON," "under 200 words" — don't make Claude guess.
Constrain the source	"Use only the attached file" prevents outside or invented detail.
Iterate in the conversation	Refining a draft over 2–3 turns is faster than engineering one perfect prompt.
Verify before you rely	Treat output as a strong draft, not a final fact. You own the result.

End of library. Found a prompt that works well? Send it to your enablement champion so it can be vetted and added.