From brainlayer
Guides deliberate BrainLayer memory use: search before assumptions with brain_search, store decisions with brain_store, recall context with brain_recall when resuming sessions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/brainlayer:memoryThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use BrainLayer when session context is incomplete or when the task depends on prior decisions.
Use BrainLayer when session context is incomplete or when the task depends on prior decisions.
brain_search before answering architecture, project-history, preference, or "what did we decide" questions.brain_recall when you need the current working context, recent session state, or session-linked summaries.brain_store after decisions, corrections, failures, or milestones so the next Claude session can recover the why, not just the code diff.Before answering from memory, verify with brain_search instead of assuming.
npx claudepluginhub etanhey/brainlayer --plugin brainlayerProactively saves decisions, conventions, bugs, discoveries, and preferences to persistent Engram memory across sessions using mem_save and related tools.
Captures cross-project learnable patterns (decisions, errors, insights) into a persistent semantic graph via Neural Memory MCP. Auto-recalls context at session start and captures learnings after feature work, debugging, or code review.
Persists learnings into a 5-layer memory hierarchy (CLAUDE.md files, memory/MEMORY.md) and consolidates by pruning outdated entries and promoting recurring patterns. Triggers on 'extract learnings', 'remember', 'dream'.