These are reusable skeletons — the structure is done, you fill in the blanks. Each is built on the Role → Task → Context → Format (RTCF) pattern with XML tags already in place, so you just replace the [BRACKETS] and drop your material between the tags. They're tuned for Claude Opus 4.8 and Fable 5.

For finished examples, see the best Claude prompts; for the reference, the Claude prompt cheat sheet.

Advertisement

How to use these

Copy a template, swap every [BRACKET] for your real details, and paste your content inside the tags. Delete any line that doesn't apply, and add "think step by step" for hard reasoning. Keep the Format line at the end — it's what makes the output arrive in the shape you need.

Work & email

1. Email reply

Draft a reply to this thread in my voice.
Goal: [WHAT I WANT TO HAPPEN]. Tone: [WARM AND PROFESSIONAL / DIRECT].
<thread>
[PASTE THE EMAIL THREAD]
</thread>
Under [WORD COUNT] words. Address every open question. Don't invent facts — leave [placeholders] where you need info. Give me two versions: concise and slightly warmer.

2. Meeting to actions

Turn this meeting transcript into a follow-up.
<transcript>
[PASTE THE TRANSCRIPT]
</transcript>
Give me: a 5-bullet summary of decisions; action items as owner — task — due date (mark unassigned/no date where missing); unresolved questions; and a short recap email to attendees.

3. One-page brief / memo

Write a one-page [BRIEF / MEMO] for [AUDIENCE] that should drive [DECISION / ACTION].
<raw>
[PASTE YOUR NOTES AND ANY DATA]
</raw>
Structure: TL;DR, context, options/recommendation, risks, next steps. One page max. Recommend, don't just summarize. Bold the one thing they must not miss.

4. Decision memo

Help me decide and write it up. Think step by step.
Decision: [DECISION]. What matters: [BUDGET, TIMELINE, RISK, TEAM].
<options>
[OPTION A]
[OPTION B]
[OPTION C]
</options>
Score each option against my criteria in a table, recommend one with reasoning, write a one-page memo for my manager, and list the top 2 risks of the pick.

Writing

5. First draft from notes

Write a first draft of [PIECE] for [AUDIENCE], about [LENGTH] words, in a [PLAIN / WARM / PUNCHY] style.
<notes>
[PASTE YOUR BULLETS, QUOTES, LINKS]
</notes>
Use only what's in my notes — don't invent facts. Open with a concrete hook, not a definition. No clichés. Leave [placeholders] where I still need to add something.

6. Match my voice

Learn my writing voice, then write in it.
<samples>
[PASTE 2-3 PIECES OF YOUR WRITING]
</samples>
First describe my voice in 5 bullets (sentence length, vocabulary, rhythm, tone, quirks). Then write [THE PIECE]: [TOPIC], [AUDIENCE], [LENGTH]. Match the samples; don't drift into generic style.

7. Line edit

Act as a strict line editor. Make this sharper without changing my voice.
<text>
[PASTE YOUR DRAFT]
</text>
Tighten every sentence, kill clichés and filler, keep my quirks. Show the edited version, then list the 3 biggest changes and why. Don't add new claims.

8. Repurpose into posts

Repurpose this into social posts for [PLATFORMS], in a [VOICE] voice.
<source>
[PASTE THE ARTICLE / TALK / THREAD]
</source>
Pull the 5 strongest standalone ideas; for each, write a post with a real hook (no "Here are 5 things..."). Keep every claim faithful to the source. Say which to lead with and why.
Advertisement

Coding

9. Write a function

Act as a senior [LANGUAGE] engineer. Write a function that [INPUTS -> BEHAVIOR -> OUTPUTS] and handles [EDGE CASES]. Clean, idiomatic code following [CONVENTION], with input validation and unit tests for the happy path and every edge case. Explain any non-obvious decision in one line.

10. Debug

Diagnose and fix this. Think step by step.
<error>
[PASTE THE FULL ERROR + STACK TRACE]
</error>
<code>
[PASTE THE RELEVANT CODE]
</code>
Expected: [X]. Actual: [Y]. Give the most likely root cause first, then 2 alternates, the exact fix, and how to confirm it's resolved.

11. Review

Act as a staff engineer reviewing this. Think step by step. Intent: [WHAT IT SHOULD DO].
<code>
[PASTE THE DIFF OR FILES]
</code>
List issues most severe first (correctness, security, edge cases, then style), each with the location and a fix. Don't rewrite the whole file — point to specific lines.

12. Build an app (Artifact)

Build a working single-file app as an Artifact: [WHAT IT DOES] for [USERS] on [DEVICE]. One self-contained HTML file, inline CSS/JS, no dependencies. Clean responsive UI, sensible defaults, handle empty and error states. After it works, list 3 features I could add next.

Research & study

13. Research with sources

Research [QUESTION] and give me a sourced brief. Use web search for anything current.
Purpose: [THE DECISION THIS FEEDS]. What I already know: [CONTEXT].
Cover current state, key options, trade-offs, and what's changed recently. Cite sources with links. End with a recommendation and 3 open questions. Flag anything you're unsure about.

14. Compare options

Compare [OPTION A], [OPTION B], and [OPTION C] for [PURPOSE]. Use web search and cite current pricing.
What matters most: [CRITERIA]. Build a comparison table scored against my criteria, recommend one with a "choose X instead if..." caveat, and note anything that changed recently.

15. Study plan

Build me a study plan to learn [TOPIC/SKILL].
Current level: [BEGINNER / SOME EXPERIENCE]. I can spend [X HOURS/WEEK] and want to be [TARGET ABILITY] in [TIMEFRAME].
Break it into weekly milestones with a concrete outcome each; for each, one thing to read/watch and one to build/practice. Point out where people get stuck. Tell me how I'll know I've learned each part.

Data

16. First look at a dataset

Give me a first look at this dataset. Use the analysis tool to compute, don't estimate. My question: [QUESTION].
<data>
[ATTACH OR PASTE THE DATA]
</data>
Data-quality check first (rows, types, missing values, duplicates, anomalies), then a statistical summary, the 3 things that stand out, and what I should ask next.

17. Answer a data question

Answer this from my data. Compute with code and show your work. Question: [PRECISE QUESTION].
<data>
[ATTACH OR PASTE THE DATA]
</data>
Give the exact answer with numbers, show the calculation so I can verify, note any assumption (date ranges, filters, blanks), and flag if the data can't answer this.

18. Chart as an Artifact

Turn my data into a clean chart as an Artifact. The point it should make: [MESSAGE].
<data>
[ATTACH OR PASTE THE NUMBERS]
</data>
Pick the chart type that best shows that point (say why in one line), render it as an interactive Artifact, label axes and add a title, and suggest one alternative view.

19. Spreadsheet formula

Give me a working [EXCEL / GOOGLE SHEETS] formula and explain it.
My columns: [E.G. DATES IN A, AMOUNT IN B, CATEGORY IN C]. I want to [WHAT TO CALCULATE].
Give the exact formula with real references, explain each part in one line, offer a cleaner alternative if there is one, and warn me about edge cases (blanks, text vs. numbers).

Paste the templates you reuse into a Project's custom instructions or a Style so Claude applies the setup automatically. For finished versions, browse the best Claude prompts, the coding pack, or the writing pack.

Frequently Asked Questions

How do I use these Claude prompt templates?

Copy a template, replace every [BRACKETED] placeholder with your real details, and paste your material inside the XML tags where marked. Keep the Role, Task, Context, and Format structure intact — that's what makes them work. Delete any line that doesn't apply to your task, and add "think step by step" for hard reasoning.

Why do the templates use XML tags?

Claude was trained to pay attention to XML tags, so wrapping your pasted material in a named tag — <document>, <code>, <data> — tells Claude exactly what it is and keeps it separate from your instructions. The templates leave the tags in place so you just drop your content between them.

Can I save these as reusable prompts in Claude?

Yes. Paste a template you use often into a Project's custom instructions, or build a Style around the voice ones, so Claude applies the setup automatically. That way you fill in only the changing details each time instead of re-pasting the whole template.

Which model should I run these on?

Claude Opus 4.8 is the strong default. Use Fable 5 for the longest, most complex tasks, Sonnet 5 as a fast, capable daily driver, and Haiku 4.5 for quick, high-volume jobs. The template text is identical across models.

How detailed should my placeholders be?

As detailed as you can be. The more specific your context — real audience, real constraints, real numbers — the better the output. Vague placeholders produce vague answers. When you don't know a detail, tell Claude to ask you or to leave a bracketed gap rather than inventing it.

Do I need to keep the Format line at the end?

Keep it — the Format line is where you tell Claude the shape of the answer (length, table, JSON, diff, Artifact). Claude follows explicit format instructions reliably, so this line is what stops you from getting a wall of text you have to reshape. Adjust it to whatever output you actually need.

Advertisement