Project Documentation
The docs/ folder, the Documentation tab, and the rules the agent follows when it writes into them.
Every project has a docs/ folder next to frontend/ and backend/. It is part of the repository, so documentation is versioned with the code and travels with a clone, an export and a publish — the documentation of a release is the documentation that shipped with it.
The Documentation tab
The tab is a file manager over docs/, with folder navigation and a breadcrumb. Markdown opens rendered, with a toggle to the source; other file types open with syntax highlighting.
New projects start with a docs/README.md that explains the suggested structure. Older projects show an empty state with a button to create the folder. On a phone the tab has its own entry in the project menu.
What the agent does with it
The agent is instructed to write documentation only into docs/, to update an existing page rather than create a second one on the same topic, and never to put credentials into a document. The file names in docs/ are part of what it sees at the start of a conversation, so it knows which documents already exist before it writes a new one.
If the agent writes a document during a chat turn, the view updates immediately — the same live refresh the other file browsers use.
What to keep in it
Architecture decisions and the reasoning behind them, the domain language of the product, runbooks for the things that go wrong, and anything a new team member would otherwise have to ask a person for. It is the one place where that knowledge survives both the chat history and the people who wrote it.