25 Claude Prompts for Better Writing: Copy-Paste Prompts for Emails, Blogs, Reports & Rewrites

1. Write a Professional Email From Rough Notes

Use this when you have bullet points or a messy paragraph and need to turn them into a finished email.

You are helping me turn rough notes into a clear, professional email.

Context: [CONTEXT: who you're writing to and why]

Rough notes: [PASTE NOTES]

Tone: [TONE, e.g., professional but warm, formal, friendly]

Goal: [GOAL: what you want the reader to do or understand]

Write a complete email based on these notes. Keep every fact and request from my notes; don't add new claims or soften any commitments I've made. Put the main point in the first two sentences, then add supporting detail. End with a clear next step. Return only the email, with a subject line.

Why this works: Breaking out the context, notes, tone, and goal means Claude doesn’t have to guess what you want. Asking it to preserve every fact and commitment also helps prevent firm language from being softened unintentionally. And by requesting only the finished email, you avoid extra commentary you would otherwise have to remove.

Customize it: Swap the tone line for “firm,” “apologetic,” or another description that better fits the situation.

2. Rewrite an Email to Sound More Professional

Use this when a draft is too casual or reads more like a text message than a work email.

Rewrite the email below so it reads as more professional, without changing what it says or who it's from.

Email: [PASTE EMAIL]

Audience: [AUDIENCE, e.g., client, senior manager, vendor]

Keep the same requests, decisions, and facts. Remove slang, overly casual phrasing, and anything that could come across as dismissive. Don't add extra pleasantries beyond what's normal for this audience, and don't make it longer than necessary. Return the rewritten email only.

Why this works: Limiting the rewrite to tone rather than content stops Claude from padding the email simply to make it sound “more professional.” Naming the audience also gives it a clear level of formality to aim for.

3. Make an Email Shorter and Clearer

Use this when a draft runs long and the main point is buried several paragraphs in.

Cut this email down so it's shorter and easier to read quickly, without losing anything the reader needs to know.

Email: [PASTE EMAIL]

Target length: [WORD COUNT, e.g., under 120 words]

Keep the core request and any dates, numbers, or names mentioned. Cut repeated points, throat-clearing, and unnecessary context. Put the ask in the first sentence. If cutting something would remove information the reader needs to act on, flag it instead of deleting it silently.

Why this works: Telling Claude to flag anything it is unsure about, rather than quietly removing it, reduces the risk of losing an important detail. The word-count target also replaces a vague instruction like “make it shorter” with a concrete goal.

4. Write a Polite Follow-Up Email

Use this when you’re waiting on a reply and want to give someone a gentle reminder without coming across as pushy.

Write a follow-up email for a situation where I haven't received a response yet.

Original message or context: [CONTEXT]

How long it's been: [TIME PERIOD]

What I need: [GOAL]

Tone: [TONE, e.g., patient, urgent but polite]

Keep it short, three or four sentences. Restate the original ask briefly so the reader doesn't have to search their inbox for it, and give them an easy way to respond. Don't apologize excessively for following up.

Why this works: Follow-ups often go wrong in one of two ways: they become too long or too apologetic. The instruction not to over-apologize keeps the message focused, while briefly restating the original request saves the recipient from searching through earlier emails.

5. Adjust an Email’s Tone Without Changing Its Meaning

Use this when the content is right, but the tone doesn’t match the relationship or situation.

Adjust the tone of this email to [TARGET TONE, e.g., warmer, more direct, more formal], without changing the meaning, facts, or requests.

Email: [PASTE EMAIL]

Context: [CONTEXT: relationship with the reader, situation]

Change word choice, sentence rhythm, and formality only. Do not add new information, change any commitments, or alter what's being asked for. If the current tone creates a specific problem, point it out briefly before the rewrite.

Why this works: Tone and content are easy to blur together, so asking for one can sometimes change both. Naming the target tone and asking Claude to identify the existing problem first makes the rewrite more controlled.

6. Write a Difficult or Sensitive Workplace Email

Use this for messages involving pushback, bad news, disagreement, or conflict, where the wrong wording could create unnecessary tension.

Help me write a difficult email for a sensitive workplace situation.

Situation: [CONTEXT: what happened, what needs to be communicated]

Recipient: [AUDIENCE: their role and relationship to you]

What I need to say: [KEY POINTS]

What I want to avoid: [e.g., sounding accusatory, admitting fault I don't own]

Write a version that's direct about the situation without being harsh, and professional without being evasive. Don't soften the message so much that the point gets lost. Give me one version, then briefly note anything in my key points that could read as more aggressive or apologetic than I intend.

Why this works: Difficult emails tend to fail in one of two directions: too blunt or too vague. Asking Claude to flag wording that may sound more aggressive or apologetic than intended helps catch problems that are difficult to notice when you’re close to the situation.

7. Turn an Outline Into a Blog Post

Use this when you already have the structure—headings, bullet points, or notes—but need full paragraphs written around it.

Turn this outline into a complete blog post.

Outline: [PASTE OUTLINE]

Topic: [TOPIC]

Audience: [AUDIENCE]

Tone: [TONE]

Target length: [WORD COUNT]

Follow the structure of the outline; don't reorganize it unless a section is clearly out of order. Write in complete paragraphs with natural transitions.

Use illustrative examples where helpful, but do not invent factual examples, statistics, companies, people, studies, quotations, or results. If a section needs information I haven't provided, mark where I should add it rather than making it up.

Don't add filler simply to reach the word count.

Why this works: Keeping Claude tied to your outline prevents it from restructuring your argument unnecessarily. More importantly, telling it to identify missing information instead of inventing details reduces the risk of plausible-sounding but unsupported claims appearing in the draft.

Customize it: Add “match the style of [REFERENCE TEXT]” if you have a sample of your own writing that reflects the tone you want.

8. Improve a Weak Blog Introduction

Use this when the body of a post is solid, but the opening takes too long to get to the point.

Improve this blog introduction so it draws the reader in faster.

Introduction: [PASTE DRAFT]

Topic: [TOPIC]

Audience: [AUDIENCE]

Get to the actual point faster; cut generic scene-setting the reader doesn't need yet. Start with something specific: a claim, a question the post answers, or a concrete detail, rather than a broad statement about the topic. Keep it roughly the same length as the original unless it's longer than it needs to be.

Why this works: Weak introductions often open too broadly before saying anything specific. Naming that problem gives Claude something concrete to fix, instead of vaguely asking it to “improve” the introduction, which can just produce a longer version of the same issue.

9. Rewrite a Section for Clarity and Flow

Use this when one part of a post feels awkward, but you don’t want the rest of the article rewritten.

Rewrite this section so it reads more clearly, without touching the rest of the post.

Section: [PASTE DRAFT]

Surrounding context (optional): [CONTEXT: what comes before and after]

Fix awkward sentences, unclear pronoun references, and rough transitions. Keep the same points and level of detail; don't add new information or cut anything substantive. Match the tone of the surrounding piece as closely as you can tell from the excerpt.

Why this works: Limiting the edit to one section, while giving Claude enough surrounding context, makes it easier to improve flow without triggering a full rewrite or creating a noticeable change in voice.

10. Make Technical Content Easier to Understand

Use this when a draft is accurate but too dense or jargon-heavy for the intended audience.

Rewrite this so it's easier for a non-technical reader to understand, without oversimplifying it to the point of being wrong.

Text: [PASTE DRAFT]

Audience: [AUDIENCE, e.g., new customers, executives, general readers]

Terms that must stay accurate: [KEY POINTS or specific terminology]

Replace jargon with plain language, or add a brief explanation the first time a term appears. Use analogies only where they clarify rather than distract. Keep technical accuracy; if simplifying a point would make it inaccurate, keep the precise version and explain it more simply instead of cutting it.

Why this works: Identifying the terminology that must remain accurate stops Claude from smoothing over technical distinctions that matter. That’s one of the biggest risks when asking an AI model to simplify technical content.

11. Remove Repetition and Filler

Use this when a draft makes the same point more than once or contains phrases that add words without adding meaning.

Edit this draft to remove repetition and filler without cutting any unique information.

Draft: [PASTE DRAFT]

Find places where the same point is made more than once and keep only the clearest version. Cut filler phrases and hedging that don't add meaning ("it's worth noting," "in order to," unnecessary qualifiers). Don't cut examples, data, or specific claims; those should stay even as the surrounding language gets tighter. Show me the edited version only.

Why this works: This separates two different problems—repeated ideas and empty phrasing—that a simple “make this tighter” instruction can blur together. Naming both gives Claude a clearer editing target.

12. Improve Transitions Between Sections

Use this when each section works on its own, but the full article reads like a collection of disconnected pieces.

Look at the transitions between sections in this draft and improve them so the post reads as one connected piece.

Draft: [PASTE DRAFT]

Don't rewrite the sections themselves; only add or adjust the sentences that connect one to the next. Each transition should reflect the actual relationship between sections (contrast, cause and effect, a natural next step), not a generic connector. Point out any place where the order of sections itself seems to be the real problem.

Why this works: Isolating the transitions prevents the request from turning into a full rewrite. Asking Claude to reflect the real relationship between sections also encourages meaningful connections instead of generic transition phrases.

13. Edit a Blog Post Without Changing the Writer’s Voice

Use this when you want errors and awkward phrasing fixed without flattening the writer’s personality.

Edit this blog post for clarity, grammar, and flow, while keeping the writer's voice and personality intact.

Draft: [PASTE DRAFT]

Fix genuine errors and awkward phrasing. Don't smooth out stylistic choices that seem intentional (unusual sentence rhythm, informal phrasing, an opinion stated directly). If you're not sure whether something is a mistake or a stylistic choice, leave it and flag it separately. Return the edited draft, followed by a short list of what you changed and why.

Why this works: Asking Claude to flag uncertain cases rather than automatically changing them reduces the chance of a distinctive writing style being rewritten into generic prose. The change list also makes individual edits easier to review or reject.

14. Turn Notes Into a Professional Report

Use this when you have raw notes or bullet points that need to become a structured business report.

Turn these notes into a structured, professional report.

Notes: [PASTE NOTES]

Purpose of report: [GOAL]

Audience: [AUDIENCE]

Sections needed (if known): [e.g., background, findings, recommendations]

Organize the notes into logical sections with clear headings. Keep every specific fact, number, and finding; don't generalize away detail or invent context I haven't given you. Where my notes are incomplete or unclear, note that instead of assuming. Write in a formal but readable tone suited to [AUDIENCE].

Why this works: Reports are especially sensitive to invented details because readers may treat the finished document as authoritative. Telling Claude to flag gaps rather than filling them in keeps the report tied to the information you actually supplied.

15. Write an Executive Summary

Use this when you have a full report and need a shorter version for readers who may never get past the first page.

Write an executive summary for the report below.

Report: [PASTE DRAFT]

Length: [WORD COUNT, e.g., 150-200 words]

Audience: [AUDIENCE, e.g., leadership team, board, client]

Cover the purpose of the report, the key findings, and any recommendations or decisions needed, in that order. Don't include background detail unnecessary for someone reading only the summary. Use plain, direct sentences rather than dense phrasing. If the report doesn't clearly state a recommendation, say so instead of inventing one.

Why this works: Executive summaries can easily become either too detailed or so cautious that the main message disappears. Giving Claude a clear order and word-count target provides a useful structure without asking it to decide what the report should recommend.

16. Convert Technical Findings Into Business Language

Use this when specialists need non-technical decision-makers to understand what their findings actually mean.

Rewrite these technical findings in business language for [AUDIENCE], without losing the substance of what was found.

Findings: [PASTE DRAFT]

Decision this will inform: [CONTEXT]

Focus on what the findings mean for the business (cost, risk, timeline, opportunity) rather than the technical process behind them. Keep any numbers or thresholds that matter to the decision. Avoid jargon; where a term is unavoidable, explain it in one short phrase. If a finding is uncertain or preliminary, keep that uncertainty visible rather than stating it as settled.

Why this works: Preserving uncertainty matters because business readers need to know when a finding is preliminary rather than confirmed. That distinction is easy to lose when technical material is simply translated into “plain English.”

17. Improve a Proposal or Business Document

Use this when a proposal is already written but needs to explain its value more clearly or persuasively.

Review and improve this business proposal.

Proposal: [PASTE DRAFT]

What we're proposing: [CONTEXT]

Audience or decision-maker: [AUDIENCE]

Goal: [GOAL, e.g., get sign-off, win the bid]

Strengthen the sections that explain the value or outcome for the reader, and tighten anything vague about scope, cost, or timeline. Keep all specific numbers, dates, and commitments exactly as written unless they're inconsistent; if you find an inconsistency, point it out rather than picking a version for me. Don't add promises that aren't already in the draft.

Why this works: Proposals can carry commercial consequences, so preventing Claude from adding unstated promises is especially important. Asking it to flag inconsistencies rather than silently choosing one version can also catch mistakes before a customer or decision-maker does.

18. Summarize a Long Document While Preserving Important Details

Use this when you need a shorter version of a document but can’t afford to lose the details that affect a decision.

Summarize this document, keeping all details that would matter to someone making a decision based on the summary.

Document: [PASTE DRAFT]

Length: [WORD COUNT]

What matters most: [KEY POINTS, e.g., dates, dollar amounts, risks, obligations]

Prioritize the items I've listed as mattering most, and don't drop them even if it means cutting other content instead. Keep specific numbers, names, and dates exact; don't round or generalize them. If the document contains conflicting information, note the conflict rather than choosing a side.

Why this works: General summarization can flatten a document by treating every section as equally important. Telling Claude what matters most, and instructing it to preserve exact numbers, names, and dates, makes the result more useful for someone who has to act on it.

19. Convert Meeting Notes Into Clear Action Items

Use this when your meeting notes are messy and need to become a clear record of decisions, actions, and open questions.

Turn these meeting notes into a clear list of decisions and action items.

Notes: [PASTE NOTES]

Separate the notes into three groups: decisions made, action items (with owner and deadline if mentioned), and open questions that weren't resolved. If an action item doesn't have a clear owner or deadline, list it anyway but mark it as unassigned rather than guessing who's responsible. Keep the wording close to what was actually said; don't infer commitments that weren't explicitly made.

Why this works: AI-generated meeting summaries can sometimes assign ownership or deadlines that were implied rather than confirmed. Marking unclear items as unassigned instead of guessing keeps the output closer to what actually happened.

20. Rewrite Text While Preserving the Original Meaning

Use this as a general-purpose rewrite prompt when you want better wording without changing the underlying message.

Rewrite the text below to improve sentence flow and word choice, while preserving the exact meaning and any facts stated.

Text: [PASTE DRAFT]

Tone to keep or adjust to: [TONE]

Don't make it more formal or casual than the original unless I've specified a tone above. Keep terminology specific to the subject rather than replacing it with a generic synonym. If a sentence is ambiguous enough that you're unsure what it means, flag it instead of guessing and rewriting around a possibly wrong interpretation. Return the rewritten text only.

Why this works: A plain “rewrite this” leaves too much room for interpretation. Clearly identifying what must remain unchanged—facts, terminology, meaning, and formality—helps separate a genuine improvement from a rewrite that drifts away from what you intended.

21. Make AI-Generated Writing Sound More Natural

Use this when a draft feels stiff, repetitive, overly polished, or obviously machine-written.

Edit this draft so it reads more naturally and less like generic AI writing, without changing the substance.

Draft: [PASTE DRAFT]

Vary sentence length instead of keeping everything the same size. Cut generic transition phrases and hedge words that don't add meaning. Remove any list format used just to pad the piece out; use plain paragraphs where a list isn't needed. Keep every fact and point the same; this is a style edit, not a content edit.

Why this works: Writing that feels “AI-generated” often has more to do with repetitive sentence rhythm, predictable transitions, and unnecessary structure than with any single word. Naming those patterns gives Claude specific things to look for instead of asking vaguely for something that “sounds human.”

Customize it: If you maintain a list of words or phrases you want to avoid, add them to the prompt and ask Claude to check for them specifically.

22. Fix Grammar Without Rewriting Unnecessarily

Use this when a draft is almost finished and needs proofreading, not another full editorial pass.

Proofread this text for grammar, punctuation, and spelling only. Do not rewrite sentences that are already correct, and do not change style, tone, or word choice unless it's a genuine error.

Text: [PASTE DRAFT]

List each correction separately with a brief note on what was wrong, then provide the corrected version in full. If something is a style choice rather than an error, leave it as is.

Why this works: Without clear restrictions, a request to “proofread” can easily turn into a rewrite. Asking for a list of corrections makes it easier to distinguish actual mistakes from stylistic changes Claude prefers.

23. Simplify Complicated Writing

Use this when a draft is correct but too dense, formal, or difficult for its intended audience to follow comfortably.

Simplify this text so it's easier to read, without losing any of the actual information.

Text: [PASTE DRAFT]

Reading level or audience: [AUDIENCE]

Break up long sentences, replace complex words with simpler ones where the meaning doesn't change, and cut unnecessary qualifiers. Keep every specific point and number; simplifying language isn't the same as cutting content, and both shouldn't happen at once unless I ask for a shorter version too. If a concept genuinely can't be simplified without losing accuracy, keep it as is and explain briefly why.

Why this works: “Simpler” and “shorter” are not the same thing, but they’re often treated as if they are. Keeping those goals separate reduces the chance of useful information disappearing when you simplify the wording.

24. Make Writing More Concise

Use this when a draft says what it needs to say but takes too many words to get there.

Make this text more concise without losing any information or changing its meaning.

Text: [PASTE DRAFT]

Target: [WORD COUNT, or "as short as possible without losing meaning"]

Cut redundant words and phrases, combine sentences that repeat the same idea, and remove qualifiers that don't change the meaning ("very," "really," "basically"). Don't cut examples, numbers, or specific claims just to save words. If you can't hit the target without cutting something substantive, say so instead of cutting it anyway.

Why this works: Word-count targets can encourage a model to remove important material simply to reach the requested number. Giving Claude permission to say when a target cannot be met without losing substance produces a more useful edit.

25. Perform a Final Editorial Review Before Publishing

Use this as a last check before publishing or sending something important.

Do a final editorial review of this draft before I publish it.

Draft: [PASTE DRAFT]

Where this will be published or sent: [CONTEXT]

Audience: [AUDIENCE]

Check for: unclear or ambiguous sentences, factual claims that sound like they might need a source, inconsistent tone, repeated points, and anything that could be misread by [AUDIENCE]. List each issue separately with the relevant sentence, rather than rewriting the whole draft. Let me decide what to fix.

Why this works: Asking Claude to identify problems rather than silently rewriting them turns it into a second pair of eyes, not another editing pass you have to compare from scratch. It can also flag claims that may need verification or sourcing before publication.

Give it context, not just text. Don’t simply paste a draft and say “rewrite this.” Tell Claude who the writing is for, why you’re writing it, and what the reader needs from it. “Rewrite this for a client who’s already frustrated about a delay” gives the model far more useful direction than “make this more professional.”

Name the audience specifically. “General audience” doesn’t give Claude much to work with. “Small business owners with no technical background” gives it a clearer target for vocabulary, examples, and detail level.

Describe the tone instead of saying “better.” Words such as “warmer,” “more direct,” “formal but approachable,” or “firm without sounding aggressive” are instructions Claude can act on. “Better” isn’t.

Tell Claude what has to stay the same. Facts, numbers, terminology, commitments, quotations, or a distinctive voice can all change during a rewrite if you don’t explicitly say they must be preserved.

Show it an example when style matters. If you already have a paragraph that sounds the way you want, paste it alongside your draft and ask Claude to use it as a style reference. A concrete example is often more useful than a long list of adjectives describing your preferred voice.

Ask Claude to flag uncertainty rather than fill gaps. If your notes are incomplete, tell Claude to identify what is missing instead of guessing. This is particularly important for reports, technical content, proposals, and anything containing factual claims.

No matter how detailed your prompt is, treat the output as a draft. Read it before you send, publish, or rely on it for anything important.

Both can work, depending on what you’re starting with.

Drafting from scratch makes sense when you already know the structure and key points and mainly need help turning them into complete prose. Outlines, meeting notes, research notes, and known facts can all provide enough structure for Claude to create a useful first draft.

Starting with your own draft often works better when the writing needs to preserve a particular voice, include precise commitments, or handle a sensitive situation. A client proposal, a difficult workplace email, or a technical report already contains decisions and nuances you may not want a model inventing for you.

For many professional tasks, the most practical approach is somewhere in between: use Claude to help create or improve the first version, then review the final wording yourself—especially when the document involves legal, financial, technical, or relationship-sensitive details.

These prompts aren’t rigid formulas. They’re starting points you can adjust depending on what you’re writing.

Swap out the placeholders, remove instructions that don’t apply, and add constraints specific to your situation. The underlying pattern is simple: tell Claude what needs to stay the same, who the writing is for, what you want changed, and what a good result should look like.

Save the prompts you use most often and refine them as you learn what works for your own documents. A prompt shaped around your usual audience, tone, and workflow will generally be more useful than starting from a generic instruction every time.