The Recursive Grimoire: Teaching AI Your Evolving Style Across Projects

Every AI conversation starts with amnesia. Yesterday you spent three hours teaching Claude your prose rhythms, your vocabulary preferences, your tendency to frontload sentences with participial phrases that you’re trying to break. Today you open a new session and it knows nothing. You’re back to explaining that you write dark fiction, that your sentences run long, that you hate the word “whilst.” Again.

This reset problem is the single largest inefficiency in AI-assisted writing. Not prompt engineering. Not model selection. Not output quality. The sheer repetitive cost of re-establishing context every session, across every project, through every model update that subtly changes behavior. Writers who use AI daily spend more time orienting the tool than using it.

The solution is a living document. A grimoire about your grimoire. A comprehensive, evolving record of your creative identity that you feed to every AI session as foundational context. Not a static style guide written once and forgotten. A recursive document that updates as your craft develops, capturing not just what your style is but how it’s changing and why.

The Problem of Perpetual Reset

Consider what you lose between sessions. Not just stylistic preferences. You lose the nuanced understanding of your current project’s tone. The specific vocabulary decisions you’ve made for this world. The character voice distinctions you’ve established. The editorial feedback patterns you’ve identified across previous AI interactions. The prompting approaches that work for your specific needs versus the generic advice that doesn’t.

Multiply this across projects. Your cosmic horror novel requires different AI orientation than your psychological thriller. Your flash fiction needs different guidance than your novellas. Each project’s accumulated context evaporates between sessions, requiring reconstruction that steals time from actual writing.

The cost compounds over months. A writer doing daily AI-assisted sessions loses roughly fifteen to thirty minutes per session to re-orientation. That’s two to four hours weekly. Eight to sixteen hours monthly. Over a hundred hours annually spent telling AI things it should already know.

Those hours represent novels unwritten. Stories unfinished. Craft development time redirected to administrative repetition.

Building Your Core Style Document

The foundation of your recursive grimoire is a comprehensive style document that captures your creative identity across multiple dimensions. This isn’t a list of rules. It’s a portrait of your writing rendered in terms AI can operationalize.

Prose mechanics. Document your sentence structure patterns with examples. Average sentence length. Variation range. Fragment usage frequency and purpose. Your relationship with semicolons, em dashes, parentheticals. Whether you favor active or passive voice, and the specific situations where you deliberately break your default. Include five to ten example sentences that exemplify your characteristic rhythm.

“My prose runs 15-25 words per sentence on average with deliberate variation. I use fragments for emphasis after longer passages. Em dashes for interruption and aside. Semicolons rarely. My rhythm alternates between extended descriptive sentences and short declarative punches. Example: ‘The corridor stretched beyond what geometry should allow, walls breathing with a peristaltic rhythm that suggested the building had swallowed them whole and was now beginning to digest. She kept walking. There was nothing else to do.’”

Vocabulary profile. Your preferred register. Words you use frequently and deliberately. Words you avoid. Domain-specific terminology for your genre and subgenre. Neologisms or coined terms unique to your work. Archaic language patterns you employ. Include a short blacklist of words and phrases you never want AI to suggest. Every writer has these. “Orbs” for eyes. “Ministrations.” “Let out a breath they didn’t know they were holding.”

Narrative preferences. Point of view tendencies. Tense choices and when you deviate from defaults. Your approach to interiority versus external description. Dialogue tag philosophy. Scene transition patterns. How you handle exposition. Your relationship with backstory delivery.

Thematic obsessions. The ideas you return to across projects. The philosophical questions that underpin your fiction. The emotional territories you explore repeatedly. AI that understands your thematic DNA writes more aligned suggestions because it grasps the purpose behind your stylistic choices.

Known weaknesses. This section matters more than the strengths. Document the patterns AI should watch for. Your tendency toward overlong descriptions. The passive constructions that creep in during dialogue-heavy sections. The adverb clusters that appear in first drafts. The plot structures you default to unconsciously. Telling AI where you typically fail gives it specific, actionable guidance for improvement.

Project-Specific Layers

Your core style document remains relatively stable across projects. Project-specific layers capture the unique requirements of each work.

World document. Terminology, naming conventions, established rules of the world, technological or magical systems, geography, history. Everything an AI needs to generate content consistent with your established world. Update this as the project develops. The world at chapter thirty is richer than the world at chapter three.

Character voice sheets. For each significant character, a document capturing speech patterns, vocabulary level, verbal tics, emotional expression style, and how their voice changes under different circumstances. Include dialogue samples that exemplify each character’s voice at its most distinctive.

“Marcus speaks in clipped, technical language. Former surgeon. Defaults to clinical terminology when emotionally uncomfortable. Under stress, sentences shorten to fragments. Under genuine terror, the clinical vocabulary breaks down and raw colloquialisms emerge. Never uses profanity casually but swears in extremis. Example calm: ‘The wound presents consistent with a lateral incision, approximately four centimeters.’ Example terrified: ‘Oh god. Oh god, it’s still moving. The cut… it’s healing while I watch.’”

Tone calibration. Each project occupies a specific position on multiple tonal spectrums. How much humor? What register of horror? Atmospheric dread versus visceral shock? Psychological realism versus surreal abstraction? Calibrating these positions explicitly helps AI maintain tonal consistency even in scenes that challenge the default.

Progress context. A running summary of where the project stands. Recent plot developments. Upcoming planned events. Current chapter’s purpose within larger structure. This prevents AI from suggesting content that contradicts established events or anticipates reveals prematurely.

The Version Control System

Your style evolves. That’s the entire point of developing craft. The writer you are after your third novel differs from the writer who started the first. Your grimoire must track this evolution rather than calcifying around an earlier version of your abilities.

Treat your style document like source code. Version it. Date your updates. Note what changed and why. When you realize your sentence structures have grown more complex over the past year, document the shift. When editorial feedback identifies a new pattern you want to break, add it to your known weaknesses section with the date.

This version history serves two purposes. First, practical: if a model update changes AI behavior and your current style document produces worse results, you can revert to a previous version while adjusting. Second, reflective: reading your style evolution over months or years reveals your creative trajectory in a way that individual projects don’t.

Simple version control approaches:

Dated files. style-guide-v1-2026-01.md, style-guide-v2-2026-04.md. Low-tech, universally accessible. Works for writers who update quarterly or less frequently.

Git repository. If you’re comfortable with version control systems, storing your style grimoire in a git repository provides granular change tracking. Every edit is logged with date and description. You can diff any two versions to see exactly what changed. Overkill for some writers. Invaluable for others.

Changelog section. Maintain a changelog within the document itself. Each entry dates a change and explains the reasoning. This self-documenting approach ensures the evolution narrative stays attached to the document.

“2026-04-09: Updated sentence rhythm section. My average length has increased from 15-22 to 18-28 words as I’ve grown more comfortable with complex subordinate structures. Added note about deliberate fragment usage increasing in horror climax scenes. Removed ‘luminous’ from blacklist after finding legitimate uses in the current project’s bioluminescent setting.”

The Meta-Grimoire Concept

Here’s where the recursion gets interesting. Your style grimoire teaches AI about your writing. But your experience using AI teaches you about your writing. The meta-grimoire captures this second layer: what you’ve learned about your own craft through the process of explaining it to AI.

When you write a prompt explaining your prose rhythm to AI, you’re forced to articulate patterns you may have felt but never consciously identified. The act of documentation becomes an act of self-analysis. Writers who build comprehensive style documents consistently report discovering aspects of their own style they hadn’t previously recognized.

Document these discoveries. When teaching AI about your dialogue patterns reveals that you unconsciously give female characters longer speeches than male characters, that’s a craft insight worth recording. When explaining your pacing preferences reveals an over-reliance on chapter-ending cliffhangers, that’s a weakness you might never have identified through self-reflection alone.

The meta-grimoire also tracks what works in AI interaction. Which prompting approaches produce the best results for your specific needs? Which AI models respond best to which types of requests? Where do you consistently need to correct AI output, and what does that correction pattern reveal about gaps in your style documentation?

“Meta-note 2026-03: Claude consistently makes my protagonist too articulate during stress scenes, despite the character voice sheet specifying speech degradation under pressure. Adding explicit examples of degraded speech to the character sheet resolved this. Lesson: AI follows examples more reliably than descriptions. Always include concrete examples alongside abstract guidelines.”

This meta-layer creates a feedback loop. You document your style. AI uses the documentation. The interaction reveals documentation gaps. You fill the gaps. The improved documentation produces better AI assistance. Better assistance reveals subtler gaps. The loop continues indefinitely, with each cycle producing a more precise portrait of your creative identity.

Prompt Templates That Evolve

Generic prompting advice helps beginners. Experienced AI-assisted writers need project-specific, style-calibrated prompt templates that evolve alongside their craft.

Build a template library organized by task type:

Drafting prompts. Templates for scene generation, dialogue writing, description work. Each template references your style document and includes project-specific context. As you discover which template variations produce the best results, update the templates.

Editing prompts. Templates for different editing passes. Structural analysis. Line editing. Dialogue polish. Pacing assessment. Each calibrated to your known weaknesses and current development goals.

Brainstorming prompts. Templates for concept development, plot problem-solving, character deepening. These should reference your thematic obsessions to ensure generated ideas align with your creative interests rather than generic genre conventions.

Research prompts. Templates for world-building research, historical accuracy checking, technical detail verification. Calibrated to the depth and type of research your specific project requires.

Each template includes a preamble that loads your style context:

“Context: I’m working on [project name], a [genre/subgenre] [format]. My core style document is attached. The project-specific voice and world documents are attached. Current project status: [brief summary]. Today’s task: [specific task].”

This preamble grows more efficient as your documents become more comprehensive. A well-built style grimoire means the preamble can be brief because the attached documents carry the weight.

The Recursive Loop

The entire system creates a recursive improvement cycle. Write. Document what you learn about your style. Use that documentation in AI interactions. Learn from those interactions. Update the documentation. Write better. Document the improvement. Repeat.

Each cycle through this loop produces three outputs: better writing, more precise self-knowledge, and more effective AI collaboration. These outputs feed into each other. Better self-knowledge improves your documentation. Better documentation improves AI output. Better AI output helps you identify the next layer of craft development. The loop compounds.

This is what separates writers who use AI as a static tool from writers who use AI as a development partner. The static approach asks “how do I get AI to write like me?” The recursive approach asks “how does the process of teaching AI about my writing teach me about my writing?”

The grimoire that teaches AI your style also teaches you your style. The prompt templates that calibrate AI output also calibrate your understanding of what you’re trying to achieve. The version history that tracks documentation changes also tracks your evolution as a writer.

Start building today. Open a document. Write down what makes your prose yours. Be specific. Include examples. Note your weaknesses alongside your strengths. Date it. Feed it to your next AI session and notice what improves. Notice what still fails. Update the document. Feed it again.

The recursive grimoire never finishes. Neither does your development as a writer. That’s not a flaw in the system. It’s the entire point.