This is such a great idea. When I'm building net-new projects, I typically end up working with the AI assistant to build a comprehensive AGENTS.md as the first thing before any work gets done: specify tools, dependencies, architecture requirements, style, etc.
I end up getting way better quality.
The same is true for existing projects, but it always takes a whole lot longer as I'm typically chatting with my AI assistant to figure out what conventions are there that I forgot, etc., before building an AGENTS.md to make future changes simpler.
Thank you!
The idea is that static analysis can recover most of the mechanical truth of a repo (stack, commands, layout), and then you can layer intentional constraints on top if you want. If this saves even a few of those back-and-forth setup chats, it’s doing its job.
Feel free to contribute if you find the right fit
This is such a great idea. When I'm building net-new projects, I typically end up working with the AI assistant to build a comprehensive AGENTS.md as the first thing before any work gets done: specify tools, dependencies, architecture requirements, style, etc.
I end up getting way better quality.
The same is true for existing projects, but it always takes a whole lot longer as I'm typically chatting with my AI assistant to figure out what conventions are there that I forgot, etc., before building an AGENTS.md to make future changes simpler.
Love how this takes care of that.
Thank you! The idea is that static analysis can recover most of the mechanical truth of a repo (stack, commands, layout), and then you can layer intentional constraints on top if you want. If this saves even a few of those back-and-forth setup chats, it’s doing its job. Feel free to contribute if you find the right fit