layered-recall

Solid

4-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.

AI & Automation 552 stars 45 forks Updated 6 days ago MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%
91
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Layered Recall 4-layer progressive memory system. Each layer adds more context only when needed, saving tokens while ensuring nothing important is missed. ## The 4 Layers ``` Layer 1: Identity (always loaded, ~200 tokens) Who is the user? What are their preferences? Layer 2: Critical Facts (per-project, ~500 tokens) Hard constraints, active decisions, blockers Layer 3: Room Recall (on-demand, ~1-2K tokens) Relevant memories for current task domain Layer 4: Deep Search (when needed, ~2-5K tokens) Full semantic search across all memories ``` ## Layer Details ### Layer 1: Identity (~200 tokens, ALWAYS loaded) Loaded at every session start. Contains: - User preferences (language, style, autonomy level) - Global constraints (no emojis, Turkish responses, etc.) - Tool preferences (which editors, which terminal) **Source:** `~/.claude/projects/*/memory/user_*.md` ### Layer 2: Critical Facts (~500 tokens, per-project) Loaded when entering a project directory. Contains: - Active architectural decisions - Known blockers and constraints - Current sprint/milestone goals - Tech stack and versions **Source:** `~/.claude/projects/*/memory/project_*.md` + `thoughts/CONTEXT.md` ### Layer 3: Room Recall (~1-2K tokens, on-demand) Loaded when task domain is detected (auth, database, deploy, etc.). Contains: - Previous decisions in this domain - Past errors and fixes - Patterns that worked - Patterns that failed **Source:** Memory palace rooms + `mature-instincts.jso...

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

AI & Automation Listed

memory-architecture

Five-layer memory architecture: where each fact lives, how layers interact, when to promote learnings

1 Updated today
sefaertunc
AI & Automation Listed

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.

2 Updated 4 days ago
shandar
AI & Automation Listed

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.

1 Updated 3 months ago
NITISH-R-G