By name: recall description: Retrieves cross-session memories about past decisions, lessons, and patterns. Use when user asks about prior work, past decisions, or mentions a feature. Triggers include check memory, what did we decide, how did we solve. context: fork allowed-tools: - Bash
Proactive Usage Guidelines
You should proactively use this skill when:
Session Start: When user mentions a feature/module, search for related memories first
- User says "let's work on authentication" →
"/Users/cyh/Development/Dev/Termdock-issues/.claude/skills/recall-termdock-issues-dc11/recall.sh" authentication - User mentions a specific service → search for prior decisions about it
- User says "let's work on authentication" →
Before Decisions: Before making architectural or technical choices
- About to choose a library → check if there's a prior decision
- Designing a new feature → search for related patterns
After Problem Solving: When you've solved a tricky issue
- Found a non-obvious bug →
"/Users/cyh/Development/Dev/Termdock-issues/.claude/skills/recall-termdock-issues-dc11/remember.sh" lesson "description" - Made an important decision →
"/Users/cyh/Development/Dev/Termdock-issues/.claude/skills/recall-termdock-issues-dc11/remember.sh" architecture "description"
- Found a non-obvious bug →
Encountering Familiar Issues: When something seems like a recurring problem
- Error looks familiar → search lessons learned
Commands
| Action | Command |
|---|---|
| Search memories | "/Users/cyh/Development/Dev/Termdock-issues/.claude/skills/recall-termdock-issues-dc11/recall.sh" <keywords> |
| Save memory | "/Users/cyh/Development/Dev/Termdock-issues/.claude/skills/recall-termdock-issues-dc11/remember.sh" <category> "<content>" |
| Remove outdated | "/Users/cyh/Development/Dev/Termdock-issues/.claude/skills/recall-termdock-issues-dc11/forget.sh" "<keywords>" |
Categories
architecture - Design decisions, technology choices
lesson - Gotchas, debugging discoveries, edge cases
pattern - Reusable solutions, conventions
style - Naming, code organization
preference - Tooling, workflow choices
Examples
"/Users/cyh/Development/Dev/Termdock-issues/.claude/skills/recall-termdock-issues-dc11/recall.sh" terminal session
"/Users/cyh/Development/Dev/Termdock-issues/.claude/skills/recall-termdock-issues-dc11/recall.sh" "error handling"
"/Users/cyh/Development/Dev/Termdock-issues/.claude/skills/recall-termdock-issues-dc11/remember.sh" lesson "node-pty requires explicit shell path on macOS"
"/Users/cyh/Development/Dev/Termdock-issues/.claude/skills/recall-termdock-issues-dc11/remember.sh" architecture "Use EventBus for cross-service communication"