Docs

Patterns

The moves your team makes on purpose. Named recipes worth reaching for, plus a companion anti-patterns.md file listing the moves you deliberately avoid. Both sides matter. The brain index links both files, so an agent that follows the session-start ritual knows where to find them.

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 “Patterns”.
  • Source: .claude/brain/patterns.md (positive recipes); anti-patterns live in the companion .claude/brain/anti-patterns.md
  • Cross-repo: Playbooks tab shows patterns shared across 2+ tracked repos.

What it does for you

Recipes get reused, not re-invented.Named patterns ("state-doc PR fast-path," "junction node_modules in worktrees") give the team and the AI a shared vocabulary for moves that already work.
Anti-patterns block the wrong moves.Listing what you DON'T do is as important as listing what you do. The AI reads both and steers clear of the foot-guns you've already mapped.
Cross-repo patterns promote to Playbooks.When the same pattern shows up in 2+ repos, the Playbooks tab lists it as an established playbook and offers to open a PR adding it to the tracked repos that lack it. A pattern found in only one repo stays a candidate until a second repo picks it up.

Configure

Nothing - patterns.md is a flat .md. Anti-patterns live in a sibling file, anti-patterns.md.

Use it well

Add a pattern the second time you reach for the same move. The first time is "just doing the work;" the second is a named pattern. Two repos is the threshold: a cross-repo pattern promotes to Playbooks once it shows up in 2+ tracked repos.

Read more

Last updated