semantic-memory-mcplisted

# Semantic Memory MCP Usage You have access to three MCP tools for semantic memory. Use them PROACTIVELY -- do not wait to be asked. ## Tools Available | Tool | Purpose | All agents | Write agents only | |------|---------|------------|-------------------| | `semantic_search` | Find memories by similarity query | Yes | -- | | `semantic_recall` | Get formatted memories for current context | Yes | -- | | `semantic_store` | Store a new memory with embedding | -- | Yes | Write agents: developer, architect, debugger, analyst, researcher, reviewer, optimizer. Read-only agents: tech-writer, devops, gitops. > **Uwaga**: Jesli ten skill jest aktywny w repozytorium bez MCP server `semantic-memory`, pomin te instrukcje. Agent bez dostepu do `mcp__semantic-memory__*` toolow powinien po prostu pracowac bez pamieci semantycznej -- file-based fallback w `.scaffolding/agent-memory/` wciaz dziala. ## WHEN to Search Memory ### At task start (MANDATORY for these scenarios): - You encounter an **unfamiliar pattern** or module you haven't worked with before - The task involves a **subsystem with known quirks** (deployment, async, database) - You are **debugging** and the error message or stack trace is unclear - You are making an **architecture or design decision** ### Mid-task (RECOMMENDED): - You hit an **unexpected error** -- search for the error message or pattern - You are about to **implement a workaround** -- check if someone already solved it - You need to understand **why a decisi