Twenty-six writing prompts for Claude — the model known for natural, controllable prose. They're built for Claude Opus 4.8, with Fable 5 for book-length work and Haiku 4.5 for quick drafts. Each wraps your material in XML tags so Claude edits the right thing, and several use custom Styles so the output sounds like you.
Pair these with the best Claude prompts for everything else, the cheat sheet for the formula, and templates when you want fill-in skeletons.
Drafting
Five prompts to beat the blank page. Give Claude your material in tags so it builds on your facts instead of inventing them.
1. First Draft From My Notes
Write a first draft from my rough notes.
Piece: [blog post / newsletter / essay / section]. Audience: [who]. Length: [words]. Style: [plain and direct / warm / punchy].
<notes>
[paste your bullet points, quotes, and links]
</notes>
Constraints:
- Use only what's in my notes — don't invent facts or stats.
- Open with a concrete hook, not a definition or a "in today's world" line.
- Leave [bracketed placeholders] where I still need to add something.
- No clichés, no filler.Why it works: "Use only what's in my notes" stops Claude from padding the draft with invented specifics.
2. Outline Before Drafting
Outline this piece before we write it.
Topic: [topic]. Audience: [who and their level]. Goal: [what the reader should think or do after].
Give me:
- A working title and 2 alternates.
- A section-by-section outline with a one-line purpose for each.
- The single argument or throughline the whole piece serves.
- The 3 questions the piece must answer to be worth reading.
Don't write the draft yet.Best for: Getting structure and intent locked before you spend an hour writing the wrong thing.
3. Turn a Transcript Into an Article
Turn this talk/interview transcript into a readable article.
<transcript>
[paste the transcript]
</transcript>
Target: [publication / blog], [length], for [audience].
Do this:
- Keep the speaker's ideas and best lines; cut the ums, repetition, and tangents.
- Impose a clear structure with headings.
- Preserve any strong direct quotes verbatim and mark them.
- Flag anything unclear that I should confirm with the speaker.Why it works: Claude holds the whole transcript in context, so it can restructure globally instead of paragraph by paragraph.
4. Generate Angles and Hooks
Give me strong angles for a piece before I commit to one.
Topic: [topic]. Audience: [who]. What I know that's a bit contrarian or specific: [your edge].
Do this:
- Propose 8 distinct angles, each with a one-line hook.
- Note which are fresh vs. done-to-death.
- For my 3 favorites (I'll pick), suggest the opening line.
Prioritize angles only I could write, given my edge.Best for: Finding the take worth writing instead of the obvious one everyone's already published.
5. Explain a Hard Idea Clearly
Write a clear explainer of a complex idea.
Explain [concept] to [audience]. They currently [what they know / believe].
Constraints:
- Open with a one-sentence plain-English definition.
- Use one concrete analogy and one real example.
- Address the most common misunderstanding directly.
- Define any unavoidable jargon inline.
- Keep it under [N] words and don't oversimplify to the point of being wrong.Why it works: Naming what the audience already believes lets Claude correct the specific misconception instead of explaining into a void.
Editing & polish
Five prompts that improve a draft without flattening it. Put the text in a tag and tell Claude what to protect.
6. Line Edit for Sharpness
Act as a strict line editor. Make this sharper without changing my voice.
<text>
[paste your draft]
</text>
Do this:
- Tighten every sentence; cut words that earn nothing.
- Kill clichés, hedging, and corporate filler.
- Keep my voice and any deliberate quirks.
- Show the edited version, then list the 3 biggest changes and why.
Don't add new claims.Best for: Turning a good draft into a tight one while keeping it unmistakably yours.
7. Developmental Edit
Give me a developmental edit — structure and argument, not commas.
<text>
[paste your draft]
</text>
What I want this piece to do: [goal].
Do this:
- Tell me whether the structure serves the goal, and where it sags.
- Point out where the argument is thin, unsupported, or out of order.
- Suggest what to cut, what to expand, and a better order if needed.
- Don't rewrite it — give me notes I can act on.Why it works: Asking for structure-level notes (not a rewrite) surfaces the problems a line edit would paper over.
8. Proofread and Explain
Proofread this and teach me my patterns.
<text>
[paste your text]
</text>
Style guide: [AP / Chicago / British English / none].
Do this:
- Fix grammar, spelling, punctuation, and consistency.
- Return the corrected text.
- Then list the recurring mistakes I make, so I can watch for them.
Change wording only where it's actually wrong, not to taste.Best for: Clean copy plus a short lesson on the errors you keep repeating.
9. Cut It Down
Cut this to a target length without losing what matters.
<text>
[paste text]
</text>
Target: [word count / single paragraph / half the length].
Constraints:
- Keep every essential fact and the core argument.
- Remove repetition, hedging, and throat-clearing.
- Add nothing new.
- Show the trimmed version and the final word count.Why it works: A hard target plus "add nothing new" forces genuine compression, not a light trim.
10. Fact-Check My Own Draft
Pressure-test the claims in my draft. Use web search where you can verify.
<text>
[paste your draft]
</text>
Do this:
- List every factual claim, stat, and quote.
- Mark each: verified (with source), unverified, or likely wrong.
- Flag anything that reads as overstated or missing a caveat.
- Tell me which claims most need a citation before I publish.
Don't rewrite — just the audit.Best for: Catching the confident-but-wrong line before a reader (or an editor) does.
Voice & style
Four prompts to control tone. Give Claude samples in a tag, or save a custom Style so every reply matches automatically.
11. Match My Voice From Samples
Learn my writing voice, then write in it.
<samples>
[paste 2-3 pieces of your best writing]
</samples>
Do this:
- First, describe my voice in 5 bullets: sentence length, vocabulary, rhythm, tone, quirks.
- Then write [the piece] in that voice: [topic, audience, length].
- Match the samples; don't drift into generic "content" style.
- Point out anywhere you weren't sure how I'd phrase something.Why it works: Making Claude articulate your voice first gives it a rubric to write against, and the match is much closer.
12. Rewrite in a Specific Tone
Rewrite this in a different tone without changing the meaning.
<text>
[paste text]
</text>
Target tone: [confident and warm / formal / playful / plain and direct].
Audience: [who].
Constraints:
- Preserve every fact and the original intent.
- Give me the rewrite, then one line on what shifted.
- Offer a second, slightly [more/less] intense version.Best for: Reusing the same content for different audiences without rewriting from scratch.
13. Match a Brand Voice
Write in our brand voice.
<voice_guide>
[paste your brand voice notes, or 3 examples of on-brand copy]
</voice_guide>
Write: [the asset — e.g. product page, email, tweet]. Audience: [who].
Constraints:
- Follow the voice guide exactly; flag if my brief conflicts with it.
- No hype words, no exclamation-mark spam unless the guide allows it.
- Give me the copy plus a one-line note on how it hits the voice.Why it works: Pasting real on-brand examples beats abstract adjectives like "friendly but professional".
14. De-AI a Draft
Make this sound like a person wrote it, not a model.
<text>
[paste the AI-ish draft]
</text>
Do this:
- Remove the tells: "in today's world", "it's important to note", "delve", "unlock", tidy lists of three, and uniform sentence length.
- Vary rhythm; let some sentences be short and blunt.
- Add one concrete, specific detail where it's generic.
- Keep the meaning; don't invent facts.Best for: Scrubbing the giveaways out of a fast draft before anyone reads it.
Long-form
Four prompts for pieces too big for one message. Keep the outline and prior sections in a Project so continuity holds.
15. Plan a Book or Long Report
Help me plan a [book / long report / guide].
Subject: [subject]. Audience: [who]. Goal: [what they get]. Rough length: [pages/words].
Give me:
- A chapter/section structure with a one-paragraph summary of each.
- The throughline that connects them.
- What belongs in each part vs. what to cut for scope.
- A realistic order to write them in.
We'll draft one section at a time from this plan.Why it works: A shared plan Claude can refer back to keeps a long project coherent instead of drifting chapter to chapter.
16. Draft One Section, In Context
Draft the next section, keeping continuity.
<outline>
[paste the overall outline]
</outline>
<previous>
[paste the last section or a summary of what came before]
</previous>
Now write: [this section], [length], in the style established so far.
Constraints:
- Pick up where the previous section left off; no repeating what's covered.
- Keep the voice and terminology consistent.
- End with a bridge into what comes next.Best for: Book-length writing — feeding the outline and prior text keeps voice and facts consistent.
17. Continuity and Consistency Check
Check this long piece for consistency.
<manuscript>
[paste the chapters or the full draft]
</manuscript>
Do this:
- Flag contradictions in facts, names, timeline, or terminology.
- Note where the voice or tense shifts unintentionally.
- List anything set up earlier but never paid off (or vice versa).
- Give me a punch list ordered by how jarring each issue is.Why it works: Claude's long context lets it hold the whole manuscript at once and catch cross-chapter slips a human skims past.
18. Summarize My Own Long Draft
Summarize my long draft so I can see its shape.
<draft>
[paste the full draft]
</draft>
Give me:
- A one-paragraph synopsis.
- The argument as a numbered spine (each section's job).
- Where the piece is strongest and where it drags.
- The one cut that would improve it most.Best for: Seeing your own structure from the outside when you're too close to it.
Social & content
Four prompts for posts and content. Feed Claude the source so it repurposes real material, not generic takes.
19. Turn One Piece Into a Content Set
Repurpose this into a set of social posts.
<source>
[paste the article, talk, or thread]
</source>
Platforms: [LinkedIn / X / Instagram / newsletter]. Voice: [describe].
Do this:
- Pull the 5 strongest standalone ideas.
- For each, write a post tuned to [platform] with a real hook (no "Here are 5 things...").
- Keep every claim faithful to the source.
- Suggest which one to lead with and why.Why it works: Extracting ideas from real source material keeps the posts specific instead of interchangeable.
20. Write a LinkedIn Post That Isn't Cringe
Write a LinkedIn post about [topic / story / lesson].
Context: [what actually happened or what you learned]. Audience: [who follows me].
Constraints:
- Open with a specific, concrete first line — no "I've been thinking a lot about..."
- One clear idea, told plainly. No fake vulnerability, no broetry line breaks for effect.
- End with a genuine question or takeaway, not "Agree?"
- Under 200 words. Give me 2 versions.Best for: Posting without the LinkedIn-influencer tics — the banned-phrases list does the heavy lifting.
21. Newsletter Issue From a Theme
Draft a newsletter issue.
Theme: [theme]. Audience: [who and why they subscribed]. Voice: [describe]. Length: [words].
Material I want to include:
<material>
[links, notes, a personal anecdote, anything to feature]
</material>
Do this:
- A subject line (+2 alternates) and a one-line preview.
- A tight intro that earns the open.
- The body built around my material.
- One clear call to action.
No filler sections just to hit length.Why it works: Building around your supplied material keeps the issue personal and specific rather than a roundup of nothing.
22. Headlines and Subject Lines
Write headlines/subject lines for this.
<piece>
[paste the content or describe it]
</piece>
Goal: [clicks / opens / shares]. Audience: [who]. Tone: [straight / playful / bold].
Do this:
- Give me 12 options across a few angles (benefit, curiosity, specific, contrarian).
- Mark the 3 you'd bet on and why.
- Avoid clickbait that the piece can't cash.Best for: A/B options fast — the "can't cash" rule keeps them honest.
Emails & messages
Four prompts for the writing you do most. Give Claude the thread and your goal; keep it short.
23. Reply in My Voice
Draft a reply in my voice.
Goal for the reply: [goal]. Tone: [warm and professional / direct].
<thread>
[paste the email thread]
</thread>
Constraints:
- Under 150 words. Address every open question.
- Don't invent facts — leave [placeholders] where you need info.
- Two versions: one concise, one slightly warmer.Best for: Fast, in-context replies. For a full email set, see the business & work prompts.
24. Say No, Gracefully
Help me decline without burning the relationship.
I need to say no to [request] from [who]. Why I'm declining: [reason]. What I want to preserve: [the relationship / the door open / my time].
Constraints:
- Warm, clear, and brief — no long apology or over-explaining.
- Decline plainly; offer an alternative only if I actually want to.
- Two versions: firmer and softer.
- Under 100 words each.Why it works: Naming what you want to preserve calibrates how much warmth vs. firmness the message needs.
25. Cold Outreach That Gets a Reply
Write a cold outreach message.
I'm [you] reaching out to [recipient and role] because [genuine reason]. What I want next: [clear, low-friction ask].
Constraints:
- Under 120 words. No "I hope this finds you well".
- Lead with why I'm relevant to them, not why they matter to me.
- One specific call to action.
- 3 subject lines to test.Best for: Sales, partnerships, or job outreach where short and specific beats a long pitch.
26. Difficult Personal Message
Help me say something hard, well.
I need to [apologize / set a boundary / share bad news / reconnect] with [who]. Situation: [context]. I want them to feel [respected / clear / cared for].
Constraints:
- Honest, kind, not passive-aggressive.
- Own my part where fair; don't over-apologize.
- Two versions: softer and more direct. Under 120 words each.Why it works: Stating the feeling you're aiming for steers tone better than describing the situation alone.
Reuse your voice and style rules by saving them as a custom Style or inside a Project, so every draft starts on-voice. For the underlying pattern, see the Claude prompt cheat sheet, and grab fill-in-the-blank templates for the pieces you write most.
Frequently Asked Questions
Why is Claude good at writing?
Claude is known for natural, controllable prose and for following detailed style and tone instructions closely. It holds a long piece in context without losing the thread, edits without flattening your voice, and pushes back when you ask it to. Claude Opus 4.8 is the strong default for nuanced writing; Fable 5 handles book-length and highly complex pieces, and Haiku 4.5 is fast for quick drafts.
How do I make Claude write in my voice?
Give it samples. Paste 2-3 pieces of your best writing wrapped in a <samples> tag and tell Claude to match the voice — sentence length, vocabulary, rhythm, and quirks. In the Claude app you can also create a custom Style from your samples so every reply uses it automatically. The more specific your description of the voice, the closer the match.
How do I stop Claude's writing from sounding like AI?
Ban the tells. Add constraints like no clichés, no "in today's world" openers, no "it's important to note", vary sentence length, and start with something concrete instead of a definition. Give it your own samples to match, ask it to keep your quirks, and have it cut anything that sounds like filler. Then edit the result yourself.
Can Claude help with a whole book or long report?
Yes. Claude's large context window lets it hold a long manuscript, and a Project keeps your outline, characters, style guide, and prior chapters as shared knowledge across every chat. Work chapter by chapter, keep a running summary, and paste the relevant sections so continuity and voice stay consistent.
What are XML tags and why use them for writing?
XML tags like <draft>, <notes>, <samples>, and <brief> mark where each piece of your input begins and ends. They stop Claude from treating your source notes as instructions and make it easy to say things like "rewrite the text in <draft> using the voice in <samples>". Claude was trained to respect these tags, so they reliably improve control.
Should I use an Artifact for writing?
For anything you'll revise, yes. An Artifact puts the document in an editable panel beside the chat, so you can iterate on the same draft — "tighten the intro", "make section 3 punchier" — without Claude reprinting the whole thing each time. It's ideal for essays, posts, and reports you'll refine over several turns.
Can I use Claude's writing commercially?
The prompt text is free to use. Whether the output is cleared for commercial or published use depends on your Anthropic plan and Claude's usage policy, so check the terms tied to your account. Always fact-check claims, verify quotes and stats, and edit the draft into your own voice before publishing.