Skip to content
AI Acceleration DESIGN REFS

№ 003 / Opening sequence

Every click gets an answer

A person should know whether their action registered and what happens next.

J-001ILLUSTRATIVE REQUEST
DISCOVERED THROUGHWebsite tool · local example

Try it. Nothing is sent.

Same source. Same question. A clearer next step.

IN EVERYDAY WORDS

The button reacts as soon as it is clicked, explains the wait, then confirms the result and next step.

The look

One clear action button with a nearby status message. Its size stays consistent as the label changes.

Say this to a designer

Give this button immediate feedback. On click, change its label to acknowledge the action and show an honest waiting message nearby. When the real work finishes, show a confirmation and the next step in the same place. Use words as well as color. If it fails, keep the person's input and explain how to retry.

Direct the motion

These are starting points, not fixed rules. Match the timing to the content and the person using it.

trigger
A click, tap, or keyboard activation of the button.
entrance
Acknowledge activation immediately with a label and a small visual change; the page must not jump.
path
Keep the control in place. Change the status inside it and the explanation directly below it.
timing
Start feedback immediately. A 120–180 millisecond visual transition is a starting point; waiting lasts only as long as the actual operation.
easing
Ease out for the small visual response. State changes should feel quick and definite.
hold
Keep the final result and next step visible until the visitor continues.
exit
Clear the status when a new action begins, without removing entered information.

The vocabulary

Microinteraction
A small response to a single action, such as a button acknowledging a click.
State
The control's current condition: ready, waiting, successful, or failed.
Feedback
A visible, audible, or announced response that tells someone what their action did.
Layout shift
Content unexpectedly moving because another element changes size or appears.

Make it fit your project

Good places to use it: submit button, save action, copy control, request form.

Any action with work, waiting or an outcome.

Watch for: Do not claim success before the operation succeeds or show fake percentage progress.

When motion is off: Keep every status message and change states directly.

Implementation and accessibility
  1. Define idle, pending, success and error states.
  2. Acknowledge the click immediately and prevent accidental duplicate submissions.
  3. Show honest status while waiting; keep the layout stable.
  4. Resolve to a concise result and the next useful action.
  5. Announce status changes accessibly and preserve a recoverable failure path.
  • Use a live status region.
  • Use text or icons as well as color.
  • Explain disabled states and keep focus predictable.
  • Cancel timers and requests on unmount.
  • Do not delay a real result for the animation.

Give it to your AI

Download the working source and example assets. Match this reference number in the included catalog to its renderer.

Replace [ELEMENT] with the part of your project you want to change. The prompt includes the design brief, motion direction, definitions, and implementation steps.

Read the full prompt
Use AI Acceleration Design Ref #003 (Every click gets an answer, version 2) on [ELEMENT] in my existing project.

Permanent reference: https://aiacceleration.ai/designrefs/003. This local brief contains the full definition. Inspect my existing stack, component, design tokens and interaction before editing.

Goal: A person should know whether their action registered and what happens next.

DESIGN REF #003 · Every click gets an answer

In everyday words: The button reacts as soon as it is clicked, explains the wait, then confirms the result and next step.

The look: One clear action button with a nearby status message. Its size stays consistent as the label changes.

Say this to a designer:
Give this button immediate feedback. On click, change its label to acknowledge the action and show an honest waiting message nearby. When the real work finishes, show a confirmation and the next step in the same place. Use words as well as color. If it fails, keep the person's input and explain how to retry.

Motion direction (starting points to adapt):
Trigger: A click, tap, or keyboard activation of the button.
Entrance: Acknowledge activation immediately with a label and a small visual change; the page must not jump.
Path: Keep the control in place. Change the status inside it and the explanation directly below it.
Timing: Start feedback immediately. A 120–180 millisecond visual transition is a starting point; waiting lasts only as long as the actual operation.
Easing: Ease out for the small visual response. State changes should feel quick and definite.
Hold: Keep the final result and next step visible until the visitor continues.
Exit: Clear the status when a new action begins, without removing entered information.

Design vocabulary:
Microinteraction: A small response to a single action, such as a button acknowledging a click.
State: The control's current condition: ready, waiting, successful, or failed.
Feedback: A visible, audible, or announced response that tells someone what their action did.
Layout shift: Content unexpectedly moving because another element changes size or appears.

Reduced motion: Keep every status message and change states directly.

Implement:
1. Define idle, pending, success and error states.
2. Acknowledge the click immediately and prevent accidental duplicate submissions.
3. Show honest status while waiting; keep the layout stable.
4. Resolve to a concise result and the next useful action.
5. Announce status changes accessibly and preserve a recoverable failure path.

Adapt the reference to my branding and content. Preserve existing functionality and semantic HTML.
Reduced motion: Keep every status message and change states directly.
Accessibility: Use a live status region. Use text or icons as well as color. Explain disabled states and keep focus predictable.
Performance: Cancel timers and requests on unmount. Do not delay a real result for the animation.
Avoid: Do not claim success before the operation succeeds or show fake percentage progress.

Show me the working result, verify keyboard, mobile, loading/error and reduced-motion behavior, and explain any tradeoff. Do not publish or change unrelated elements.

Permanent reference #003 · version 2. Pairs with #005, #008.

Explore all 320 references

YOUR FIELD GUIDE

Collect the ideas.

Choose the parts of a property experience you want to build. Give each one a place in your project.

My property brief (0)

Add a reference below or start with a combination.

Start with a real estate combination

320 references

Download the full catalog · Get the working source kit · Agent instructions