Support personal rules scoped by repo origin in ~/.claude/

Feature Request

Problem

There's no way to define personal (non-committed) rules that automatically apply to all clones of the same repository.

Currently, the configuration options are:

| Location | Scope |
|---|---|
| .claude/CLAUDE.md | All clones, all developers (committed to repo) |
| .claude/CLAUDE.local.md | One specific clone, one developer |
| ~/.claude/CLAUDE.md | All projects globally, one developer |

What's missing is: all clones of the same repo, one developer — personal rules that apply whenever I'm working in any clone of a repo with the same origin remote URL.

Use Case

As a developer, I have personal conventions and preferences for specific projects that I don't want to commit to the repo (they're not relevant to other contributors), but I want them to apply automatically across all my local copies of the same repository (e.g., multiple worktrees, fresh clones, etc.).

Proposed Solution

Support a configuration directory in ~/.claude/ that is keyed by the git remote origin URL. For example:

• ~/.claude/repos/<normalized-origin>/CLAUDE.md
• or a mapping file like ~/.claude/repo-rules.json that maps origin URL patterns to rule files

When Claude Code starts in a git repository, it would check the origin remote URL and load any matching personal rules from ~/.claude/.

Current Workaround

Symlinking .claude/CLAUDE.local.md to a shared file in ~/.claude/ works, but requires manual setup in every clone.

Priority

This is a gap in the configuration hierarchy. The four natural scopes are: global, per-repo (personal), per-repo (shared), and per-clone. Only per-repo (personal) is missing.