edwmurph

One thing that's worked well for me is scattering agents.md files throughout the repo and loading the relevant ones based on what the agent is touching. It keeps architecture notes and local conventions close to the code, which works better than one giant project document.

I think that’s the key. Don’t hand over the thinking, use it as part of the loop. The more I use it, the better I get at knowing what to ask for, what to ignore, and when to take back control.

nice! this might replace the explainer i usually handout for this concept https://www.youtube.com/watch?v=8aGhZQkoFbQ but Vivix seems