CC-301k · Module 2

Cross-Editor Consistency

3 min read

On a team where some developers use VS Code, some use JetBrains, and some use the terminal, Claude Code behavior must be consistent. The consistency mechanism is CLAUDE.md — it is editor-agnostic. Every integration reads the same CLAUDE.md file, loads the same rules, and produces the same behavior. The editor is the interface; CLAUDE.md is the contract.

The inconsistency risk is in editor-specific configuration. VS Code has settings.json. JetBrains has its own configuration format. The terminal uses ~/.claude/settings.json. If a developer adds a hook in their VS Code settings that is not in the project's .claude/settings.json, other team members on different editors do not get the hook. The solution: all shared configuration goes in .claude/settings.json (project-level, committed). Editor-specific configuration goes in the editor's own settings (personal, not committed).

Do This

  • Keep all Claude rules in CLAUDE.md — editor-agnostic, committed to the repo
  • Put shared hooks in .claude/settings.json — accessible from all editors
  • Test CLAUDE.md changes from both editor and terminal to verify consistency
  • Document editor-specific setup in a team wiki, not in CLAUDE.md

Avoid This

  • Put Claude rules in VS Code settings — JetBrains users will not get them
  • Assume your editor-specific hooks work for all team members
  • Create editor-specific CLAUDE.md instructions — the rules must be universal
  • Enforce a specific editor — consistency comes from CLAUDE.md, not editor choice