learn

Project Learnings

Manage project-specific operational knowledge that persists across Claude Code sessions. Learnings complement the memory system — memory stores cross-project user preferences, learnings store project-specific operational knowledge.

Storage

Learnings live in plain markdown files alongside the project's memory directory:

~/.claude/projects/{project-hash}/learnings/
├── index.md         # Quick-reference summary (briefing for new sessions)
├── patterns.md      # "This codebase does X because Y"
├── pitfalls.md      # "Don't do X, it breaks Y"
├── operational.md   # "Build requires Z, deploy needs W"
└── decisions.md     # "We chose X over Y because Z"

Note: /learn is a skill trigger — not a registered slash command. Invoke it by saying "show learnings", "add a learning", etc. The index is not auto-loaded at session start. To load it automatically, add this line to your project's CLAUDE.md:

@~/.claude/projects/{project-hash}/learnings/index.md

Usage

• show learnings — Show the index (quick reference of all learnings)
• add a learning — Add a new learning interactively
• search learnings <query> — Search all learnings files for a term
• prune learnings — Check for stale entries (referenced files that no longer exist)
• export learnings — Export learnings as a block suitable for CLAUDE.md
• learning stats — Show counts by category (total + per file)

Adding a Learning

When adding a learning (either via /learn add or at end of session), classify it:

pattern — How this codebase does things. Conventions, architecture patterns, integration approaches that aren't obvious from reading the code.

## Build system uses turborepo with custom pipeline
The monorepo runs `turbo build` but the order matters — `packages/db` must build before
`apps/api` because it generates Prisma types. Running `turbo build --filter=apps/api`
alone will fail with missing types.

pitfall — Things that break. Gotchas, footguns, things that look right but aren't.