Overview
How might we design contextual shortcuts so people can trust and act on AI output?
When this pattern fits
- Perfect for productivity tools, power-user applications, and platforms where context-aware shortcuts improve workflow efficiency and discoverability.
When to skip or lighten it
- Changing shortcuts mid-task without showing the new map.
- Mobile products with no hardware keyboard.
- Contexts where muscle memory needs fixed bindings.
States
State model coming soon
Key UX elements
Key UX elements coming soon
Anti-patterns to avoid
Rebinding keys silently when context switches.
Cheatsheet that lists every shortcut with no filter.
AI-suggested shortcuts with no confirm before bind.
Conflicts with OS shortcuts unmarked.
How products use it
| Product | Implementation |
|---|---|
| VS Code | When clauses on keybindings by editor language and view. |
| Figma | Tool-specific shortcuts while editing vs presenting. |
| Notion | Slash menu and shortcuts change by block type. |
| Linear | Issue view shortcuts vs inbox view shortcuts. |
Implementation
Copy this prompt to generate a production-ready implementation in Cursor, Claude Code, Lovable, or any AI coding agent.
Generate a production-ready implementation of the "Contextual Shortcuts" AI interface design pattern.
Pattern Definition:Frequently asked questions
Show shortcuts how?
Hold modifier to reveal overlay, or context panel listing only active bindings.
Contextual shortcuts vs command history?
Shortcuts are keys for actions. Command history replays past AI commands.
Customization?
Let power users pin favorites across contexts.
AI role?
Rank which shortcuts to promote based on task, not invent new keys silently.