not obvious to me why this is an improvement of having the agent just update the rule files directly itself; i have it do that to my various AI-targeted readme files and it works great.
Graphiti MCP can recall more than just preferences and coding styles. Application specifications and evolution of these may be stored. For any non-trivial application, config files would likely be a misfit for this use ase.
i store those in my rules files - really all the knowledge i would pass onto another engineer (incl. AI). not sure i follow why you would avoid putting that into AI-readable files in your repo like i do now.
Comments
not obvious to me why this is an improvement of having the agent just update the rule files directly itself; i have it do that to my various AI-targeted readme files and it works great.
Graphiti MCP can recall more than just preferences and coding styles. Application specifications and evolution of these may be stored. For any non-trivial application, config files would likely be a misfit for this use ase.
i store those in my rules files - really all the knowledge i would pass onto another engineer (incl. AI). not sure i follow why you would avoid putting that into AI-readable files in your repo like i do now.