[FEATURE]: Config dir AGENTS.md conflates global and repo-specific rules #11639

Feature hasn't been suggested before.

• I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

I version my ~/.config/opencode/ as a git repo (skills, commands, etc) for version-control and easy syncing across computers.

When I want to add an AGENTS.md there, it ends up serving two purposes that don't mix well:

1. Global preferences - rules I want applied to all my OpenCode sessions everywhere
2. Repo development context - instructions for working on this config repo specifically (like "check OpenCode docs when writing skills")

(docs for reference)

The problem is everything in ~/.config/opencode/AGENTS.md gets loaded globally, so any instructions I give agents that work on my OpenCode configuration repo (for creating skills, updating OpenCode configuration, etc.) also supposedly shows up for any project I'm working on with OpenCode.

Suggestion

A convention to use a different file for "repo-specific" stuff when the config dir is itself a repo.
For example, for the actual OpenCode config repo, the regular AGENTS.md will be used, while the global preferences file will have a different name, like USER-AGENTS.md / AGENTS.user.md GLOBAL-AGENTS.md / AGENTS.global.md, or something along these lines.