PromptVaultWhich contextual-help pattern belongs beside the task?
For interface designers choosing among inline help, tooltips, popovers, and linked guidance.
Works with
- Cursor
- Gemini
- DeepSeek
- Grok
The prompt44 words · 1 blank
What you fill in
- Guidance situation
[help_context]ExampleFirst-time payroll admins must distinguish gross pay from taxable pay without leaving the form.
How to use it
- 1Open it in PromptVault. Find it in Design, or search for “Which contextual-help pattern belongs beside the task?”.
- 2Fill in the blank. guidance situation — the only things the prompt cannot know.
- 3Copy and paste it into Gemini. It also works with Cursor, DeepSeek and Grok.
About this prompt
“Which contextual-help pattern belongs beside the task?” is a beginner design prompt. For interface designers choosing among inline help, tooltips, popovers, and linked guidance. It is 44 words long and written to get a usable answer on the first message, in Cursor, Gemini and DeepSeek or any other chat assistant. Good for: decision making, comparison, accessibility and ux writing. Like every prompt in PromptVault, it was written and edited in-house, and it works offline once the app is installed.
More design prompts
All 64 in Design
Which destructive-action wording prevents the wrong deletion?For interface writers choosing copy that supports informed action rather than hesitation.- Search filters that match how people narrow resultsFor product designers selecting a filter interaction from documented search behavior.
- A trade-show key visual that survives booth scaleFor campaign teams selecting a booth direction against brand and fabrication constraints.
- A transactional email that reads like a real system messageFor product teams visualizing a trustworthy receipt, alert, or confirmation email.
- Account recovery copy becomes one calm sequenceFor product teams turning inconsistent recovery messages into concise interface-ready strings.
- Choose the mobile navigation pattern that will hold upFor product designers choosing between two navigation models with a defensible call.