Slack Global & Message Shortcuts Design Prompt
Design Slack global shortcuts and message (context-menu) shortcuts that launch modals and workflows, distinct from slash commands, with clean UX and payload handling.
- Target user
- Engineers adding shortcut entry points to a Slack app
- Difficulty
- Intermediate
- Tools
- Claude, ChatGPT
The prompt
You are a Slack platform engineer who designs intuitive shortcut entry points that users actually discover and reuse. I will provide: - The actions we want users to trigger - Whether they act on a specific message or are global - Existing slash commands / modals we already have - Our app manifest Your job: 1. **Global vs message shortcuts** — explain the difference and when to use each: global shortcuts (from the composer / shortcuts menu, no message context) vs message shortcuts (the message `...` overflow menu, carry the target message). Recommend which actions belong where instead of cramming everything into slash commands. 2. **Naming & discoverability** — concise verb-first names, sensible `callback_id` conventions, and how the shortcuts menu surfaces them; avoid overlap with native Slack actions. 3. **Payload handling** — for message shortcuts, parse the `message`, `channel`, and `user` from the `message_action` payload; for global, handle the `shortcut` payload with no message. Show the 3-second `trigger_id` window for opening a modal. 4. **Modal launch** — open a `views.open` modal seeded from the shortcut context (e.g., pre-fill text from the selected message); handle `view_submission` and validation errors inline. 5. **Manifest config** — the exact `shortcuts` block (name, type global/message, callback_id, description) and the interactivity request URL or Socket Mode setup. 6. **Error & permission UX** — ephemeral errors when the user lacks rights; graceful handling when `trigger_id` expires. 7. **Testing** — sample payloads for both shortcut types and how to replay them locally. Output: (a) decision table mapping each action to global vs message shortcut vs slash command, (b) manifest `shortcuts` block, (c) handler pseudocode for both payload types, (d) modal JSON launched from a message shortcut, (e) local test payloads. Bias toward: putting message-contextual actions on message shortcuts, verb-first names, and respecting the trigger_id window.
Run this prompt with AI
Test it, get an AI-improved version, or compare models — live in the Prompt Workspace. No copy-paste.
Related prompts
-
Slack Block Kit Overflow & Context Menu UX Prompt
Design clean per-message action menus using Block Kit overflow menus and accessory buttons, so a busy alert or incident message exposes the right actions without cluttering the channel or hiding critical ones.
-
Slack Block Kit Modal Input Validation & Error Display Prompt
Design server-side validation for Block Kit modals — response_action errors, per-input error keying, cross-field rules, and re-render UX that never loses user input.
-
Slack response_url Delayed Follow-up Design Prompt
Use the response_url from slash commands and interactive payloads to send delayed follow-up messages after the 3-second ack, respecting its 30-minute / 5-use lifecycle instead of leaking it or letting long work time out.
-
Slack Block Kit Date & Time Picker Constraints Prompt
Design Block Kit datepicker/timepicker/datetimepicker inputs with min/max bounds, timezone handling, and validation for ops scheduling forms.
More Slack prompts & error guides
Browse every Slack prompt and troubleshooting guide in one place.
Reading prompts? Get all 500 in one free PDF
500 battle-tested, copy-paste AI prompts engineered by a senior systems engineer — every one with fill-in placeholders and safety/back-out notes. Drop your email and it's yours.
- 500 prompts: Linux · Kubernetes · Terraform · OpenStack · GitLab · Docker · Monitoring · Incident Response
- Instant PDF download — yours free, forever
- Plus one practical AI-workflow email a week (no spam)
Single opt-in · unsubscribe anytime · no spam.