Claude memory kit
The starter kit for Claude Code — your agent remembers across sessions: date-tagged memory under three hook-enforced caps, per-session handoffs, stale-refs detection, multi-project isolation, audit-driven promotion via /close-session, plus an opt-in multi-agent orchestration layer. Zero deps.
npx -y skills add awrshift/claude-memory-kitAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Persistent memory for Claude Code agents with an agent-audit-ritual architecture. User only talks; the agent captures, audits, proposes promotions, and writes. Memory lives in layers — a hot cache (MEMORY.md) held under three size caps, per-session handoffs (context/handoffs/), topical knowledge articles (knowledge/concepts/), and canonical rules (.claude/rules/) — plus multi-project isolation via projects/<name>/ and an experiments/ sandbox. /close-session runs the end-of-session audit ritual. Zero external dependencies.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
5.7 KB, as published. Nobody here has run it
Claude Memory Kit v5
Persistent memory for Claude Code agents. Layered memory, agent-driven promotion, zero manual file editing. The v5 lean core: two operators, per-session handoffs, memory that fails loudly instead of rotting quietly.
Two core invariants
- User only talks. Agent captures, proposes, writes. Every architectural decision passes this test.
- Every memory entry carries a
[YYYY-MM-DD]date tag. This is what lets/close-sessiondetect cross-session repetition and propose promotions.
What's new in v5
- Session close is
/close-session, not/close-day. The ritual: capture dated patterns → audit for 3+-date repetition → promote on your "yes" → replace the MEMORY.md header (current state, never a chronicle) → write a per-session handoff. - Per-session handoffs replace the rolling next-session-prompt. One immutable note per closed session in
context/handoffs/<topic>-YYYY-MM-DD.md; the SessionStart hook injects the newest one. No rolling file to freeze while looking authoritative. - Three independent MEMORY.md caps, hook-enforced: 180 lines / 32 KB / 3000 chars per line. Line count alone lies — content densifies into ever-longer lines while
wc -lstays flat. Any tripped cap opens the next session with an audit prompt. - Stale-reference detector. Every session start, file paths mentioned in memory are checked against disk; anything moved or missing is flagged.
- The daily journal (
daily/+/close-day) moved to opt-in.kit/advanced/close-day-layer/— it was the layer that silently rotted in long-running use. Onecpre-enables it.
See .kit/CHANGELOG.md for full migration notes.
Quick start
git clone --depth 1 https://github.com/awrshift/claude-memory-kit.git my-project
cd my-project
claude
First session: agent greets you, asks 2-3 setup questions, loads you in. Type /tour for a guided walkthrough.
Daily workflow
- Open a session — the hook auto-loads the newest handoff + MEMORY health stats + knowledge index
- Work normally — agent captures patterns in MEMORY.md as you speak
/close-sessionwhen done — agent audits for promotions, proposes verbally, writes on your verbal "yes", and leaves the handoff note for next time
Tomorrow starts where today left off — from that handoff.
Included skills
Default — the whole loop:
| Skill | Description |
|---|---|
/close-session | End-of-session audit ritual: capture + promotion proposals + MEMORY header refresh + handoff |
/tour | Interactive guided walkthrough on your own files |
Opt-in (.kit/advanced/, copy into .claude/ to enable):
| Skill | Description |
|---|---|
/close-day | Day-by-day journal layer (close-day-layer/) — synthesizes a daily log, backfills missed days from git history |
/memory-usage | Read-only telemetry: hot files vs cold archival candidates |
/memory-lint | Structural hygiene (broken links, sparse articles, orphans) |
/session-review | Orchestration layer — end-of-session adversarial review with independent reviewers |
/second-opinion | Orchestration layer — cross-check a high-stakes answer (Devil's Advocate · Boardroom · Round-Table) |
The orchestration layer (.kit/advanced/orchestration-layer/) also ships three agents —
executor (builds to a decided spec in a worktree), recon (read-only fact-gatherer),
idea-validator (isolated adversarial critic) — and four rules (orchestrator fact-check ·
parallel development · doc governance · decisions log) for multi-agent development.
Architecture
Memory lives in layers, each answering a different question:
| Layer | Answers | Written by |
|---|---|---|
.claude/memory/MEMORY.md | «what patterns repeat» + «where things stand» | agent as you speak |
context/handoffs/*.md | «what happened, session by session» | agent via /close-session |
knowledge/concepts/*.md | «facts and rationale by topic» | agent after your "yes" on /close-session |
.claude/rules/*.md | «what must always / never happen» | agent after a long-stable pattern |
Promotion runs observation → candidate → law: a dated pattern in MEMORY.md that repeats on 3+ distinct dates becomes a knowledge/concepts/ article or a .claude/rules/ constraint on /close-session — always agent-written, always on your verbal confirmation.
See .kit/ARCHITECTURE.md for full details and CLAUDE.md for the agent's session workflow.
Built from production use
Distilled from 1000+ real sessions over 12 months of continuous daily Claude Code work by one operator across many verticals (marketing, sales, lead generation, business analysis, R&D, production code with backend/frontend engineers) — the same agent architecture cloned per vertical. Every component earns its place; experiences/, background-detection scripts, generic role-guidance seeds — and, in v5, the daily-chronicle default — didn't survive review.