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>
1.5 KiB
1.5 KiB
name, description, metadata
| name | description | metadata | ||
|---|---|---|---|---|
| brainstorming | Use when exploring options or shaping a direction before committing — open up the solution space instead of jumping to the first idea. Triggers on "how should we approach X", "what are the options", weighing trade-offs, or any open-ended design question. Recall prior thinking first; capture the decision after. |
|
Brainstorming
Widen before you narrow. The first idea is rarely the best; the goal is a few real options and a reasoned choice — not a single path defended after the fact.
Recall first
search Grimoire before generating from scratch — a prior decision, note, or
brainstorm on this often already exists. Build on it instead of repeating it.
Open up
- Generate a few genuinely different options, not variations of one. Include at least one you don't initially favor.
- For each: the core idea, what it's good at, and its main cost or risk — briefly.
- Resist converging until the space is actually explored.
Then choose
- Recommend one, and say why — the trade-off that decided it, not just the pick.
- Surface the 1–2 places you made an interpretive call, so the operator can redirect before it's baked in.
Capture the decision
When a direction is chosen, record it in Grimoire (create_note, e.g. tag
decision): the choice, the alternatives weighed, and the reason. That's what
keeps the same question from being re-litigated later — and what a future
session reads to understand why, not just what.