Retrieve development context and patterns from memory. Use when user asks "how did we build", "what's the pattern for", "who worked on", "show me previous", or when implementing similar features.
Automatically retrieves relevant development context, patterns, and team knowledge from memory when implementing features, debugging code, or making architectural decisions. Activates when you ask about past work, propose technical approaches, or start similar tasks to surface historical decisions and established conventions.
/plugin marketplace add julep-ai/memory-store-plugin/plugin install memory-store@claude-pluginThis skill inherits all available tools. When active, it can use any tool Claude has access to.
This skill enables Claude to automatically retrieve relevant development context, patterns, and team knowledge from the memory store without explicit user requests.
Claude should invoke this skill automatically when:
Starting new implementations
Making architectural decisions
Debugging or investigating code
Refactoring or modifying code
Answering "why" questions
When Claude detects a task that might benefit from historical context:
1. Identify key concepts from user's request
2. Use memory_recall to search for relevant memories
3. Present relevant context to inform the response
4. Suggest patterns or warn about deviations
Scenario 1: New Feature Implementation
User: "I need to add a new API endpoint for user preferences"
Claude (internally):
- Detects: New API endpoint needed
- Recalls: API endpoint patterns, authentication requirements
- Retrieves: Similar endpoint implementations, team conventions
- Applies: Suggests following established patterns
Claude: "I'll help you create the user preferences endpoint. Based on our established
patterns (see src/api/auth.ts:45), I'll follow the same authentication and error
handling conventions we've used for other endpoints..."
Scenario 2: Architectural Decision
User: "Should we use MongoDB or PostgreSQL for this new feature?"
Claude (internally):
- Detects: Database choice decision
- Recalls: Previous database decisions
- Retrieves: Reasoning from 3 months ago
- Applies: Provides historical context
Claude: "Looking at our memory store, the team decided to use PostgreSQL 3 months ago
(session mem-2024-10-15-xyz) for ACID compliance and complex relationships. Unless this
feature has significantly different requirements, I'd recommend staying consistent..."
Scenario 3: Code Investigation
User: "Why is this authentication code structured this way?"
Claude (internally):
- Detects: Question about existing code
- Recalls: Authentication implementation decisions
- Retrieves: Context from when code was written
- Applies: Explains reasoning
Claude: "This authentication structure was implemented 2 weeks ago following the OAuth2
pattern. The team chose this approach for better security and SSO support (documented
in CLAUDE.md anchor <!-- AUTH-FLOW -->). The specific structure handles edge cases
like token refresh and concurrent requests..."
This skill primarily uses these memory MCP tools:
memory_recall - Retrieve relevant memories
memory_recall({
cues: ["authentication", "api endpoint", "pattern"],
background: "User is implementing new API endpoint for user preferences",
k: 5
})
memory_overview - Get project-wide context
memory_overview({
mode: "standard"
})
The skill retrieves context from these categories:
The skill should balance consistency with flexibility. Historical context informs but doesn't dictate. When user has good reasons to deviate, support the new approach while documenting it for future reference.
User starts task → Skill activates → Retrieve context → Apply to response
↓
Store new patterns → Update memory → Enable future retrieval
/memory-context command - Manual context retrievalThis skill is successful when:
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.