keystone: Command for Claude Code

bootstrap

One-time initial charter scaffold. Detect the project's stack, seed corpus/state/, scaffold idiom directories with code-grounded globs, inventory computational guides, classify sensors, and generate the globs index. Run once per project.

Activities

Every activity below produces a concrete file write. Detecting, narrating, or summarizing is not enough — call the edit primitive and land the change before moving on.

1. Detect the stack. Inspect the repo (package.json, go.mod, pyproject.toml, Gemfile, Cargo.toml, requirements.txt, build.gradle, etc.) and list every primary language, framework, and notable library.
2. Seed .charter/corpus/state/CODEBASE_STATE.md. Propose an edit that replaces every template placeholder with real values:
   • Detected stacks
   • Tool commands (lint / type-check / test / build / coverage) — actual commands, not placeholders
   • Region map (top-level directories → which stacks they hold) — this becomes the source of truth for the globs in step 3
   • CI platform (GitHub Actions / GitLab CI / etc.)
3. Seed stack idioms with globs. For each detected stack, scaffold .charter/corpus/idioms/<stack>/ and the paired .charter/guides/idioms/<stack>/. The guides directory gets a README.md describing the stack, and each seeded guide's frontmatter declares globs: derived from the region map written in step 2 — the globs reflect real code paths, not invented patterns. Populate idiom files as patterns emerge; new files inherit the region's globs unless they cover a sub-tree (in which case narrow them).
4. Inventory computational guides. Record LSP, formatter, and editor enforcement (.editorconfig, pre-commit hooks, etc.) under .charter/guides/computational/. Each entry records globs: set to the paths the tool actually covers (read from its config file) — this lets the stack-drift sensor compare documented vs. effective configuration.
5. Classify sensors. For each sensor in .charter/sensors/, propose an edit to CODEBASE_STATE.md recording whether this adapter can run it. Inferential sensors (review-functional, review-security, review-risk, review-deployment, spec-adherence) and computational sensors get separate sections.
6. Generate .charter/corpus/state/GLOBS_INDEX.md. Walk every guide under .charter/guides/ and .charter/policies/*/guides/, read each guide's globs: frontmatter, and write the reverse-index (glob pattern → list of guides claiming it). Touch only the ## Index table; preserve everything else. The index ships with an empty <pattern> placeholder row — bootstrap replaces it with real data. Pointer-style adapters (Claude Code, Codex, Aider) read this index to gate idiom loading on the touched-files set.
7. Project to per-adapter rule surfaces. For each guide with globs: declared, produce the agent-specific projection:
   • Cursor (if .cursor/rules/ exists in the install) — write .cursor/rules/keystone-<topic>-<name>.mdc for every guide that declares globs:. The <topic>-<name> slug comes from the guide's path under .charter/guides/ (e.g. guides/idioms/typescript/hooks.md → keystone-idioms-typescript-hooks.mdc). The .mdc frontmatter mirrors the guide's globs:; the body is a single-line pointer at the source guide. Guides without globs: get no .mdc.
   • Pointer-style adapters (Claude Code, Codex, Aider, Cline, Continue, Goose, Pi) — GLOBS_INDEX.md from step 6 is the projection. No per-guide file is written; each adapter's orient playbook reads the index.
   • _generic — skip. This adapter does not honor globs: and falls back to topic defaults.