pace-memory

PACE — Persistent AI Context Engine

PACE is a local Markdown memory system that gives you persistence across sessions. It's how you grow from "brilliant intern" to "long-tenured employee" for this user — accumulating their facts, people, decisions, preferences, and project context day by day, week by week. Full design in the user's PACE PRD.md if they have it.

First-vault bootstrap (when MCP isn't loaded yet)

If the user asks to set up, initialize, install, or onboard PACE in this folder — and the pace_* MCP tools aren't available (no pace_status, pace_init, etc. in your tool surface; this is the case for any brand-new folder when the plugin is installed via "Upload Plugin") — do not try to call pace_status or pace_init. They'll fail. Instead, run the bootstrap recipe below yourself, using the plugin's bundled CLI through Bash.

(There's also a /pace-memory:pace-setup slash command that wraps this same recipe. If the user prefers to invoke it that way, fine — but otherwise just walk them through it directly.)

Step 1 — Greet and collect identity

Open with this script (adapt lightly):

Hi — I'm Claude. Before I scaffold this folder as a PACE vault, three quick questions:

1. What should I call you?
2. What name and emoji should I use for myself in this vault? Pick a nickname plus emoji, or say "you pick" and I'll choose one that fits the work, or "just Claude is fine" to skip the personality.
3. What's the rough nature of the work we'll be doing here?

Wait for the user's answers before doing anything else.

• If they defer on the emoji ("you pick"), choose one that fits the work: 🧠 memory/research, 📊 analytics, 🚀 launches, 🎨 design, 📝 writing. Tell them which one you chose so they can object.
• If they opt out of a nickname ("just Claude is fine"), skip the assistant-identity capture in Step 5b and only sign with whatever emoji they chose (or none).

Step 2 — Find the plugin install path

${CLAUDE_PLUGIN_ROOT} is not automatically set in your Bash environment — it's only substituted in .mcp.json files at MCP launch time. Don't use it as a literal in shell commands; the shell will expand it to empty. Instead, find the plugin install yourself: