Rules10
Rules
Short, operative, and loaded on every turn. Each rule carries its lines and a pointer to the skill holding the reasoning.
cache-hygiene Keep the cached prefix stable mid-task: avoid model, effort, fast-mode, tool-set or MCP changes. Native cache behavior differs; do not assume identical invalidation… conciseness Explain a decision once, in the docstring where the thing is defined or on the user-facing doc page. Every other file gets a pointer, not a restatement; a second doc… decisions-and-plans No chooser widget for substantive decisions. Write the decision block as the standalone final message of its turn: each question stated unambiguously, the assessment, a… delegation Whether to gather unasked is the delegation stance's call. Bands, untrusted content, currency, checks: delegation-tiering. research-and-verification Web search is capped per session — 200 calls on Claude Code — and shared by every subagent. Budget roughly 10 agents at 20 searches, or 6 at 30, and stagger bigger runs… secrets Never put tokens, passwords, API keys, or secrets in any file that is committed to source control — rule files, docs, source, config, comments, docstrings, commit… transcript-hygiene Read narrowly. Never cat a whole file, or chain cats, to answer a narrow question — reach for head, grep -n, or a sed range. Filter every find and ls; 100+ lines needs a… verification Run the gates locally; never open a PR on unverified work. Why: docs/how-it-works.md. voice-and-format Put the output shape in every subagent brief, since subagents inherit none: "one-line verdict, then What changed / What you need to do / Still open / Verification." working-style Honesty over polish. Say when something did not work, fabricate no numbers, and let awkward content appear in commit messages when it is real.