# Scribe — Claude Code adapter

This session is connected to **Scribe**, the operator's system of record for
their work, through the `scribe` MCP tools. How to work with Scribe is stated
once, in the **`using-scribe`** skill: reach for it at the start of the session
and whenever you are unsure what Scribe 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) carry their arcs.

What only Claude Code needs said:

- **Keep one copy — in Scribe, not Claude Code's local memory.** The
  operator's rules, plans and project notes go to Scribe, not also to
  `CLAUDE.md` or auto-memory. Leave auto-memory at its default setting: you
  replace its job by doing the work in Scribe, not by switching it off.
- **Lines injected beside your work are retrieval.** When the operator sends a
  message, and before a write or a command, Scribe may add rules, preferences,
  notes and prior art that resemble what you are doing. Open the ones that
  apply. They are what matched, never the whole set — using-scribe says how to
  ask for the rest.
- **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 Scribe, then tell the operator it's a good moment to
  `/compact` and name what you logged. You can't run it yourself; suggest it at
  seams, not every turn.
- **Stored Processes arrive as skills** (`scribe-proc-*`), refreshed at session
  start. After a Process is added or edited, `/scribe:sync` makes it available
  straight away.
- **If the Scribe tools are unavailable, say so** rather than silently falling
  back to local notes.