Project Memory Recall FAQs

Question 1

Does this skill integrate with vector search?

Accepted Answer

Yes. If a Qdrant MCP server is available, the skill uses vector search to find semantic keyword matches and file-path hints. This provides a powerful starting point for the skill's primary tree-based navigation and progressive disclosure strategy.

Question 2

What does the Project Memory Recall skill do?

Accepted Answer

This skill enables Claude to access a structured, file-based memory store specific to your project. It retrieves architectural decisions, historical context, and domain-specific patterns categorized into episodic, procedural, and semantic modules to inform development tasks.

Question 3

How does the tri-modular memory structure improve search?

Accepted Answer

By categorizing data into Episodic (concrete project events), Procedural (workflow-specific steps), and Semantic (high-level architecture and domain logic), the skill allows Claude to target the exact type of information needed, reducing noise and improving accuracy.

Question 4

Will using this skill clutter my main conversation context?

Accepted Answer

No. The Project Memory Recall skill is designed to run in a separate context using the Task tool with a general-purpose subagent. This keeps the information gathering process isolated, preventing your main conversation from becoming overwhelmed with search data.

Question 5

When should I use this skill instead of universal tools?

Accepted Answer

Use Project Memory Recall when you need insights unique to your specific codebase, such as why a certain library was chosen or how a custom module works. For general coding patterns or language-wide best practices, use 'coder-memory-recall' instead.

Project Memory Recall

Project Memory Recall

Key Features

Use Cases

Key Features

Use Cases