layered-recall
Solid4-layer memory recall system. Layer 1 (identity) always loaded, Layer 2 (critical facts) per-project, Layer 3 (room recall) on-demand, Layer 4 (deep search) when needed. Progressive context loading for token efficiency.
Install
Quality Score: 91/100
Skill Content
Details
- Author
- vibeeval
- Repository
- vibeeval/vibecosystem
- Created
- 8 months ago
- Last Updated
- 6 days ago
- Language
- C#
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
memory-architecture
Five-layer memory architecture: where each fact lives, how layers interact, when to promote learnings
memory-recall
Load and summarise the cross-project memory index at the start of a session, or whenever the user asks what Claude remembers about their work. Use this skill when the user says things like "what do you remember", "what's the context", "what's the current state", "show me the memory map", or "what do you know about my projects"; and "where did I/we leave off" or "catch me up" only when no project is named and the current folder has no STATUS.md. To restore one project from its STATUS.md ("catch me up on [project]", "[project] status"), use memory-map. Also trigger proactively at the start of any new conversation if a memory store exists — surface the current state and pending items without being asked, so the user does not have to re-orient Claude. Pairs with memory-map (which writes memory) and memory-prune (which cleans it). Together they form a complete memory loop across Claude sessions.
memory-recall
Retrieve relevant project memory before acting on a task — checking past decisions, related episodes, and semantic facts so work doesn't contradict or duplicate what's already known, following the read-before-reasoning discipline. Use before starting any non-trivial task, before proposing an architectural approach, or when something in the current task sounds like it might have come up before.