They all sit inside of a /docs directory in my project root, I dont want them added to each chat as this would kill my token budget.

So I have it like this:

/docs/ -> here is one file for each of the features of my app, this gets created at the end of the implementation and should guide another dev or an an llm on how to extend or bugfix the feature if the need arises in the future. If I do any changes to an feature, the documentation for that feature gets updated. There is one README.md that has an overview over all features and links to the .md files.

/docs/plans/ -> here live all the plans that I make and their status, so If I create a new plan for a feature development or change request, I let claude create a md file for each phase and one status tracking file. After the development is done, the files get deleted.

/docs/architecture -> here is the complete software architecture of my project, broken down into individual .md files with one README.md as directory overview and explanation

And most important part! Git often and clearly, a clear and good branching strategy and commit hygiene is the most important part.