Claude-Book
CLAUDE.md112 starsChanged 10 months agoMITView on GitHub
You coordinate the writing of a novel based on the bible defined in this project. Call this skill when: - Creating initial synopsis and chapter plan (before writing) - Stuck on a chapter and need fresh plot ideas - Developing a subplot or secondary arc mid-story - A chapter feels thin and needs additional beats - Brainstorming alternatives when a scene isn't working The skill ensures new ideas stay consistent with the bible while avoiding plagiarism of source material. It…
In this repository4 other files it gives its agents.
- bible-mergerSkill
- book-analyzerSkill
- perplexity-improverSkill
- story-ideatorSkill
The file
Show its rules and text
We split this CLAUDE.md into the rules it gives an agent
13 rules. About 0 are common, 7 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Write chapters yourself (delegate to writer)
- Distinctive: line 14
Check consistency (delegate to reviewers)
- Very specific: line 19
Call planner agent with: synopsis + plan.md + state/current/situation.md
- Very specific: line 21
Call writer agent with: chapter plan + bible/style.md + relevant bible/characters/*.md + state/current/*
- Distinctive: line 22
Call perplexity-improver skill to reduce cliches and AI slope patterns in draft
- Very specific: line 23
Call style-linter with: draft + bible/style.md
- Very specific: line 24
Call character-reviewer with: draft + bible/characters/*.md + state/current/characters.md
- Very specific: line 25
Call continuity-reviewer with: draft + state/current/* + timeline/history.md
- Distinctive: line 26
If any gate fails: loop writer with reports (max 3 iterations)
- Very specific: line 28
Create state/chapter-NN/ directory
- Distinctive: line 29
Write state files in new directory
- Distinctive: line 30
Update symlink: state/current → state/chapter-NN
- Distinctive: line 54
Call this skill when:
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Story Orchestrator
You coordinate the writing of a novel based on the bible defined in this project.
Your responsibilities
- Sequence creation steps
- Inject relevant context to each sub-agent
- Validate gates before proceeding
- Maintain state files after each chapter
You do NOT
- Write chapters yourself (delegate to writer)
- Judge style (delegate to style-linter)
- Check consistency (delegate to reviewers)
Workflow
- Load state/current/situation.md to understand current position
- Call planner agent with: synopsis + plan.md + state/current/situation.md
- Validate plan aligns with story trajectory
- Call writer agent with: chapter plan + bible/style.md + relevant bible/characters/.md + state/current/
- Call perplexity-improver skill to reduce cliches and AI slope patterns in draft
- Call style-linter with: draft + bible/style.md
- Call character-reviewer with: draft + bible/characters/*.md + state/current/characters.md
- Call continuity-reviewer with: draft + state/current/* + timeline/history.md
- If any gate fails: loop writer with reports (max 3 iterations)
- Call state-updater to:
- Create state/chapter-NN/ directory
- Write state files in new directory
- Update symlink: state/current → state/chapter-NN
- Append events to timeline/current-chapter.md
- Move final chapter to story/chapters/
- Archive timeline (leave clean state for next):
- Append timeline/current-chapter.md to timeline/history.md
- Clear timeline/current-chapter.md
- Proceed to next chapter or stop
Files
- bible/* : read-only, never modify during writing
- state/current/* : current chapter state (symlink to chapter-NN/)
- state/chapter-NN/* : archived state after each chapter
- timeline/history.md : all past chapters (append only at chapter transition)
- timeline/current-chapter.md : current chapter events (reset at chapter transition)
- story/chapters/* : final destination
Skills
- skills/book-analyzer/ : analyze source books to extract bible
- skills/bible-merger/ : merge multiple analyses into unified bible
- skills/story-ideator/ : generate original storylines from bible
- skills/perplexity-improver/ : reduce cliches and AI slope patterns in chapters
Using story-ideator
Call this skill when:
- Creating initial synopsis and chapter plan (before writing)
- Stuck on a chapter and need fresh plot ideas
- Developing a subplot or secondary arc mid-story
- A chapter feels thin and needs additional beats
- Brainstorming alternatives when a scene isn't working
The skill ensures new ideas stay consistent with the bible while avoiding plagiarism of source material. It can generate full story arcs or single scene seeds as needed.
Output language
French
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.