// book 40
patriola.com

Book 40 · Patriola’s Guide to Claude

Writing Fiction with Claude


Preserve your voice in AI co-writing. A voice document, a session architecture, and a vocabulary engineering layer that keep your signature intact through the generation pass.

Buy Ebook on Amazon

Patriola's Guide to Claude — Writing Fiction: Preserve Your Voice in AI Co-Writing
What this book is

The dead-chapter problem is an anchoring problem

Most fiction written with Claude sounds like Claude wrote it. The chapters are competent, the sentences are grammatical, the dialogue moves — but the voice is gone, every chapter landing in the same measured, slightly formal, hedged register. If you've used Claude on a novel and gone back to read it cold, you know the feeling: the prose is dead, and it kept none of you.

That is not a Claude problem. It's an anchoring problem. Claude has no idea what your voice sounds like unless you show it, in detail, before every session. This book is about building that anchor: a voice document extracted from your own real prose, a session architecture that loads it reliably, and a vocabulary engineering layer that makes sure your signature words and rhythms survive the generation pass intact.

The book walks through a complete fiction workflow: opening a novel-scale project, anchoring the session, co-writing a chapter, running the quality pass, and closing without losing state. Every worked example is drawn from real manuscript work — nothing here is hypothetical. The session architecture section covers long-project management specifically: how to maintain coherence across dozens of sessions without rereading the entire novel before each one.

What you’ll learn

Building the anchor, chapter by chapter

  • Voice extraction — pulling pattern from real manuscript samples into a document Claude can actually use.
  • Session construction — what belongs in the system prompt, what belongs in the context window, and what belongs in the working file.
  • Character continuity — tracking arcs and history so Claude doesn't contradict chapter 3 in chapter 17.
  • Vocabulary engineering — building a suppression list from your own manuscript patterns to catch the filler phrases and tells that come back no matter how good the prompt is.
  • The quality gate — flagging AI tells before they reach a human reader.
  • Long-project session architecture — maintaining coherence across dozens of sessions without re-reading the whole novel each time.
From the book

A preview

The prose is dead. It kept none of you. That is the tell that something in the anchoring — not the prompt, the anchoring — has failed.
You Chapter 12 needs to sound like me, not like generic competent prose. What's actually missing from how I'm prompting this?
Claude A prompt describes what should happen in the scene. It doesn't show me the texture of your sentences — where you clip, where you let a sentence run, which words you reach for and which ones you'd never use. Without a voice document built from your own prose, I default to a safe, generic register, because that's the only one I have to fall back on. Show me the pattern once, load it every session, and the difference isn't subtle.
Who it’s for

Fiction writers with a project already in progress

This book is for fiction writers who want Claude as a genuine co-writer without losing their voice in the process. It assumes you already write — this is not an introduction to fiction craft. The technical bar is low, but the creative bar is high: you need a real manuscript sample to anchor from. Readers who want the full AI-tell removal method in depth should pair this book with Book 6, Removing AI Tells.

A longer excerpt is available to newsletter subscribers.

Buy Ebook on Amazon

Stay current

New books in this series

One short email per book launch.