Session learning capture

Oturum öğrenimlerini yakalayın ve belgeleyin

yazan kuscubasiece·8 Eylül 2026

Kaynak: davepoon/claude-code-subagents-collection · MIT

Kurulum

mkdir -p .claude/commands && curl -sL https://www.antrophiclove.com/api/kaynak/session-learning-capture/raw -o .claude/commands/session-learning-capture.md

Hedef dosya: .claude/commands/session-learning-capture.md

Önizleme Ham metin ⑂ Kendi sürümünü oluştur

Session Learning Capture

Capture and document session learnings

Instructions

Identify Session Learnings
- Review if during your session:
  - You learned something new about the project
  - I corrected you on a specific implementation detail
  - I corrected source code you generated
  - You struggled to find specific information and had to infer details about the project
  - You lost track of the project structure and had to look up information in the source code
Determine Appropriate File
- Choose the right file for the information:
  - CLAUDE.md for shared context that should be version controlled
  - CLAUDE.local.md for private notes and developer-specific settings
  - Subdirectory CLAUDE.md for component-specific information
Memory File Types Summary
- Shared Project Memory (CLAUDE.md):
  - Located in the repository root or any working directory
  - Checked into version control for team-wide context sharing
  - Loaded recursively from the current directory up to the root
- Local, Non-Shared Memory (CLAUDE.local.md):
  - Placed alongside or above working files, excluded from version control
  - Stores private, developer-specific notes and settings
  - Loaded recursively like CLAUDE.md
- On-Demand Subdirectory Loading:
  - CLAUDE.md files in child folders are loaded only when editing files in those subfolders
  - Prevents unnecessary context bloat
- Global User Memory (~/.claude/CLAUDE.md):
  - Acts as a personal, cross-project memory
  - Automatically merged into sessions under your home directory
Update Memory Files
- Add relevant, non-obvious information that should be persisted
- Ensure proper placement based on component relevance:
  - UI-specific information → apps/[project]-ui/CLAUDE.md
  - API-specific information → apps/[project]-api/CLAUDE.md
  - Infrastructure information → cdk/CLAUDE.md or infrastructure/CLAUDE.md
- This ensures important knowledge is retained and available in future sessions

Credit

This command is based on the work of Thomas Landgraf: https://thomaslandgraf.substack.com/p/claude-codes-memory-working-with