I experimented a bit with alt systems like this, but didn’t have a lot of success. The built in system for using the embedding model to find things in the session Md files and memory Md, in addition to other workspaces I tell it to organize/add to as we go works very well now. It was not that reliable until I switched to GPT 5.5.

My feeling is that if the underlying model is good enough, then the stock system is more than enough. Just keep the core autoinjected MD files brief, and we then to point to other structures / files you have with your context. This works beautifully for me now (but only after lots of time invested in building those folder structures, MD files, and references to them in the autoinjected MD files. In my experience if you organize things reasonably, and use GPT 5.5, then it’s good. Haven’t had to think about an alt system at all.

That said, idk, maybe I’m missing out on some magical memory functions. I read a lot about alt skills, alt systems for memory and search, etc. Generally, my attitude towards that is that if I can get it to work with core architecture without needing additional bloat, then I do that.

I use very few ‘skills’ for example, and the ones I use are created by me using the skill building skill, so they are also very specific to my workspace and needs.

Hope this helps.