[FEATURE] Pinned quick-action bar for custom slash commands in the CLI

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Custom slash commands in .claude/commands/ are powerful, but invisible until you type /. In projects with a fixed set of recurring tasks — compiling an APK, running a lint pass, deploying — I retype the same commands dozens of times a day, and colleagues joining the project don't discover them at all. The commands exist, but nothing in the interface surfaces them.

Proposed Solution

There should be a way to mark a slash command as pinned, e.g. via frontmatter in the command file:

label: Compile APK
pinned: true

The interface should show pinned commands as a compact quick-action bar above the input prompt — one short label per command. In the terminal TUI these would be selectable with a hotkey or number (e.g. Alt+1, or arrow keys plus Enter); in the desktop app and IDE extensions they would be clickable buttons.
Only commands explicitly marked pinned appear, so the bar stays to a few entries and doesn't eat vertical space. If no commands are pinned, nothing renders and the interface is unchanged.
Ideally this works the same way across the CLI, the desktop app and the IDE extensions, since the command definitions are already shared.

Alternative Solutions

Currently I work around this by retyping the commands, or by relying on shell history search — which doesn't help discoverability for anyone else on the project, and breaks as soon as the command list changes.
I've also considered wrapping the frequent ones in shell aliases or a Makefile, but that moves them outside Claude Code and loses the context the slash command carries.
Other tools solve this with pinned actions or a task runner panel (e.g. VS Code's task list, or Warp's workflow bookmarks), where frequent commands are one keystroke or click away and visible to everyone working in the repo.

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_