Overview
How might we design slash commands so people can trust and act on AI output?
When to use
- Perfect for IDEs, productivity tools, and developer environments where power users need quick keyboard-first access to AI models, templates, and actions.
When to skip
- Consumer surfaces where most users never learn command syntax and would never discover the feature.
- Products with very few actions, where a visible button is faster to find than a hidden command.
- Mobile-first composers where a slash menu competes with the on-screen keyboard for space.
Rules
No visible hint that "/" does anything, leaving the feature undiscoverable.
Commands with cryptic names and no description or preview of what they do.
Slash menu and a separate "+" menu offering overlapping actions with no shared mental model.
Breaking normal typing when a message legitimately starts with a "/" character.
Evidence
| Product | Implementation |
|---|---|
| Slack | Slash commands trigger integrations and actions like /remind or /poll from the message box. |
| Notion | Typing "/" opens a block-type and AI-action menu inline in the document. |
| Discord | Slash commands expose bot and app actions with argument autocomplete. |
| Midjourney | Slash commands like /imagine and /blend are the primary way to invoke generation. |
