Menú
Scaffold a corpus reasoning entry (the *why*) at the canonical path.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Full dual-flywheel audit — Learning (capture from review) + Pruning (remove dead rules). Periodic charter hygiene.
One-time initial charter scaffold — detect stack, seed state, scaffold idioms, classify sensors, build the globs index.
Run the drift sensor on the current diff — fast pre-verify check that loaded charter rules still match what the code is doing.
Triage the code-debt ledger — review the debt sensor's findings and update corpus/state/code-debt.md.
Regenerate .keystone/INDEX.json — the primitive descriptor index every agent reads at session start.
Capture a learning candidate (surprise, incident, review finding) into .charter/learning/inbox/ for later synthesis.
| name | keystone-new-corpus |
| description | Scaffold a corpus reasoning entry (the *why*) at the canonical path. |
| tools | ["Read","Write","Edit","Glob","Bash"] |
| model | sonnet |
A corpus entry is the long-form reasoning behind a rule. It lives
at .charter/corpus/<topic>/<name>.md and is opened only when
a guide's traces: (or a prose forward-link) points at it.
Most authors use keystone:new-guide, which scaffolds both the guide
and its paired corpus in one shot. Reach for keystone:new-corpus
only when adding reasoning to an existing guide that lacks one, or
when the corpus stands alone (rare).
keystone new corpus <topic>/<name>
Example:
keystone new corpus idioms/rails/migrations
# writes .charter/corpus/idioms/rails/migrations.md
traces: in frontmatter or a prose For reasoning, see ...
footer).keystone index to refresh the descriptor surface.Full port contract:
docs/ports/corpus.md.