Setup Memory Skill
Jorgecrm/setup-memory-skill
Memória persistente automática entre sessões do Claude Code
Ver no GitHubUma skill para Claude Code que implementa memória persistente entre sessões. Automaticamente carrega contexto do projeto no início de cada sessão e o salva ao final, mantendo um arquivo único e sempre atualizado que elimina a necessidade de re-explicar decisões e progresso.
Instalação
npx convez-ai Jorgecrm/setup-memory-skill1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Manter contexto de projetos longos sem perder histórico
- Evitar re-explicar decisões técnicas e status do projeto
- Acelerar início de novas sessões com snapshot automático
- Gerenciar preferências e configurações por projeto
Veredito

Skill bem estruturada que resolve um problema real: perda de contexto entre sessões. Implementação com hooks automáticos é sólida, embora dependa de 3 skills relacionadas funcionarem em conjunto. Ideal para fluxos de trabalho de longo prazo.
README
A tradução para o português deste README ainda está na fila.
setup-memory — Claude Code Skill
A skill that gives Claude persistent memory across sessions. Once installed, Claude automatically loads project context at the start of every session and saves it at the end — without you having to ask.
The Problem It Solves
Every time you start a new Claude Code session, Claude has no idea what you were working on. You have to re-explain the project, re-explain decisions, and re-explain context. It wastes time and breaks your flow.
setup-memory fixes this. It creates a Memory/ folder in your project that Claude reads at the start of every session and updates at the end.
How It Works
- Session start: A hook runs automatically and injects the contents of
Memory/current-state.mddirectly into Claude's context — no file read required, guaranteed to load. - Session end: When you say "done", Claude runs the end-session skill → session-handoff → memory-keeper rewrites
current-state.mdwith a fresh snapshot. - If you close without saying done: A
SessionEndhook writes a marker file. Next session, Claude is warned that the previous session wasn't saved.
One file, always fresh, never grows.
What Gets Created (One-Time Setup)
| Item | What it does |
|---|---|
Memory/README.md | Explains the memory system |
Memory/current-state.md | Single snapshot — status, decisions, preferences, next step. Overwritten each session. |
.claude/agents/memory-keeper.md | Sub-agent that rewrites current-state.md at session end |
.claude/settings.json hooks | SessionStart: injects memory into context. SessionEnd: writes crash-guard marker. |
How to Set It Up
Step 1 — Copy all three skills into your Claude Code skills folder
This skill has two dependencies that handle saving memory at session end. All three need to be installed.
setup-memory (this skill — the main one):
~/.claude/skills/setup-memory/
SKILL.md ← SKILL.md from the root of this repo
templates/
current-state.md
memory-keeper-agent.md
memory-readme.md
session-handoff (writes the end-of-session summary):
~/.claude/skills/session-handoff/
SKILL.md ← session-handoff/SKILL.md from this repo
end-session (triggers the save workflow when you say "done"):
~/.claude/skills/end-session/
SKILL.md ← end-session/SKILL.md from this repo
Step 2 — Open Claude Code in your project and say:
set up memoryadd memory to this projectI want Claude to remember things across sessions
Claude asks two questions: what the project is, and what you want to build first. Then sets everything up.
Step 3 — Start a new session
From that point on, memory is active automatically.
How Memory Gets Saved
Say any of these when you're done:
done for todaysee you tomorrowupdate memorywrap up
Claude saves the session automatically. If you close without saying done, the next session will warn you that memory from the previous session may be missing.
What current-state.md Looks Like
# Current State
**Project:** My Forex trading journal SaaS
**Status:** Login page built, now building the dashboard
**Last session:** June 15, 2026
**What we did:**
- Built login page with Supabase auth
- Connected frontend to Supabase
- Fixed redirect bug after login
**Key decisions:**
- Using Supabase for auth (not Firebase)
- Next.js for the frontend
**About me:**
- Explain things in plain language, no jargon
- Always tell me what to do next
**Next step:** Build the dashboard main view
Requirements
- Claude Code
- A project folder
- All three skills installed (setup-memory, session-handoff, end-session)
Created by
Jorge — built with Claude Code.