I will say, having built something similar for tracking 'memory' and items at home, it can quickly consume your tokens when dealing with both reading and updating, keeping stale info relevant etc.. when the amount of data starts to grow. Smaller tasks can balloon in their token cost as documents a read, updated, collated, refreshed etc..
however, I have found keeping a good solid reference to my home infrastructure, services, ci/cd setup, hosts, storage , networking etc.. really works wonders as a set of 'memories' to share across projects that I expect to be tested / deployed / acceptance tested etc.. using the home infra bits and pieces.
For everything I touch, infrastructure is in code.
People take things a little too literally and absolute on the internet. I'm more posting like this as a push back from the absolutely insane amount of documentation, plugins/skills, decision docs, and other bs I'm seeing in my professional life and being shared online.
I even said in my original comment in here that I still do have AGENTS/CLAUDE.md files. I've just trimmed them.
There's documentation where I work. I'd say I even made up about 5-10% of the documentation on our knowledge base (pre-llm). But now our knowledge base is mostly useless because every eng/dev is creating so much fucking documentation. A lot of it trash LLM generated.
however, I have found keeping a good solid reference to my home infrastructure, services, ci/cd setup, hosts, storage , networking etc.. really works wonders as a set of 'memories' to share across projects that I expect to be tested / deployed / acceptance tested etc.. using the home infra bits and pieces.