Every Claude session starts from zero. slimecontext is a Claude Code plugin
(slime) that fixes that: it maintains dry, condensed, hierarchical project
context notes as you build, so every new session picks up exactly where the
last one left off — decisions, direction, and next steps — without dragging a
bloated history along.
notes root (your choice — ideally a Drive-synced folder)
├── .slimecontext ← metadata: projects, recent sessions, tag index
└── <project>/context.md ← top-level living note: all relevant context
└── <feature>/context.md ← a big part of the project
└── <sub-feature>/context.md ← the details you're working on right now
Every note is a living document (Now / Decisions / Direction / Log) with a detail curve: the last session stays detailed, older content gets progressively summarized so notes never bloat.
Requires Claude Code with plugin support (CLI, desktop, or web).
/plugin marketplace add jerlifish/slimecontext
/plugin install slime@slimecontext
Then run /slime:setup to pick where your notes live — you're done. The five
/slime:* commands appear in your slash-command list; manage or remove the
plugin any time via /plugin.
Installing from a local clone (for hacking on the plugin):
git clone https://github.com/jerlifish/slimecontext
/plugin marketplace add /path/to/slimecontext
/plugin install slime@slimecontext
The notes themselves never live in this repo — /slime:setup asks you where
to keep them (a Drive-synced folder is the recommended spot).
/slime:setup— pick where notes live (say yes to the CLAUDE.md line).- Work on your project as usual.
/slime:savebefore you stop — it distills the session into the tree.- Next session:
/slime:bootstrap— pick the topic, get the context, continue.
| Command | What it does |
|---|---|
/slime:setup |
Show current setup, or pick a notes root and initialize it. Optionally adds one line to your global ~/.claude/CLAUDE.md so every session knows the notes exist (ambient RAG). |
/slime:bootstrap |
Pick a recent topic and load its context chain (project → feature → sub-feature) to resume work. |
/slime:save |
Distill this session — decisions, direction, future work — and merge it into the right notes at the right levels. Auto-detects the project from your git remote/cwd; offers to create one if unknown. |
/slime:tidy [project|all] |
Apply the detail curve across a project's notes: compress old log entries, keep decisions, prune stale tags. |
/slime:status |
Show root, project tree, tags, and recent sessions. |
start session
/slime:bootstrap ← "what was I working on?" → loads the relevant chain
… work …
/slime:save ← folds new decisions / direction / next steps back in
You can also just run /slime:save cold in any repo — if no project matches,
it offers to create one.
Heavy file work (reading trees, rewriting notes, metadata bookkeeping) runs in
subagents, so slime commands add minimal noise to your working context. A
PreCompact hook nudges you to save before a long conversation gets compacted.
- Keep notes out of your repo. Point the root at a Google Drive / Dropbox / OneDrive synced folder. Notes accumulate forever — in a repo that's bloat, in a synced folder it's free cross-machine access plus version history.
- Notes are deliberately dry: bullets, file paths, decisions with dates. They're written to be loaded, not read aloud.
- Say yes to the CLAUDE.md line in setup — sessions can then use your notes as
lightweight RAG (via the tag index in
.slimecontext) even when you never invoke a slime command.
.claude-plugin/plugin.json plugin manifest (name: slime)
.claude-plugin/marketplace.json install source
skills/{setup,save,bootstrap,tidy,status}/SKILL.md
references/format.md the format spec all skills follow
hooks/hooks.json PreCompact save reminder
MIT — see LICENSE. Issues and PRs welcome.