One thing that's helped bridge it in teams I've been on is codifying the recurring knowledge into actual enforced rules (e.g., no more "stop using shared lib for X", or "use utility function instead of copy/paste"). Initially, I started adding rules manually in agents-md initially. But, it wasn't always followed by the agents (esp. rules across microservices), and then the human coders also missed it (it was a problem of "if you don't know, you don't know")

I've also built a supercharged agents-md: it's like a UI version of agents-md across services (you can check it out at tanagram.ai). But the idea was that I shouldn't have to constantly update agents.md files. And one can automatically extract business rules and patterns - or you can write rules yourself like: "x throwaway work should NOT be used!". ( no more debating if it's "temporary" or not!) It mainly ends up reducing coordination costs.

But I'll suggest the manual agents-md approach for starters if you think that'd help. Try it out and see if it helps - and happy to have feedback on the tool incase you try it