I just have a /fix-github-issue command that tells Claude to fix issue #xx with some extra definition of done stuff (test + build + update docs before finishing).
I also have a few other /commands for preparing and labeling issues.
Documentation by itself isn't useful (the human-readable kind), but for larger projects it's really useful to have a tree-style description on what is in each directory and a short description on where everything is in general. And this file is specifically LLM-optimised without any extra prose or formatting.
For larger projects you're wasting context if the LLM has to poke around in the dark and guess based on file/class names where everything is.
I just have a /fix-github-issue command that tells Claude to fix issue #xx with some extra definition of done stuff (test + build + update docs before finishing).
I also have a few other /commands for preparing and labeling issues.
Documentation by itself isn't useful (the human-readable kind), but for larger projects it's really useful to have a tree-style description on what is in each directory and a short description on where everything is in general. And this file is specifically LLM-optimised without any extra prose or formatting.
For larger projects you're wasting context if the LLM has to poke around in the dark and guess based on file/class names where everything is.