Reference · Files

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: http://localhost:4000/, then Reference (drawer) → Files in the sidebar.
  • Hosted: repoops.ai/team/reference (browse it from the Reference drawer)
  • Keyboard: ⌘ K, then type “Files”.
  • On disk: .claude/brain/files.md

What it does for you

Find the right directory in one read.Hand-curated, flat, ranked top-down by importance. Beats tree output and outlives it (this file moves when intent moves; tree just describes disk).
New directories show up here in the same PR that creates them.CLAUDE.md hard rule: don't create a new top-level directory without updating files.md in the same PR. The map never drifts.
The first file a fresh agent should read after INDEX.Two-minute onboard: INDEX tells you what just shipped; Files tells you where to look. Together, you can change any part of the repo confidently.

Configure

Nothing - it's a hand-curated markdown file. Keep entries one line each; keep the order semantic (top = most-touched, bottom = rarely touched).

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. The brain-drift CI job will catch you if you don't.

Read more