/session-learning-capture
Capture and document session learnings
$ npx -y skills add qdhenry/Claude-Command-Suite --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/session-learning-capture
Context preview
What this command does when you run it.
Capture and document session learnings
Command definition
session-learning-capture.mdSession Learning Capture
Capture and document session learnings
Instructions
1. **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
2. **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
3. **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
4. **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
Read more
Session Learning Capture
Capture and document session learnings
Instructions
1. **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
2. **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
3. **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
4. **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
A comprehensive development toolkit designed following Anthropic's Claude Code Best Practices for AI-assisted software development.
Repo: qdhenry/Claude-Command-Suite
Other commands on claude-command-suite.
- /boundary-bbcr-fallback
Execute automatic BBCR (Collapse-Rebirth Correction) when knowledge boundaries are exceeded or reasoning fails.
Open command - /boundary-detect
Analyze semantic position relative to knowledge boundaries to prevent hallucination and identify uncertainty zones.
Open command - /boundary-heatmap
Generate a visual heatmap of knowledge boundaries showing safe zones, risk areas, and semantic coverage.
Open command - /boundary-risk-assess
Evaluate the current risk level and provide detailed analysis of potential hallucination or reasoning failure.
Open command - /boundary-safe-bridge
Find and construct semantic bridges to safely navigate from current position to target concept without crossing dangerous boundaries.
Open command - /optimize-prompt
Takes an input prompt and returns ONLY a token-optimized version that preserves meaning while minimizing token count. Based on LLM tokenization principles: common words tokenize more efficiently, unusual words break into more tokens, and conciseness reduces cost.
Open command