memories — team brain + design canon for Claude Code

Compounds

day 1empty
week 1first 20 memories captured
month 1decisions live in memory, not heads
month 6onboard via /recall
year 1+git tells what · memories tell why

Setup

Install Claude Code ·requires Homebrew
```
brew install --cask claude-code
```

Run the installer ·two lines

curl -fsSL https://137-memories.fly.dev/install.sh -o /tmp/install.sh
bash /tmp/install.sh

Paste the token ·1Password → OpenViking root key (input is hidden)
Restart Claude Code ·⌘+Q, reopen
Try
```
/recall how do memories work
```

What gets wired

User-scope, no per-project setup. One install touches your ~/.claude/ only.

mcp
openviking server Native MCP via streamable HTTP — search, read, store, forget. claude mcp list to verify.
commands
/remember · /recall · /forget Slash commands at ~/.claude/commands/. Use sparingly — saves are mostly automatic.
skill
137-design At ~/.claude/skills/137-design/. Critical rules inline; full canon fetched on demand from viking://user/default/memories/137_design/.
hook
SessionStart When cwd is a 137 repo, attaches one short reminder so the skill + memory backend are visible without you asking.
routing
auto-memory → team backend Block in ~/.claude/CLAUDE.md redirects auto-saves from local files to OpenViking. Saves get team-shared without you typing /remember.
bearer
~/.137-memories/bearer chmod 600. For non-MCP tools and future Cursor/Codex setups. Same trust level as ~/.claude.json.

In a 137 repo

Detected via git remote -v on 137-xyz/*. The skill activates passively — you don't load it, you don't decide when.

session openspassive

Hook fires. Skill + memory backend attached. Critical design rules in context. ~50 token cost.

you ask for UIautomatic

Claude uses tokens, sentence case, no exclamation points, the right company accent — without being told.

you decide somethingautomatic

Save lands in OpenViking under memories/auto/. Next teammate's session sees it. No /remember needed.

you reference past workautomatic

Claude pulls from team memory when a question mentions a prior decision or system. Cross-session continuity.

Commands

Most saves are now automatic. Use these for explicit cases, ambiguity, or recall.

/remember after a non-obvious decision or gotcha write

/recall anything you'd ask in Slack read

/forget stale or wrong · always confirms delete

Project tagging

Auto-detected from your current directory. /recall stays in your project by default — append all to broaden. Override with /remember [project] … from anywhere.

[137-os] [memories] [izza-os] [izza-welcome] [jung137] [fellowship-ops] [general]

Daily habits

starting a task
/recall <area you're touching> 2 minutes — surfaces what the team already knows. Saves you from re-discovering known gotchas.
stuck >15 min
/remember what was wrong + what fixed it Capture immediately, not at end of day. The detail you'd lose by tomorrow is exactly what your future self needs.
after a decision
/remember we chose X over Y because… The "why" is what's hard to recover later. Code shows what; memories show why.
before slack-asking
/recall your question Faster than waiting for a reply. If memory misses, then ask — and remember to capture the answer once you get it.

Scenarios

capture a gotcha[137-os]

/remember RLS policies on company-scoped tables use the user_companies join pattern — auth.uid() goes through that, never pass user_id from client

vendor quirk[izza-os]

/remember Booking Factory property ID for IZZA Marrakech is 7151 — hardcoded in property config, not a runtime lookup. Don't try to fetch it from /properties.

onboard to an area[izza-os]

/recall ARI vs Open API — when do we use which, what are the quirks

capture a decision[137-os]

/remember cycles are global across all 4 companies, not per-company — one unified cadence (architecture decision, not a feature flag)

plain English[izza-welcome]

save this as a team memory: welcome flow uses single-input forms only — multi-field caused 30% drop-off in pilot

ingest a document[memories]

add this URL to memories as a resource: https://docs.bookingfactory.com/api/rate-sync

cross-project lookupall

/recall how do we handle Stripe webhooks all

What goes in

capture

why a decision was made
gotchas (>15 min to figure out)
trade-offs you might revisit
vendor quirks & undoc'd limits

skip

what the code does
conventions / patterns
in-flight, ephemeral state
secrets — keys, tokens, PII

If something breaks

commands missing

restart Claude Code

mcp list shows ✗

check /health · re-run install if 200

auth fails

key rotated · pull fresh from 1Password

design rules ignored

ls ~/.claude/skills/137-design/SKILL.md · re-install if missing

auto-saves not happening

confirm ~/.137-memories/bearer exists · check ~/.claude/CLAUDE.md has the routing block

recall returns nothing

corpus is small at first · keep using /remember