9fc6ad20d2
Three internal documentation references pointed at non-existent targets: - docs/api.md: MessageItem.content linked to #addmessage, which has no heading or anchor; corrected to #messageitem (the slug used by every other MessageItem cross-reference and matching the ### MessageItem heading). - docs/cascade_runbook.md: the FD-exhaustion cross-ref used a single hyphen where the GitHub slug of "FD exhaustion (`os error 24` / EMFILE)" has a double hyphen (from the ` / ` separator); corrected to #fd-exhaustion-os-error-24--emfile. - use-cases/claude-code-plugin/skills/memory-tools.md: the always-injected skill named two tools (search_memories, get_memory) that the MCP server never exposes; replaced with the real evermem_search tool and its params (query required, limit default 10 / max 20). Markdown-only; no runtime behavior change.
36 lines
1.6 KiB
Markdown
36 lines
1.6 KiB
Markdown
---
|
|
description: Guidance for using EverMem memory tools to recall past session context
|
|
alwaysInclude: true
|
|
---
|
|
|
|
# EverMem Memory Tools
|
|
|
|
You have access to memory tools that can recall context from the user's past coding sessions. Use these tools proactively when they would help provide better assistance.
|
|
|
|
## Available Tools
|
|
|
|
- **evermem_search**: Search past conversations using semantic + keyword matching. Params: `query` (required), `limit` (default 10, max 20)
|
|
|
|
## When to Use Memory Search
|
|
|
|
**DO search memories when:**
|
|
- User asks about past work, decisions, or implementations ("how did we handle X?")
|
|
- User references previous sessions ("remember when", "last time", "we discussed")
|
|
- User is debugging something that may have been solved before
|
|
- User asks about project patterns, conventions, or architecture decisions
|
|
- Context from previous sessions would improve your response
|
|
- User seems to expect you to know something from before
|
|
|
|
**DON'T search memories when:**
|
|
- The question is self-contained and doesn't need historical context
|
|
- User explicitly provides all needed context in their message
|
|
- It's a general knowledge question unrelated to their project history
|
|
- You've already searched for this topic in the current session
|
|
|
|
## Best Practices
|
|
|
|
1. **Be selective**: Don't search for every query - only when past context adds value
|
|
2. **Use specific queries**: Search for relevant terms, not the entire user message
|
|
3. **Synthesize results**: When you find relevant memories, integrate them naturally into your response
|
|
4. **Be transparent**: Mention when your response is informed by past session context
|