Support prompts
Prompts in generative AI chats that present recommended inputs to the user
Key UX concepts
Types of prompts
Support prompts in AI workflows can be largely categorized into two types: non-editable prompts and editable prompts. The distinction is based on what happens when a user selects them.
Non-editable: These prompts send immediately upon selection without appearing in the prompt input.
Editable: Editable prompts populate the prompt input field when selected, allowing users to review, modify, or replace the variables in the prompt template before sending.
Affordance for editable prompts
Editable prompts do not execute on selection. The interface should clearly signal that the prompt can be edited with an edit icon before any interaction occurs. A designated visual affordance sets the correct expectation that selecting the prompt will insert the editable text.
No persistent state
Selecting a prompt is a one-time interaction that inserts text into the prompt input. Support prompts do not maintain state upon selection. Selecting a prompt is a one-time interaction that either populates the prompt input in editable prompts or sends immediately with non-editable prompts.
Common use cases
Helping users get started
Editable prompts can be useful when users are beginning an AI interaction. They act as starting points, or icebreakers, that users can select from to get started.
Welcome to the AI assistant
Choose a prompt below or type your own in the prompt input to begin a conversation.
Guiding users during a conversation
Non-editable prompts help maintain conversation flow by proactively suggesting contextually relevant next steps. Users can quickly select these suggestions to continue the interaction without composing their own prompt, making the experience feel more guided.
General guidelines
Do
- Enable users to edit all text after inserting an editable prompt into the prompt input.
- Use variables in editable prompt text to indicate expected customization. For example, when a user selects "Analyze my AWS cost trends over the past <time_period>," they understand that <time_period> is the primary element to customize.
Don't
- Avoid using editable prompts when prompts should be sent directly into the conversation. For example, use non-editable prompts for contextual follow-up questions, or suggestions like "Show me more details" or "Compare with last quarter" that users can quickly select and send without customization.
- Don’t disable text inserted from a prompt template.
Writing guidelines
General writing guidelines
Use sentence case, but continue to capitalize proper nouns and brand names correctly in context.
Use end punctuation, except in headers and buttons. Don’t use exclamation points.
Use present-tense verbs and active voice.
Don't use please, thank you, ellipsis (...), ampersand (&), e.g., i.e., or etc. in writing.
Avoid directional language.
For example: use previous not above, use following not below.
Use device-independent language.
For example: use choose or select not click.
Component-specific guidelines
Variable text
Follow the writing guidelines for variables.
Support prompt labels
Follow the writing guidelines for support prompt group.
Accessibility guidelines
General accessibility guidelines
Follow the guidelines on alternative text and Accessible Rich Internet Applications (ARIA) regions for each component.
Make sure to define ARIA labels aligned with the language context of your application.
Don't add unnecessary markup for roles and landmarks. Follow the guidelines for each component.
Provide keyboard functionality to all available content in a logical and predictable order. The flow of information should make sense.