prefer-local-over-global-edits
Prefer Local Over Global — Edit Project .claude/, Not $HOME/.claude/
Section titled “Prefer Local Over Global — Edit Project .claude/, Not $HOME/.claude/”When asked to update, edit, fix, or extend a rule, skill, agent, hook, or registry fragment, default to the project-local copy under ./.claude/, NOT $HOME/.claude/. Override only on an explicit trigger word: “global”, “user-level”, “user-scope”, “$HOME/.claude”, ”~/.claude”, “for me only”, “just on my machine”, “personal”. None → local.
Never silently edit $HOME/.claude/ when a project-local exists or could exist. Only a global copy exists → AskUserQuestion: copy-local-and-edit (default), edit-global-only, or open the owning kit repo.
Gotcha: t1k modules update overwrites a diverged project-local file: run /t1k:sync-back FIRST, then update. Narrow exceptions: explicit global trigger word, user-personal change (keybindings, MCP config, memory), or a file that only exists in $HOME/.claude/ by design. Anti-patterns: docs/prefer-local-over-global-edits.md.