[FEATURE] Use # prefix for skills to distinguish from / commands

Problem

Currently, both built-in commands and skills are invoked using the / prefix (e.g., /help, /commit). This creates ambiguity:

• Users can't quickly tell if something is a built-in command or a user-defined skill
• Both are highlighted the same way (blue) in the terminal, providing no visual distinction
• As the ecosystem grows with more plugins and skills, this confusion will increase

Proposed solution

Credits to @mrgoonie - he first proposed this idea here.

1. Use # prefix for skills: Change skill invocation from /skill-name to #skill-name

• /help, /clear, /compact → remain as / (built-in commands)
• /commit, /code-review, /create-pr → become #commit, #code-review, #create-pr (skills)

1. Different syntax highlighting: Use a distinct color for # skills

• Built-in commands (/): Keep current blue highlighting
• Skills (#): Use a different color (e.g., purple, orange, or green) to visually distinguish them

Alternatives considered

• Use a different symbol like @ or !: # feels more natural and is commonly associated with tags/categories
• Add a prefix like /skill:commit: More verbose and less ergonomic
• Status quo: Keeping both as / works but reduces discoverability and clarity

Priority

Medium

Category

Interactive mode (TUI)