So my app is scaling and getting bigger and I want to find the best approach to track everything, and make sure Claude knowns what has been done, why, and how to implement new features, all while keeping the tokens usage low. This is my approach right now: I use Claude Chat for brainstorming and generating prompts for Claude Code, I’m using a project and Chat reads the CLAUDE.md from the Github repo so I hope they’re aligned. Code does only the operational part, not the brainstorming, but I also use Plan Mode to make sure he follows the prompt. I’m trying Obsydian with the LLM Wiki approach in order to build a knowledge base: every Code session gets saved to a .md file, then I have a command to compile them that I run once in a while (it uses a lot of tokens). Rn the wiki is not really human readable so I don’t really know what’s in there, if it’s helpful and if he’s using it or not. I also installed Graphify to map the codebase, and it runs automatically every commit. Here too, I’m not really sure it’s helpful. Since I started using this approach, Code hasn’t duplicated code, rewritten existing parts, or applied inconsistent logic across the same section anymore, so I guess it’s working. But it still takes just a couple of messages in a long chat, or a couple of prompts, to burn through 20% of my 5-hour session. Is my approach overkill? submitted by /u/Brilliant_Lobster349
Originally posted by u/Brilliant_Lobster349 on r/ClaudeCode
You must log in or # to comment.