bvandeusenandClaude Opus 5.5
e99f1169f7
CI & Build / Python lint (push) Successful in 3s
CI & Build / Plugin hooks (push) Successful in 12s
CI & Build / TypeScript typecheck (push) Successful in 52s
CI & Build / integration (push) Successful in 1m1s
CI & Build / Python tests (push) Successful in 1m55s
CI & Build / Build & push image (push) Successful in 36s
Step 1 of the Scribe -> Grimoire rename: every capitalised "Scribe" in prose
becomes "Grimoire" ("Fabled Scribe" -> "Fabled Grimoire") across the UI,
the PWA manifest and page title, the MCP instructions and tool docstrings,
hook and skill text, docs and README, with the tests that assert on that
prose moving with it. Old migrations keep their wording.
Identifiers are untouched here: the package, plugin name, MCP server key,
hook file names, env vars, the .scribe marker and FabledScribe repo/image
names move in steps 2 and 3, along with prose that quotes them.
The sweep matched "Scribe" only as a whole word, so describe/subscribe and
friends are untouched. The longer name took the MCP instructions one
character over their 1,600 budget; two phrases are shortened to fit.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2.1 KiB
2.1 KiB
Grimoire — Claude Code adapter
This session is connected to Grimoire, the operator's system of record for
their work, through the scribe MCP tools. How to work with Grimoire is stated
once, in the using-scribe skill: reach for it at the start of the session
and whenever you are unsure what Grimoire expects. Each tool's contract is in its
description, and the process skills (writing-plans, reporting-back,
reusing-code, systematic-debugging, verification, brainstorming,
shape-accounting, family-canon) carry their arcs.
What only Claude Code needs said:
- Keep one copy — in Grimoire, not Claude Code's local memory. Claude
Code's local memory is
CLAUDE.mdand auto-memory: the operator's rules, plans and project notes go to Grimoire instead, and using-scribe says how Grimoire works alongside them. - Lines injected beside your work are retrieval. When the operator sends a message, and before a write or a command, Grimoire may add rules, preferences, notes and prior art that resemble what you are doing — and, when a tool call or the reply ending a turn reaches a moment of work, the rules mounted on it. Open the ones that apply; using-scribe says what a quiet turn means and how to correct a moment that fired wrongly.
- Compact at clean seams. Because work is recorded as you go, a compaction
is safe once in-flight state is logged. After finishing a block of work in a
long session, log it to Grimoire, then tell the operator it's a good moment to
/compactand name what you logged. You can't run it yourself; suggest it at seams, not every turn. - When the operator wraps up, hand off first. Log where each task you worked stands before the session ends; the plugin releases your claims at session end, but only you can say what happened (using-scribe, "Hand off").
- Stored Processes arrive as skills (
scribe-proc-*), refreshed at session start. After a Process is added or edited,/scribe:syncmakes it available straight away. - If the Grimoire tools are unavailable, say so rather than silently falling back to local notes.