Claude Code Memory Kit gives Claude a permanent memory for your project. Functions, decisions, bugs, and context — loaded automatically every session. Never lost to a crash, a context limit, or a new machine.
88 sessions. Legacy Java backend. Multiple crashes. This is what actually happened.
Start Session, and Claude picks up exactly where it left off. Lessons loaded. Known bugs loaded. No re-explanation. This was tested repeatedly and held up every time.$1.class for anonymous generic inner classes — was discovered the hard way. Logged to errors.md and lessons.md. Now it loads every session. Same with a SQL apostrophe injection bug in email subjects. Neither will ever cost a debugging session again."Without this kit, day 3 would have started re-explaining the Java patterns to Claude. By day 6 the context would have been too bloated to continue cleanly."
— from an actual session recap, day 6 of 7 building the platform
Run this in your project root. It downloads setup.py and runs it. Claude handles the rest from inside the chat.
The drift checker runs silently after every file edit. Memory updates after every code change. You don't manage any of it — you just work.
Nothing here is decoration. If it's in the kit, it's because a session went wrong without it.
.claude/memory/. Claude reads compact summaries instead of re-scanning your entire codebase every session. On a 100+ function project, this is the difference between a 10-second startup and a 10-minute one.check_memory.py runs silently after every file edit via a PostToolUse hook. Add a function, rename a CSS class, delete an endpoint — Claude's memory updates within seconds, not next session. On the test codebase, it caught 21 undocumented functions on first run and ~50 more when a new feature was added across sessions. Without it, that logic would have been invisible to Claude indefinitely.todo.md for plans, lessons.md so mistakes don't repeat, decisions.md so architecture doesn't get re-debated, errors.md so you never debug the same bug twice.Generate Skills builds a starter set of 7 skills tailored to your stack: code-review, security-check, fix-bug, new-feature, environment-check, run-verification, and refactor. Each skill includes supporting reference docs (like ANTI-PATTERNS.md, ENVIRONMENT-MATRIX.md) that Claude reads when it runs. Add custom skills with a single chat message.claude --headless "your task" and Claude works fully in the background. You return to finished code. Best for well-defined jobs where you don't need to watch every step.Update Kit. The updater shows you exactly what will change and asks before touching anything. Your memory files, task files, and everything below the kit block in CLAUDE.md — never touched.Handoff generates a snapshot for whoever picks up the project next — no Slack thread required.Type any of these in Claude Code chat. Skills fire automatically — no commands needed.
No framework. No cloud. Just markdown files and a Python script.
js_functions.md, backend_reference.md, html_css_reference.md, project_status.md, user_preferences.md. Claude reads these instead of re-scanning your whole codebase every session.todo.md is Claude's plan. lessons.md is its mistake log. decisions.md is its architecture record. errors.md is its bug history. All four are read at the start of every session. All four commit to your repo.settings.json.check_memory.py --silent after every Edit or Write tool call. You never trigger it manually. It just runs in the background and alerts you if drift appears.SKILL.md (trigger + instructions) and optional supporting docs Claude reads when it runs — like ANTI-PATTERNS.md for the refactor skill, or ENVIRONMENT-MATRIX.md for the environment-check skill. Generate Skills creates 7 skills tuned to your stack. You can add custom ones with a single chat message: "Create a skill called [name] that [does X]."## Session Commands or older heading variants). Replaces only that block. Everything else — your project config, memory files, task files — is untouched. Shows a diff before applying.Everything commits to your repo. Pull on a new machine, type Install Memory, and you're back.
This started as a CLAUDE.md I copy-pasted between projects. After session 20 I got annoyed and built the drift detector. Skills were added after noticing the same prompts typed every single day. The updater came after manually patching CLAUDE.md across three separate repos. The tasks/ files came after debugging a bug that had already been fixed two weeks earlier. Everything here has a story.
"By session 10 Claude knew the codebase better than I did — because it had been reading the same lessons.md, errors.md, and decisions.md at the start of every single session."
— from an actual session recap, session 42
One line installs it. Claude handles the rest. You'll be running Start Session in under 2 minutes.