I stopped trying to load a lot into my CLAUDE.md and instead created a marketplace of plugins. I have a personal settings plugin that helps sync and manage setting.gain and my status command line and my user level rule files. It also sets the precedent for how to format project level CLAUDE.md files and project rules. I then have another plugin that holds my model centric agents and a hook that helps decide to which to use. The primary bulk of my plugins are a core plugin that covers all of our studios core packages with skills while bespoke and standalone packages get their own plugin with skills in order to allow selective use of the packages that may or may not be relevant. There is also a skills and workflow related plugin for our bash environment, conventions, and studio mounts and paths. I used the plugin dev tools to help enforce structure and design to remain efficient with routing descriptions that Stay concise. So far this has actually worked quite well, but I do find some of the routing or the ability to automatically use the skills without reminders is tough. I’m trying to keep my context overhead low while having institutional knowledge loaded on demand, I’m curious if anyone else is working this way and has any recommendations? Basically I install and update my own market place and And then I use superpowers for planning and execution. I do occasionally use nested Claude files with short information that indexes the contents of code modules to help the agents retain the right understanding of the code when working in those sections. TLDR, using plugins with minimal rules and concise Claude.md with a few hooks vs large Claude.md having trouble getting skills to be automatically selected without reminders. submitted by /u/BaddyMcFailSauce
Originally posted by u/BaddyMcFailSauce on r/ClaudeCode