Use the EpochDB long-term memory layer to recall facts from past sessions and offload heavy context, minimizing token use during long development loops.
How this skill is triggered — by the user, by Claude, or both
Slash command
/epochdb-memory:epoch-memory [recall|save|search][recall|save|search]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
This plugin gives Claude Code an automatic, local long-term memory backed by
This plugin gives Claude Code an automatic, local long-term memory backed by EpochDB. It runs through hooks (no MCP server required):
<long_term_memory> tags.~/.epochdb (override with EPOCHDB_STORAGE_DIR).<long_term_memory> context appears, treat it as
background from earlier sessions. Prefer it over asking the user to re-paste
configs, decisions, or history — but verify file/flag names still exist
before acting on them./memory-stats — show counts, storage path, and retrieval mode./memory-search <query> — semantically search stored memories.sentence-transformers is installed (default),
and falls back to entity/keyword matching otherwise — memory still works.npx claudepluginhub jersobh/epochdb-memory-plugin --plugin epochdb-memorySearches MemPalace before answering questions about past work, people, projects, or prior decisions. Returns verbatim stored content instead of guessing from model memory.
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Implements vector databases with Pinecone, Weaviate, Qdrant, Milvus, pgvector for semantic search, RAG, recommendations, and similarity systems. Optimizes embeddings, indexing, and hybrid search.