From b4449ce678745c2fdbbcaaf7db91b116b59d9073 Mon Sep 17 00:00:00 2001 From: Bastien Chanot Date: Mon, 6 Jul 2026 02:09:25 +0200 Subject: [PATCH] job1: F8 stale model ref, F7 internal dup, F4 skill-first redundant --- CLAUDE.md | 16 +++++++--------- 1 file changed, 7 insertions(+), 9 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index bd6bd56..2020ca1 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -41,7 +41,7 @@ Apply unless repo-specific instructions override. More compute on hard problems. Task fans out across independent items (many files, parallel searches, multi-point checks) → delegate to sub-agents, don't iterate serially. Default to delegation for - multi-file exploration. Counters Opus 4.8 tendency to under-delegate. + multi-file exploration. Counters model tendency to under-delegate. - One question upfront if needed — don't interrupt mid-task. *Exception: skill-mandated gates and checkpoints (orchestrator validation gates, approval gates, darwin checkpoints) always fire.* @@ -80,10 +80,9 @@ Apply unless repo-specific instructions override. ## Memory registries (`.claude/memory/`) -Five registries persist across sessions. Read all at session start. -Capitalize during/after work. Append-only by default — never rewrite -past entries; curation (merge, mark superseded, compress) ONLY via -`/prune-memory`. +Five registries persist across sessions. Capitalize during/after work. +Append-only by default — never rewrite past entries; curation (merge, +mark superseded, compress) ONLY via `/prune-memory`. | File | ID format | Purpose | |------|-----------|---------| @@ -257,10 +256,9 @@ Apply at every dev step: design, scaffolding, implementation, review. # Tooling & skills ## Skill routing -Request matches a skill → invoke via Skill tool first, before any direct -answer or other tool. Most skills route by name — match the request to the -skill whose description fits (full list is in context). Rules below cover -only the non-obvious cases: gstack fallbacks, disambiguation, cryptic names. +Most skills route by name — match the request to the skill whose +description fits (full list is in context). Rules below cover only the +non-obvious cases: gstack fallbacks, disambiguation, cryptic names. - Product idea, "worth building?" → office-hours - Bug / error / 500 → investigate (bugfix if gstack off)