[Feature Request] Configurable skill precedence order for team workflows

Bug Description
Feature Request: Configurable skill precedence

Currently, skill precedence is fixed as enterprise > personal > project. This means user-level skills (~/.claude/skills/) always override project-level skills
(.claude/skills/) when names conflict.

This is counterintuitive for team workflows where:

• Project-specific skills should override personal defaults
• Teams want consistent behavior across contributors
• A developer's personal skill shouldn't silently override a project's documented skill

Requested solution: Add a configuration option (in settings.json or CLAUDE.md) to control skill precedence, such as:

{
"skillPrecedence": "project-first" // or "personal-first" (current default)
}
…
Note: Content was truncated.