Claude Projects for Authors: Write a Whole Novel With AI
Free Guide A Niche Raiders course for AI authors

Claude Projects for Authors

Learn how to use Claude Projects to write a whole novel with AI, with your characters, world, and plot kept consistent from the first chapter to the last. A free step-by-step guide. Jump to any section from the list on the right.

Part 01

What Claude Projects Are (and Why Authors Need Them)

If you have tried to write a novel with AI, you already know the frustration: you build a rich world and a cast of characters in one chat, and the next time you open Claude it has forgotten all of it. Eye colors change. The timeline drifts. Your hero's sister gets a new name. The story slowly falls apart.

Claude Projects are the fix. A Project is a container that holds all the chats for one book, plus a shared knowledge base and a set of standing instructions that Claude remembers across every chat inside it. Instead of re-explaining your story over and over, you set it up once, and Claude draws on it automatically every time you write.

For a fiction author, that is the difference between a pile of disconnected chats and a single organized writing room where your whole novel stays consistent. It is the single most important habit for writing a long, coherent book with AI.

What a Project gives you

  • Project knowledge: a shared library of files and notes (your story bible, outline, and summaries) that every chat can see.
  • Custom instructions: standing directions for how Claude should write for you, applied to every chat in the Project.
  • Organized chats: each chapter or scene is its own chat, but they all share the same memory.
Heads up: Claude Projects are part of the paid Claude plans (Pro, Max, Team, and Enterprise). The free plan does not include them. Pro is around twenty dollars a month and is plenty for writing a novel.
Part 02

Create Your Book Project

Setting up a Project takes about a minute, and you make one per book.

  1. Open Claude at claude.ai and look for Projects in the sidebar.
  2. Click to create a new Project and name it after your book, or simply "My Novel" if you do not have a title yet.
  3. Add a short description so future-you remembers what it is (genre, point of view, the one-line premise).

That is the whole setup. From now on, every chat for this book lives inside this Project. The next two sections are where the real power comes from: project knowledge and custom instructions.

Tip: One Project per book keeps things clean. Resist the urge to write three different stories inside one Project, because the shared knowledge would blur together and confuse Claude.
Part 03

Project Knowledge: Your Story Bible

Project knowledge is the shared library that every chat in your Project can read. This is where your story bible lives, and it is what keeps your novel consistent. Whatever you put here, Claude can draw on without you pasting it again.

What to upload

  • Your story bible: logline, character sheets (names, ages, looks, wants, wounds), world details, and a timeline.
  • Your outline: the chapter-by-chapter or beat-by-beat plan for the book.
  • A running story-so-far summary: a short recap of what has happened, which you update as you draft. This is the secret to long-book consistency.

You can add these as uploaded files or as pasted text. Keep each document focused and clearly labeled (for example, "Characters," "World," "Outline," "Story So Far") so Claude can find the right information fast.

You do not need all of this on day one. Add to your project knowledge as you build the book over the next few writing sessions. By the time you are drafting chapters, your story bible will be doing the heavy lifting of keeping everything straight.
Tip: Update the story-so-far summary every few chapters. A current summary in project knowledge is the single biggest thing that stops Claude from contradicting earlier events as your book gets longer.
Part 04

Custom Instructions: Lock In Your Style

Custom instructions are standing directions that apply to every chat in the Project. Set them once and Claude follows them every time, so you stop repeating yourself and your whole book keeps a consistent style.

What to include

  • Point of view and tense: for example, third person limited, past tense.
  • Genre and tone: the kind of book and the feel you want.
  • Voice and style rules: sentence rhythm, words to favor or avoid, and any hard rules (for example, no clichés, no over-explaining emotion).
  • What Claude should hand you: clean prose only, no commentary, formatted ready to paste into your manuscript.

Here is a starting template you can paste into your Project instructions and adjust:

Project instructions
You are my fiction writing partner for this novel. Write in third person limited, past tense. The genre is [your genre] with a [tone, e.g. warm, fast-paced, emotional] feel. Always use the characters, world, and timeline from the project knowledge, and never contradict the story-so-far summary. Write in clear, vivid, modern prose. Favor short, punchy sentences for tension. Show emotion through action and detail rather than naming it. Avoid clichés and stock phrases. When I ask for a scene or chapter, return clean finished prose with no notes or commentary, ready to paste into my manuscript.
Tip: If you have a sample of writing in the voice you want, capture it as a short style sheet and add it to your instructions. The closer your instructions describe your voice, the less editing you will do later.
Part 05

How to Actually Write Inside a Project

With your knowledge and instructions in place, the writing rhythm is simple and repeatable.

  1. Start a new chat inside the Project for each chapter or scene. Name it ("Chapter 3") so you can find it later.
  2. Tell Claude what this scene needs to do. Point to the outline beat and any characters involved. Claude already has the context from project knowledge.
  3. Draft, react, revise. Read what it gives you, keep what you love, and ask for changes ("more tension here," "make her angrier," "cut this part").
  4. Update your story-so-far summary in project knowledge when the chapter is done, so the next chat knows what happened.
Prompt
Using the characters, world, and outline in the project knowledge, write the next scene. It covers this beat from my outline: [paste the beat]. It should be from [character]'s point of view, run about [word count] words, and end on [the moment or hook you want]. Keep it consistent with everything in the story-so-far summary.

Because every chat shares the same project knowledge and instructions, chapter twenty stays just as consistent as chapter one. That is the whole promise of writing in a Project.

Part 06

Keeping a Whole Novel Consistent

The longer your book gets, the more details there are to keep straight. A few simple habits inside your Project will keep continuity airtight.

  • Keep the story-so-far summary current. This is your number one defense against contradictions. Update it as you go.
  • Use Claude to check itself. Ask it to flag inconsistencies against your story bible.
  • Keep character sheets updated. When a character changes (a new scar, a secret revealed), update the sheet in project knowledge.
Prompt
Here is my latest chapter. Check it against the character sheets, world details, timeline, and story-so-far summary in the project knowledge. List any inconsistencies or contradictions you find (wrong eye color, a timeline that does not add up, a character knowing something they should not yet know). Just list them, do not rewrite anything.
Tip: Run that consistency check every few chapters, not just at the end. Catching a continuity slip early saves you a painful tangle later.
Part 07

Habits, Limits & Good Practice

A few final pointers to get the most out of Claude Projects as an author.

  • One book, one Project. Keep stories separate so their knowledge does not blur.
  • Keep knowledge tidy. A few clear, well-labeled documents beat one giant messy file.
  • You are still the author. Always read what Claude gives you and have an opinion. Keep what you love, change what feels off. The story is yours.
  • Back up your work. Keep your manuscript and story bible saved outside Claude too, in your own documents or cloud storage, so nothing lives in only one place.
Want this done for you?

The Niche Raiders plugins build story bibles, outlines, and consistent drafts for you, on top of everything you just learned. See them on the plugins page, or join the community of AI authors over on Skool.

FAQ

Frequently Asked Questions

Do I need a paid Claude plan to use Projects?

Yes. Claude Projects are available on the paid plans (Pro, Max, Team, and Enterprise). The free plan does not include Projects. Pro is around twenty dollars a month and is plenty for writing a novel.

Can Claude write a whole novel inside one Project?

Yes. You keep one Project per book and write each chapter or scene as its own chat inside it. Every chat shares the same project knowledge and instructions, so your characters, world, and style stay consistent across the entire book.

What should I put in project knowledge?

Your story bible (logline, character sheets, world details, timeline), your outline, and a running story-so-far summary that you update as you write. These give Claude the context it needs to keep your novel consistent.

Will Claude remember my characters between chats?

Within a Project, yes, as long as the details live in your project knowledge. Claude draws on the shared knowledge and custom instructions in every chat inside that Project, so you do not have to re-paste your characters each time.

How is a Project different from a normal Claude chat?

A normal chat forgets everything once you start a new one. A Project is a container that holds many chats plus a shared knowledge base and standing instructions, so all the work on your book stays organized and consistent in one place.