Stats
Actions
Available In
Tags
███████╗████████╗███████╗████████╗██╗ ██╗███████╗███████╗██████╗
██╔════╝╚══██╔══╝██╔════╝╚══██╔══╝██║ ██╔╝██╔════╝██╔════╝██╔══██╗
███████╗ ██║ █████╗ ██║ █████╔╝ █████╗ █████╗ ██████╔╝
╚════██║ ██║ ██╔══╝ ██║ ██╔═██╗ ██╔══╝ ██╔══╝ ██╔═══╝
███████║ ██║ ███████╗ ██║ ██║ ██╗███████╗███████╗██║
╚══════╝ ╚═╝ ╚══════╝ ╚═╝ ╚═╝ ╚═╝╚══════╝╚══════╝╚═╝
XML protocol framework + false-positive catalog for Claude Code.
Stop Claude from "helpfully" refactoring your intentional code.
⚡ 30-second install
npx stetkeep install
This is the one-command minimal install: protocols, subagents, slash commands, path-scoped rules. Next session of claude, type /brain-scan and you're working.
For full mechanical enforcement (hooks + permissions deny-lists), the Install section below has a two-step recommended flow: one extra cp command.
Full walkthrough: BOOTSTRAP_GUIDE.md.
🎯 What stetkeep actually is
Two things other Claude Code projects don't ship:
1. XML-structured protocol framework
Prose prompts ("be careful when refactoring, prefer readability over cleverness...") don't survive 20K-token contexts. XML-tagged directives do. Anthropic's own prompting guide recommends XML tags explicitly as a way for Claude to parse prompts more accurately. We built three protocols around it:
- BRAIN.md —
<routing>/<mode>/<inhibit>— decides where a command goes - CRAFT.md —
<anti_patterns>/<safety_net>/<false_positives>— structural refactor discipline - PERF.md —
<pre_check>/<perf_budget>/<measurement_gate>— measurement-first performance work
~1–2K tokens each (BRAIN ~1K · CRAFT ~1.5K · PERF ~1.8K). Claude's attention lands on XML-delimited sections more reliably than on Markdown prose headers.
2. False-positive catalog
The 16-entry registry of "patterns Claude will mistakenly flag as problems." Examples:
| What Claude sees | What Claude will say | What it actually is |
|---|---|---|
| 1000-line config / data file | "God File (A1). Split it." | A data table. Splitting loses context. |
Deliberate inline for loop | "Duplication (A3). Extract." | Profiled hot path. 10× faster than reduce. |
Plain <img> element | "Use next/image." | Below-fold. Not the LCP element. |
Array.map().map().map() | "Collapse into reduce." | V8 optimizes this; readability wins. |
When Claude matches one of these, the Safety Net flags it 🔴 Low confidence and asks before editing. Catalog is under <false_positives> in CRAFT.md and PERF.md.
No competitor ships this.
🛡 Supporting layer — hook-enforced Safety Net
On top of the XML framework, stetkeep ships a five-layer defense:
- Layer A —
permissions.denyhard-blocks edits tolegacy/,generated/,vendor/(deterministic) - Layer B — PreToolUse hook runs out-of-process; returns
deny/ask/allowJSON (deterministic) - Layer C — Subagent tool scoping —
craft-specialist/perf-specialistcan't create new files; edits to existing files require explicit user approval (structural) - Layer D — Path-scoped rules auto-load CRAFT/PERF on
src/**file access (heuristic) - Layer E — XML protocols + false-positive catalog (heuristic)
Layers A / B / C fire regardless of model attention. Layers D / E bias behavior. Honest breakdown in ARCHITECTURE.md §1.
This part is not novel — TDD-Guard, claude-guardrails, and others already ship hook-based enforcement. stetkeep's wedge is the XML framework + FP catalog above; hooks are just the vehicle.
