/memory-bank
Update the project's CLAUDE.md memory bank with current session learnings.
$ npx -y skills add rohitg00/awesome-claude-code-toolkit --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
/memory-bank
Context preview
What this command does when you run it.
Update the project's CLAUDE.md memory bank with current session learnings.
Command definition
memory-bank.mdUpdate the project's CLAUDE.md memory bank with current session learnings.
Steps
1. Read the existing `CLAUDE.md` (project root) or create one if it does not exist. 2. Analyze the current session to extract:
- **Decisions made**: Architecture choices, library selections, pattern adoptions.
- **Problems solved**: Bugs fixed, workarounds discovered, gotchas identified.
- **Patterns established**: Naming conventions, file organization, coding standards.
- **Commands discovered**: Useful CLI commands, build steps, debug techniques.
- **Dependencies**: New packages added and why, version constraints.
3. Categorize learnings into the appropriate CLAUDE.md sections:
- Project overview and key paths.
- Build and test commands.
- Architecture notes.
- Known issues and workarounds.
- Session-specific notes.
4. Merge new information without duplicating existing entries. 5. Update the "Last updated" timestamp. 6. Keep the file concise: each entry should be one to two lines.
Format
# Project Memory
## Overview
- Description, key paths, tech stack
## Commands
- `<command>` - what it does
## Architecture
- Key design decisions and patterns
## Known Issues
- Issue description and workaround
## Session Notes
- Last updated: YYYY-MM-DD
- <new learnings from this session>
Rules
- Never remove existing entries unless they are explicitly outdated.
- Keep each entry factual and actionable, not narrative.
- Limit the file to 200 lines; archive old session notes if it grows beyond that.
- Use bullet points for scanability, not paragraphs.
- Store project-specific memory in project root, personal memory in `~/.claude/CLAUDE.md`.
Read more
Update the project's CLAUDE.md memory bank with current session learnings.
Steps
1. Read the existing `CLAUDE.md` (project root) or create one if it does not exist. 2. Analyze the current session to extract:
- **Decisions made**: Architecture choices, library selections, pattern adoptions.
- **Problems solved**: Bugs fixed, workarounds discovered, gotchas identified.
- **Patterns established**: Naming conventions, file organization, coding standards.
- **Commands discovered**: Useful CLI commands, build steps, debug techniques.
- **Dependencies**: New packages added and why, version constraints.
3. Categorize learnings into the appropriate CLAUDE.md sections:
- Project overview and key paths.
- Build and test commands.
- Architecture notes.
- Known issues and workarounds.
- Session-specific notes.
4. Merge new information without duplicating existing entries. 5. Update the "Last updated" timestamp. 6. Keep the file concise: each entry should be one to two lines.
Format
# Project Memory ## Overview - Description, key paths, tech stack ## Commands - `<command>` - what it does ## Architecture - Key design decisions and patterns ## Known Issues - Issue description and workaround ## Session Notes - Last updated: YYYY-MM-DD - <new learnings from this session>
Rules
- Never remove existing entries unless they are explicitly outdated.
- Keep each entry factual and actionable, not narrative.
- Limit the file to 200 lines; archive old session notes if it grows beyond that.
- Use bullet points for scanability, not paragraphs.
- Store project-specific memory in project root, personal memory in `~/.claude/CLAUDE.md`.
The most comprehensive toolkit for Claude Code -- 135 agents, 35 curated skills (+400,000 via SkillKit), 42 commands, 176+ plugins, 20 hooks, 15 rules, 7 templates, 15 MCP configs, 26 companion apps, 53 ecosystem entries, and more.
Repo: rohitg00/awesome-claude-code-toolkit
Other commands on rohitg00-claude-code-toolkit.
- /adr
Write an Architecture Decision Record documenting a significant technical decision.
Open command - /design-review
Conduct a structured design review of a module, feature, or system component.
Open command - /diagram
Generate Mermaid diagrams from codebase analysis or description.
Open command - /migrate
Plan and execute a framework or library migration incrementally.
Open command - /plan
Create a structured implementation plan for the requested feature or change.
Open command - /refactor
Perform a systematic refactoring of the specified code area.
Open command

