Feature Request: Team/shared CLAUDE.md configuration support

Summary

Support a shared or team-level CLAUDE.md configuration that multiple collaborators can use, rather than each person manually maintaining their own ~/.claude/CLAUDE.md.

Problem

Right now every collaborator needs to independently maintain their own ~/.claude/CLAUDE.md. For teams, this means:

• Company-wide standards drift — each person ends up with a different version
• Onboarding friction — new collaborators have to manually copy/configure settings
• No single source of truth for how Claude should behave across the team

The workaround (shared git repo + symlink setup script) works but is fragile and requires every team member to manually run setup.

Proposed Solution

One or more of the following:

1. Remote config URL — allow ~/.claude/config.json to specify a URL for a shared CLAUDE.md that Claude fetches and merges with the local one (e.g. from a private GitHub raw URL with auth)
2. Repo-level team config — support a .claude/TEAM.md in a project repo that's loaded alongside the personal CLAUDE.md, so team standards live in the codebase
3. @import / @include directive — allow CLAUDE.md to reference another file or URL to compose configs

Use Case

Small product team (2–5 people). We want:

• Shared company coding standards, communication preferences, and business context loaded for everyone
• Individual personal sections per team member (my preferences vs. my co-founder's)
• Changes propagated automatically when someone updates the shared config

Current Workaround

Shared private repo (claude-config) with a CLAUDE.md and a setup.sh that symlinks ~/.claude/CLAUDE.md to the repo file. Works, but requires manual git pull to stay current and breaks if the repo path changes.

Impact

This would meaningfully improve Claude Code adoption in small teams and agencies. The personal config is powerful — making it shareable unlocks it for collaborative work.