From d362ad0e4968cfc6aa93f9ef163512a692ca5d1b Mon Sep 17 00:00:00 2001 From: Ed Saipetch Date: Sat, 21 Feb 2026 11:41:48 -0600 Subject: [PATCH] fix: remove personal preferences from project CLAUDE.md Project CLAUDE.md is loaded for every contributor using Claude Code. It should contain project documentation, not personal preferences. Removed: - Hardcoded home directory path (/Users/florianbruniaux/...) - Sibling project references (ccboard, cc-economics) - French language preference and communication style These belong in the author's personal ~/.claude/CLAUDE.md, not in the repo where they get imposed on every fork and contributor. --- CLAUDE.md | 16 ++-------------- 1 file changed, 2 insertions(+), 14 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index 6a46ee68..33f7b3b1 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -508,13 +508,11 @@ hyperfine 'target/release/rtk git log -10' --warmup 3 **ALWAYS confirm working directory before starting any work**: ```bash -pwd # Verify you're in /Users/florianbruniaux/Sites/rtk-ai/rtk +pwd # Verify you're in the rtk project root git branch # Verify correct branch (main, feature/*, etc.) ``` -**Never assume** which project to work in. RTK shares parent directory with other projects (ccboard, cc-economics). - -**Context**: Wrong directory detection was a common friction point in multi-repo environments. Always verify before file operations. +**Never assume** which project to work in. Always verify before file operations. ## Avoiding Rabbit Holes @@ -545,16 +543,6 @@ When user provides a numbered plan (QW1-QW4, Phase 1-5, sprint tasks, etc.): **Why**: Plan-driven execution produces better outcomes than ad-hoc implementation. Structured plans help maintain focus and prevent scope creep. -## Language & Communication - -- **User communicates in French**: Respond in French unless explicitly writing English content (docs, code comments, READMEs) -- **"reprend"**: Resume previous task where it was left off -- **Be direct**: User prefers direct, factual communication (Bold Guy style - cash, bienveillant, énergique) - -**Examples**: -- ✅ "Ça ne va pas marcher parce que X. Voici ce que je ferais : Y." -- ✅ "Le test échoue car le regex ne capture pas les commits merge. Fix : ajouter `(?:Merge|commit)`." -- ❌ "Je pense que peut-être nous pourrions éventuellement envisager de..." (trop verbeux, pas direct) ## Filter Development Checklist