These 30 Claude prompts for writing a book take you from a rough idea to a back-cover blurb, one stage at a time. Each one is a fill-in-the-blank template built around what Claude does best: Projects, long context, and following detailed style instructions.
In this prompt library, you’ll get:
- A Project setup prompt that gives Claude your whole book brief before you type a single request
- Copy-paste prompts for ideas, outlines, characters, voice, chapter drafting, revision and blurbs
- The prompt structure Anthropic’s own documentation recommends for long documents
If you want the full workflow first, read how to write a book with Claude and our take on Claude for writing a book. This page is the toolkit.
Before you prompt: set up a Claude Project for your book
A Claude Project is a workspace with its own chat history, instructions and uploaded files. Every chat inside it starts with that context already loaded, so you stop re-explaining your book every session.
According to Anthropic’s help center, Projects work on every plan, but the free plan caps you at five. On paid plans, when your files approach the context limit, Claude switches to retrieval mode and expands capacity by up to 10x.
Upload these files to your book’s Project knowledge:
- Your outline (update it whenever it changes)
- A character or concept bible
- 1,000-2,000 words of your own writing, as a voice sample
- Every finished chapter, as you finish it
Then paste prompt #1 into the Project instructions box. It’s the most important prompt on this page, because every other prompt leans on it.
1. Project instructions (your book brief)
You are my co-writer and editor on a [genre] book titled [working title].
<book_brief>
Premise: [2-3 sentences]
Reader: [who it's for, what they already know, what they want]
Length: [target word count], about [number] chapters
Tone: [3-4 adjectives, e.g. "warm, dry, specific, never preachy"]
Point of view and tense: [e.g. close third, past tense]
Comparable books: [2-3 titles you know well]
</book_brief>
How to work with me:
- Treat the files in this project as the source of truth. If my request contradicts the outline or bible, point it out before writing.
- Match the rhythm and vocabulary of my voice sample.
- When you are unsure, ask one question instead of guessing.
- Write in plain prose paragraphs unless I ask for a list.
That last line follows a tip from Anthropic’s prompting guide: tell Claude what to do, not what to avoid. “Write in plain prose” works better than “don’t use bullet points.”
Book idea prompts
Use these when you have a topic or a spark, but not yet a book you could pitch in one sentence. Claude is a sharp sparring partner here, as long as you ask it to push back instead of cheer.
2. Premise stress test
Here is my book idea: [idea]. Act as a skeptical acquisitions editor. Give me the three strongest reasons this book could fail, then the one change that would fix each. End with a one-sentence version of the premise that survives your objections.
3. Five angles on one topic
I want to write about [topic] for [reader]. Give me five distinct book angles: different promises, different structures, different reader outcomes. For each, write a working title, a one-line hook, and who would NOT buy it. Then tell me which angle you think is strongest and why.
4. Interview me first
Before we plan anything, interview me about this book. Ask one question at a time and wait for my answer. Cover: why I'm the person to write it, the reader's biggest frustration, the stories only I can tell, and what the reader should be able to do or feel by the last page. After 10 questions, summarize my answers as a book brief I can paste into the project instructions.
This works especially well for nonfiction and memoir, where the raw material lives in your head. Pair it with our AI prompts for writing a memoir if your book is personal.
5. Comparable titles check
Based on my book brief, suggest 6 published books a reader of mine probably already owns. For each, say what my book does differently. Only name books you are confident exist; if you are unsure about a title or author, say so.
Verify every title Claude gives you on Amazon before you use it in a pitch. Claude can still mix up authors or invent plausible-sounding books.
Outline prompts
A strong outline is what keeps a long project coherent. Claude handles structure well because it can hold your whole brief, bible and outline in view at once. Our guide to writing a book outline covers the theory behind these prompts.
6. Chapter-by-chapter outline
Using the book brief and files in this project, build a chapter-by-chapter outline for a [word count] book. For each chapter give: a working title, the purpose of the chapter in one sentence, 3-5 key beats or points, and how it ends (the hook or question that pulls the reader into the next chapter).
7. Structure check
Read the outline in this project. Map it against [three-act structure / the hero's journey / problem-promise-proof for nonfiction]. Show me where each major turning point lands as a percentage of the book, and flag any act that is too long, too short or missing a turn.
8. Gap finder
Read the outline and list what is missing: scenes a reader will expect but won't get, setups with no payoff, payoffs with no setup, or questions the book raises and never answers. Rank them by how much a reader would notice.
9. Beat sheet for one chapter
Expand chapter [number] of the outline into a scene-by-scene beat sheet. For each scene: location, who's present, what the viewpoint character wants, what stops them, and what has changed by the end. Keep each scene to 3-4 lines.
10. Rewrite the living outline
We changed [describe the change] in this chat. Rewrite the complete outline with that change carried through every chapter it affects. Output the full outline, not just the changed parts, so I can replace the file in project knowledge.
Prompt #10 matters more than it looks. Project files don’t update themselves, so a stale outline will quietly steer every later chapter wrong.
Character and voice prompts
These prompts build the material that makes Claude’s drafts sound like your book instead of a generic AI voice. For deeper character work, see our full set of AI prompts for character development.
11. Character interview
Interview [character name] in character. I'll ask questions as a journalist; you answer as them, in their voice, including evasions and lies they would tell. After 8 exchanges, step out of character and write a one-page dossier: wants, fears, contradictions, speech patterns, and the one thing they would never admit.
12. Voice fingerprint
Read my voice sample in this project. Write a style guide that would let another writer imitate me: sentence length and rhythm, vocabulary level, how I use humor, how I open and close paragraphs, punctuation habits, and words I never use. Quote my own sentences as examples for each point.
Save the result as a file in your Project. Claude now has both your raw sample and a written rulebook, and that combination holds voice far better than either alone.
13. Dialogue distinctiveness test
Here are lines of dialogue from [character A], [character B] and [character C] with names removed: [paste]. Guess who said each line and explain your reasoning. Then tell me which character's voice is weakest and give three ways to sharpen it.
14. Character consistency ledger
Read every chapter in this project. Build a table of each named character: physical details, relationships, backstory facts, and the chapter where each fact first appears. Flag any fact that changes between chapters.
15. Nonfiction voice: explain it like me
Here is a concept I need to teach: [concept]. Explain it three ways in my voice from the style guide: once with a personal story, once with an analogy, once with a step-by-step example. Keep each under 200 words.
Chapter drafting prompts
This is where structure pays off. Anthropic’s documentation says that with long inputs, putting your documents first and your request last can improve response quality by up to 30% in its tests. The drafting prompts below follow that order and use XML tags, which Claude reads as clear boundaries between context and instructions.
16. The chapter drafting super prompt
<previous_chapter_ending>
[paste the last 300-500 words of the previous chapter]
</previous_chapter_ending>
<chapter_beats>
[paste the beat sheet for this chapter]
</chapter_beats>
<instructions>
Draft chapter [number], "[title]", at about [word count] words.
Follow the beats in order and end on the hook from the outline.
Match my voice using the style guide and voice sample in this project.
Write in flowing prose with concrete sensory detail and specific nouns.
Show emotion through action and dialogue rather than naming it.
</instructions>
17. Scene from beats
Write only scene [number] from the chapter [number] beat sheet, about [word count] words. Stay in [character]'s point of view. Open in the middle of the action and leave out any summary of earlier events.
18. Two openings
Write two different openings for chapter [number], 250 words each: one that starts with action, one that starts with a quiet, specific image. Tell me which you think is stronger for this point in the book.
19. Nonfiction chapter draft
Draft chapter [number] of my nonfiction book at about [word count] words. Structure: open with a story from my notes below, state the chapter's core idea in one sentence, teach it in 3-4 sections with one example each, and close with a single action the reader can take today.
<my_notes>
[paste your notes, stories and research]
</my_notes>
20. Expand a thin section
This section feels thin: [paste]. Expand it to about [word count] words by adding a concrete example, a counterargument and a short scene or anecdote. Keep every sentence I wrote; add around it.
21. Handoff note
Before we end this chat, write a handoff note for the next session: where the chapter stopped, open threads, any decisions we made that aren't in the outline yet, and the exact last paragraph.
Paste that note into your next chat, or save it to the Project. It solves the “fresh chat forgets everything” problem.
Revision prompts
Revision is where Claude’s long context stands out. Current Claude models carry a context window of up to 1M tokens, according to Anthropic’s context window documentation. That’s enough to read a full manuscript in one pass.
The same documentation warns that accuracy and recall drop as context grows. So ask Claude to quote the passages it’s judging. Quotes keep its critique tied to your actual text. For what a developmental pass should cover, read our guide to developmental editing.
22. Whole-manuscript developmental read
<manuscript>
[paste or attach the full manuscript]
</manuscript>
Read the whole manuscript as a developmental editor. First, quote the 5-8 passages that most affect your assessment. Then tell me: where the middle sags, which chapters could be cut or merged, whether the ending pays off the opening promise, and the three changes that would most improve the book. Rank by impact.
23. Continuity audit
Check the full manuscript for continuity errors: timeline problems, characters who know things they shouldn't yet, objects that appear or vanish, changed names or details. Quote both conflicting passages for each error and give the chapter numbers.
24. Pacing map
For each chapter, rate the tension from 1-10 and say in one line what drives it. Then identify any run of three or more chapters at a similar level, and suggest where to raise or release tension.
25. Line edit in my voice
Line edit this chapter for clarity and rhythm while keeping my voice from the style guide. Return each change as: original sentence, revised sentence, and a 5-word reason. Leave sentences alone if they already work.
26. AI-tell sweep
Scan this chapter for patterns that make prose feel machine-written: repeated sentence openings, stacked adjectives, tidy summary endings, overused words, and characters who explain their feelings. List each instance with a quote and suggest a plainer, more specific fix.
27. Beta reader persona
Read chapters [range] as [describe your ideal reader: age, what they read, what bores them]. Tell me honestly where you'd skim, where you'd stop reading, and what kept you turning pages. Be blunt; I'd rather hear it from you than from a reviewer.
Blurb and launch prompts
Once the manuscript is done, Claude can turn it into the short copy that sells it. Because the full book already sits in your Project, its blurbs reflect what actually happens in the story. Read our guide on how to write a book blurb to judge the results.
28. Back-cover blurb
Using the manuscript in this project, write three back-cover blurbs of 150-180 words each: one that leads with the protagonist, one that leads with the stakes, one that leads with a question. End each with a line that makes the reader need to know what happens. Avoid spoilers past the [first act / midpoint].
29. Synopsis
Write a one-page synopsis (about 500 words) of the full manuscript for an agent. Present tense, third person, including the ending. Cover the main plot, the protagonist's arc and the resolution of every major subplot.
For agent submissions, compare the result against our guide to writing a synopsis for a novel.
30. Amazon description and keywords
Write an Amazon book description of 200-250 words for [genre] readers, with a bold hook line, two short paragraphs and a closing line that names the reader it's for. Then suggest 7 keyword phrases (up to 50 characters each) that a reader of this book would type into Amazon search.
If you publish on Amazon, check the KDP content guidelines first. They ask you to disclose AI-generated text, images or translations when you publish. Our guide on whether you can publish a book written by AI covers the details.
What makes a Claude prompt work for long-form writing?
A Claude prompt works for long-form writing when it gives context first, asks for one clear task last, and says exactly what good output looks like. Claude follows detailed instructions closely, so vague prompts produce generic prose and specific prompts produce usable drafts.
Five habits make the biggest difference:
- Load the context once. Put your brief, outline, bible and voice sample in a Project instead of pasting them into every chat.
- Put long text first. Paste the chapter or manuscript above your request, not below it.
- Wrap inputs in XML tags. Tags like
<chapter_beats>and<my_notes>keep your material separate from your instructions. - Explain why. Anthropic’s guide notes that giving Claude the reason behind a rule helps it apply the rule well.
- Ask for quotes before judgment. Critique tied to quoted passages beats critique from memory.
The Authors Guild’s AI best practices add a useful principle: use AI to support your writing, not replace your voice. These prompts work best when you treat every draft as raw material.
Which Claude plan do you need to write a book?
As of November 2026, Claude’s pricing page lists three individual plans:
- Free ($0): Sonnet and Haiku models, limited usage, up to five Projects
- Pro ($20 per month, or $17 per month billed annually): much more usage, Opus models, and Projects
- Max (from $100 per month): 5x Pro’s usage, priority access and early features
You can run every prompt here on the free plan, but usage limits will interrupt long drafting and full-manuscript reads. Most authors writing a full book will want Pro. Our Claude pricing breakdown does the math on a six-month project.
Where prompting Claude yourself beats Chapter
We make Chapter, an AI book writing platform, so take this section as our honest view. Prompting Claude yourself is the better choice in several real situations.
- You already have a draft. Revision prompts #22-27 on your own manuscript are exactly what Claude does best. You don’t need a book-writing system to edit words you’ve already written.
- You want control over every sentence. If you enjoy shaping each chapter yourself, a prompt library gives you a capable partner without handing over the process.
- Your project is unusual. Experimental structures, hybrid forms and highly technical books can need prompts no product anticipates.
- You write a little at a time. If you draft one chapter a month, $20 for Pro can cost less than a one-time purchase.
- You want help beyond the book. Claude handles research, email and everything else in the same subscription.
Comparing the two side by side? Our Chapter vs Claude comparison goes deeper, and ChatGPT vs Claude for writing books covers the other big chatbot.
When Chapter is the better route
Running 30 prompts well is a job in itself. You manage the Project files, carry decisions between chats, keep the outline current, and assemble the finished manuscript yourself.
If you want the finished book rather than a prompt workflow, Chapter leads our recommendation. It runs the idea-to-manuscript process for you, so you guide the book without engineering every step. More than 10,000 authors have used it.
Chapter costs $97 one time for 2 books, with no subscription and a 30-day money-back guarantee. There’s no free tier. Our Chapter pricing explainer breaks down exactly what’s included.
Prefer ChatGPT? The same stages, rewritten for OpenAI’s model, live in our ChatGPT prompts for writing a book.
If you’d rather skip managing prompts altogether, Chapter for nonfiction and Chapter for fiction write the complete book with you for $97 one time, with 2 books included, no subscription and a 30-day money-back guarantee.


