What is the best way to provide project metadata that would then influence agentic behavior within the project? E.g., if I’m working on a project which is not yet released to users in the wild, it isn’t as important to ensure backwards compatibility when refactoring code. I’ve found the agents typically overweight maintaining compatibility over generating clean code, so the refactor is often littered with conditionals checking for old map key names, old parameter names, etc so that legacy callers will still work. However, when working on a “supported” codebase, such backwards compatibility may be crucial.
I understand that it’s possible to define project specific rules, but it might be nice to be able to select into rule families based on project metadata. I also realize this can quickly get complicated, as we’re starting to delve into creating taxonomies of project types. However, this complexity can be put on the user by exposing a mechanism to compute the active ruleset and providing a default implementation that (for example) allows enable/disable of individual rules based on exact or prefix string matching against project metadata attributes.
If that’s too complicated, at least some mechanism to trigger local/project rules-file generation from dependencies, at appropriate times (startup?)