codex-claude-code-config: Instructions file for Claude Code

Claude Global Rules

Core Working Rules (always-on, mechanical)

Hard user directives, codified as drop-in rules/ + mirrored on hooks:

• rules/secrets-as-data.md -- secrets are working data, used freely; the closed Claude/Codex working chat is inside our trust boundary, so an exact credential needed for the task may be read, used, and shown here without masking; do NOT scrub tokens or nag about rotation; the only hard line is nothing leaks into a PUBLIC repo (pre-push scan). Do not dump unrelated credentials without a work need.
• rules/quality-code.md -- code quality between two poles: no monkey-patches (don't cut corners at the cost of stability) AND no over-engineering (YAGNI ladder); sweet spot = minimal correct architecture + verify. /lean-code = on-demand intensifier (our own skill).
• rules/finish-the-task.md -- the single work-discipline canon (6 pillars, all in one place): finish to runtime · cover all accepted branches of the current milestone · quality over token economy · difficulty is no reason to defer · fix every exact reproduced cause immediately with one minimal causal test · execute available reversible machine steps instead of telling the user to copy/paste/run them; ask only for the irreducibly human OTP/CAPTCHA/physical approval after reaching that prompt · explicit user instructions outrank skill methodology, and a skill-caused pause names the exact instruction · never block the current sufficient milestone on a future, unavailable, optional, or production-only capability unless it is an explicit current acceptance criterion or causally required for correctness/safety. Broad repeated reviews/tests are forbidden unless a concrete changed risk requires them. Enforced by stop-phrase-guard + session-handoff-*; near-overflow -> write a handoff.
• rules/quality-over-tokens-independent-verify.md -- optimize for quality, NOT token economy; complex/irreversible work gets independent fresh-context agent verification (Generator-Evaluator).
• rules/deletion-confirm-and-verify.md -- any deletion needs explicit unambiguous user confirmation; after a delete/copy, re-verify it actually happened. Enforced by human-confirmation-guard + verify-deleted-guard.
• rules/autonomy-risk-tiers.md -- act WITHOUT asking on anything reversible (restarts, re-runs, config-with-backup, launching jobs); gate only the irreversible tier (DROP/DELETE, rm of non-regenerable data, force-push, prod migrations) via backup -> verify -> proceed, or wait. No "what should we do?" endings on reversible work. Enforced by stop-phrase-guard.
• rules/no-guessing.md -- never guess: every decision rests on a verifiable source (code / probe / docs / checklist / user quote), not memory or intuition; unsure -> research or ask. High-stakes decisions get an independent fresh-context verifier.
• rules/git-source-of-truth.md -- git is the single source of truth: everything committable gets committed and pushed; deployed == committed; only 4 classes stay out (regenerable, secrets, machine junk, heavy binaries).
• rules/file-organization-cohesion.md -- durable artifacts go into the existing structure (repo / KB / project folder); related files stay TOGETHER, not scattered across /tmp, home root, Desktop, Downloads. Advisory hook file-cohesion-guard reminds.
• rules/cross-harness-agents-md.md -- multi-harness projects keep canonical context in AGENTS.md (Claude Code imports it via @AGENTS.md, Gemini CLI reads it via context.fileName, Codex natively); NO symlinks; markdown briefs/handoffs are the cross-harness context currency.
• rules/learn-from-corrections.md -- the agent learns a lesson every time the user corrects it: session-feedback-capture (Stop) auto-queues sessions, /distill-feedback extracts durable corrections into rules human-gated. Detection is LLM-semantic (a keyword detector was independently tested and rejected at held-out F1 0.42 vs 0.97). Operationalizes TRACE — compile corrections into rules, and into hooks where mechanically checkable.