Docs
Files
Know what every directory is for before you change anything. A flat, hand-curated map of every folder and key file - one line of purpose each. The first thing to read when a fresh agent (or a fresh you) needs to find anything.
See it in motion
Where to find it
- Desktop:
localhost:4000, then Memory in the sidebar, then Reference index under All tools, in the Lessons, wiki and patterns group, which lists it. - Hosted:
repoops.ai/team/reference, from Memory in the sidebar, then Reference index under All tools, in the Lessons, wiki and patterns group, which lists it. - Keyboard: ⌘ K, then type “Files”.
- On disk:
.claude/brain/files.md
What it does for you
tree output and outlives it (this file moves when intent moves; tree just describes disk)..claude/brain/files.d/ fragment plus npm run sync-files, never a hand-edit of files.md. Nothing compares the map to the tree, so a missed row is a convention agents keep rather than a check that fails. The fold itself is gated: brain-drift fails the PR when the managed block is behind its fragments, or when a path the map names no longer resolves.Configure
Nothing to set up. Keep each row one line, and keep the order semantic (top = most-touched, bottom = rarely touched). The rows above the managed block are hand-curated. Where a repo folds fragments, as RepoOps itself does, a new row goes in .claude/brain/files.d/<slug>.md and npm run sync-files folds it into the block, so two PRs never collide on one table.
Use it well
Before changing the layout of the repo, read Files. Match the existing structure unless you have a real reason not to. After your PR adds a directory, document it here - one line is enough. It's a CLAUDE.md hard rule: no new top-level directory without a files.md row in the same PR.
Read more
Last updated