Recall

Proactive Usage Guidelines

You should proactively use this skill when:

1. Session Start: When user mentions a feature/module, search for related memories first

   • User says "let's work on authentication" → ./recall.sh authentication
   • User mentions a specific service → search for prior decisions about it

2. 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

3. After Problem Solving: When you've solved a tricky issue

   • Found a non-obvious bug → ./remember.sh lesson "description"
   • Made an important decision → ./remember.sh architecture "description"

4. Encountering Familiar Issues: When something seems like a recurring problem

   • Error looks familiar → search lessons learned

Commands

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

./recall.sh terminal session
./recall.sh "error handling"
./remember.sh lesson "node-pty requires explicit shell path on macOS"
./remember.sh architecture "Use EventBus for cross-service communication"