Slash command picker: hard to distinguish user vs project scope for same-name skills

Problem

When the same skill name exists at both user level (~/.claude/commands/) and project level (.claude/commands/), the slash command picker shows both entries with only a small (user) / (project) suffix to distinguish them.

This is a legitimate scenario — project-level skills intentionally override user-level defaults (e.g., a project-customized /drive that extends the user-level /drive). The picker makes it very difficult to tell them apart at a glance.

Current behavior

/drive    High-drive autonomous execution mode...    (user)
/drive    High-drive autonomous execution mode...    (project)

The (user) / (project) labels are:

• Small and low-contrast
• Positioned at the far right, easy to miss
• The only distinguishing element — descriptions are often identical

Expected behavior

The scope distinction should be immediately visible. Some ideas:

1. Visual grouping — separate user/project skills into labeled sections
2. Prefix or icon — e.g., 📁 /drive (project) vs 👤 /drive (user)
3. Path hint on hover/focus — show the resolved file path when an entry is highlighted
4. Priority display — since project-level takes precedence, dim or collapse the user-level duplicate, or show only the effective one with an indicator that it's overriding

Use case

Skill authors distribute general-purpose skills at user level (installed via symlinks to ~/.claude/commands/). Individual projects then override specific skills with project-customized versions in .claude/commands/. Users need to quickly confirm which version they're invoking.

Environment

• Claude Code v2.2
• macOS 15.5