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.

Use agent mode in vscode with sonnet or Claude code terminals and do an architectural decision record doc for each setup areas and all technical decisions. Ask more of your agent about your processes. Use context to your advantage and think not just of the product but also the docs as being the foundational context for the work.

undefined

[flagged]