After 12 months of folk building YAMM (Yet Another Memory Model) how about properly documenting and commenting your code and just telling Claude to read the ****in’ docs like you would any other junior dev? Flippancy aside; this does actually work and it’s what a production code base should really have anyway in case you get hit by a bus at lunchtime and the system crashes in the afternoon. Add a structured docs folder to your project; this will hold the architecture, db structure, important models, service, client, etc. Add docstrings; or equivalent in your language, to all the interface methods. Claude can read these instead of deciphering the raw code Add a Claude.md to each project and have it refer to the docs folder. Claude will look stuff up when it needs to. Write a skill to keep the docs, docstrings and Claude.md files in sync; run this every time you’ve finished working on the code. That‘s it; your done; no more pissing about looking for the next panacea. Document your code and stop doomscrolling or that bus will get you ;-) submitted by /u/New_Goat_1342
Originally posted by u/New_Goat_1342 on r/ClaudeCode
You must log in or # to comment.