From bifrost
Guides setup of Bifrost memory system: checks git/python deps, scaffolds git repo with MEMORY.md/inbox/journal/procedures, sets machine name, writes config/rules.
npx claudepluginhub acostanzo/quickstopThis skill uses the workspace's default tool permissions.
Full guided setup — from zero to working memory system. Walk the user through each step, adapting based on what they already have.
Configures Claude for proactive mnemonic memory with automatic recall/capture, git org/project detection, bash setup of store paths and config.json.
Initializes Poor Man's Memory in projects: runs interactive wizard for save cadence, git commit behavior, window size, verbosity, repo visibility, model choice; scaffolds memory/ dir, configures hooks. First-time only.
Configures Claude Code's memory: CLAUDE.md files, .claude/rules for scoped instructions, auto memory. Persists preferences, coding conventions across sessions.
Share bugs, ideas, or general feedback.
Full guided setup — from zero to working memory system. Walk the user through each step, adapting based on what they already have.
/setupRun these checks via Bash:
git --version — required. If missing, stop and tell the user to install Git.python3 --version — required for hooks. If missing, warn and link to python.org.Look for ~/.config/bifrost/config. If it exists, show current values and ask if they want to reconfigure or start fresh.
Also check for legacy configs (~/.config/asgard/config, ~/.config/munin/config). If found, offer to migrate values.
Ask: "Do you have an existing memory repo, or should we create one?"
If they have one:
MEMORY.md, inbox/, journal/, procedures/. If any are missing, offer to create them.If they need a new one:
~/projects/my-memory).git initMEMORY.md
procedures/procedures.md
journal/
inbox/
context-trees/
.gitignore
MEMORY.md with a starter template:
# Memory
## Identity
- Name:
- Role:
## Preferences
## Active Projects
## Technical Environment
procedures/procedures.md:
# Procedures
Index of learned workflows. Individual procedure files live in this directory.
.gitignore:
.DS_Store
git remote add origin <url>.git add -A && git commit -m "Initial memory repo"git push -u origin mainMEMORY.md with what your agents should know about you — identity, preferences, projects, technical environment."Ask for a machine name. This identifies the machine in inbox filenames. Suggest the hostname as default: run hostname via Bash. The name should be short, lowercase, hyphenated (e.g., personal-laptop, home-desktop). Validate: only allow [a-z0-9-] — reject names with spaces, slashes, or special characters.
Ask where to plant the rules file (AskUserQuestion, single-select):
~/.claude/rules/bifrost.md — active in all projects.claude/rules/bifrost.md — active only in current projectmkdir -p ~/.config/bifrost
cat > ~/.config/bifrost/config << EOF
BIFROST_REPO=<path>
BIFROST_MACHINE=<name>
BIFROST_JOURNAL_DAYS=2
EOF
Write the rules file to the chosen location. Critical: Do NOT hardcode the repo path. Instead, instruct Claude to read the config file at runtime:
# Bifrost: Memory Awareness
You have persistent memory. To find its location, read `~/.config/bifrost/config`
and use the `BIFROST_REPO` value.
## Session Context
Your core memory (MEMORY.md) and recent journal entries are already in your
context — loaded by the bootstrap hook at session start. Don't re-read them.
Use Read/Grep on the layers below when you need specific workflows or
historical context that wasn't loaded at startup:
| Layer | Path (relative to BIFROST_REPO) | Use |
|-------|------|-----|
| Core memory | `MEMORY.md` | Stable facts — already loaded as context |
| Procedures | `procedures/` | Learned workflows — Read when doing multi-step tasks |
| Journal | `journal/` | Recent events and decisions — Grep for temporal context |
| Context trees | `context-trees/` | Project status and relationships |
## When to Recall
Before planning or making decisions that could benefit from historical context:
- Use Grep on `journal/` and `procedures/` for specific topics
- For deep searches across all layers, use `/odin <topic>`
## Corrections
When the user corrects you about something memory should know, note the
correction explicitly: "Noted correction: <what changed>." This flags it
for future consolidation.
## Constraints
- Memory files are **read-only during sessions** — never edit them directly
- Don't recite memory to the user — use it silently to inform your behavior
Confirm everything is wired up:
MEMORY.md