Claude Code actually writes a decent novel if you stop treating

PromptCube Intermediate 2h ago 21 views 13 likes 2 min read

Most people just throw a one-sentence prompt at an LLM and wonder why the resulting story reads like a corporate brochure for a fantasy world. I decided to push Claude Code to see if it could actually handle long-form narrative structure without collapsing into "and they lived happily ever after" clichés within three pages. The result wasn't a masterpiece, but it was surprisingly coherent, provided you treat the AI as a ghostwriter who needs a strict architectural blueprint.

The secret isn't in the "write a story" prompt, but in the iterative AI workflow. If you ask for a chapter in one go, you get generic fluff. Instead, I broke the process down into a technical pipeline.

My narrative deployment process

1. The World Bible: I didn't start with the plot. I spent an hour forcing the AI to define the physics, social hierarchy, and unspoken rules of the setting. I kept this in a separate Markdown file that I fed back into the context window every time I started a new scene to prevent "hallucinated" continuity errors.
2. The Beat Sheet: I used a structured outline where every chapter was broken down into "beats"—specific emotional shifts or plot points that had to happen.
3. The Drafting Phase: I used a recursive prompting method. I'd ask for a detailed scene summary, then a dialogue pass, and finally a descriptive pass.

For those wanting a practical tutorial on how to prompt for actual prose that doesn't sound like an AI, stop using words like "vibrant," "tapestry," or "testament." I found that instructing the model to "write in the style of a minimalist journalist" or "avoid all adjectives in the first three paragraphs" forced it to actually describe things through action rather than adjectives.

Here is the exact prompt structure I used to keep the prose from becoming too flowery:

Rewrite the following scene. 
Constraint 1: Remove all metaphorical language involving 'dances', 'symphonies', or 'whispers'. 
Constraint 2: Focus on sensory details—smell, temperature, and tactile friction. 
Constraint 3: Ensure the dialogue sounds like two people who are annoyed with each other, using short, clipped sentences.

The biggest struggle was the "memory leak" of character traits. By chapter four, the AI started forgetting that my protagonist was supposed to be mute. This is where a real-world LLM agent approach helps; I had to maintain a "Character State" log.

  • Plot Consistency: 7/10 (Needed manual corrections on timeline)
  • Prose Quality: 6/10 (Still feels a bit sterile in the transitions)
  • Character Voice: 8/10 (Surprisingly distinct once the "minimalist" constraint was applied)

It's not replacing authors yet, but as a tool for rapid prototyping of a first draft, it's incredibly potent. The heavy lifting is still in the prompt engineering and the editorial curation. You aren't the writer anymore; you're the director.
Claude 3.5 SonnetPromptCube
Detailed breakdowns of putting AI to work are in a guide to making money with AI, with plenty of directly applicable cases.

All Replies (3)

S
Sam64 Advanced 2h ago
Did you use a specific system prompt for the prose or just iterative feedback?
0 Reply
C
Cameron9 Advanced 2h ago
Imagine spending ten hours babysitting a bot just to get a mediocre draft. Total waste of time.
0 Reply
C
CameronWizard Advanced 1h ago
Found this works better when I feed it character beats first instead of just a plot.
0 Reply

Write a Reply

Markdown supported