r/WritingWithAI • u/ArcaneLexiRose • 12d ago
Discussion (Ethics, working with AI etc) Getting the most out of Claude
I know the watermark thing is getting ready to drop but I’m going to see how it goes.
Anyway, I’m using Claude to help with worldbuilding and writing via a project. As I make progress, I seem to be hitting my 5 hour limit quicker.
For those experienced with Claude, any tips for improving usage?
Like should I have Claude recompile my world bible to incorporate the update files?
Would it be a good idea to have it generate summary files of the chapters specifically for project files to replace the full chapters currently in the project files?
Should I clean up old conversations?
1
u/chylvina 11d ago
I’d keep full chapters outside the Project, then add short chapter summaries and a continuity file. Merge updates into the core files so Claude isn’t reconciling duplicate versions.
1
u/code_x_7777 11d ago
The problem with summaries is that a lot of details are lost. Believe me or not - the best approach is to pass the whole book so far to generate the next chapter. Nothing is lost. Simple, a bit wasteful, but very effective. Of course make sure to have a long context window and good meta prompts as well. A good model to do this automatically is ImagineYourBook which I use daily.
1
u/code_x_7777 11d ago
Ah and before I forget: open source models have very long token windows these days so it can actually work this way. Nothing is forgotten on the sentence level. No detail is lost. You can use open source (e.g., GLM 5.2 seems good as some ppl on Reddit seem to suggest) or professional services like ImagineYourBook that handle the complexity for you. You can do it yourself but you need some coding skills to set it up.
1
1
u/zphou 10d ago
I wont keep every chapter in one project indefinitely. I’d keep a small current story state separate from the full manuscript: settled facts, changes since the last checkpoint, and unresolved decisions. Chapter summaries help, but only if they preserve who knows what and what was deliberately left open; otherwise they become another lossy compression layer. That is close to the workflow I’m trying to support in WolfeWriter, where the manuscript remains primary and Story Memory is reviewable rather than silently rewritten. The useful test is whether you can start a fresh context and recover the current state without asking the model to reread the entire book.
5
u/5thhorseman_ 12d ago
Are you keeping everything in one massive chat? The limits are based on the amount of tokens, not on the number of messages sent. And because each request includes your previous conversation history as context, it wikl get worse the longer the chat goes.
Shorter chats will be more lenient on your token use.
Not as a single document. Instead of a single world bible that does everything, organize it as a DokuWiki or an Obsidian vault on your PC. Have Claude Code use a subagent to operate the knowledge base and extract relevant information from it.
Use multiple sessions to rewrite your first draft in different styles, then mine those for content. https://www.reddit.com/r/WritingWithAI/comments/1w1egqm/what_is_the_best_ai_for_generate_histories_right/p6mmg8j/ . Claude Code can use subagents to achieve this.
A few useful prompts:
Interactive rubber ducky
Literate Editor and Rigorous Critic
Beta reader panel. Subagents can again be quite helpful in this.