№ 537 / Message choreography
Move a conversation into search
The question condenses into a search chip. A matching room thumbnail rises directly under it.

IN EVERYDAY WORDS
Start at “Question in thread”. The question condenses into a search chip. A matching room thumbnail rises directly under it.
The look
The question condenses into a search chip. A matching room thumbnail rises directly under it.
Say this to a designer
On my buyer message thread, use “Move a conversation into search”. The question condenses into a search chip. A matching room thumbnail rises directly under it.
Direct the motion
These are starting points, not fixed rules. Match the timing to the content and the person using it.
- trigger
- Scrub “Move a conversation into search”, replay, or advance with native scrolling.
- entrance
- Establish “Question in thread” so the viewer can recognize the starting state.
- path
- The question condenses into a search chip. A matching room thumbnail rises directly under it.
- timing
- The complete replay takes 3.6 seconds. Keep each cue tied to its position in the sequence.
- easing
- Seek directly to the requested frame. Ease the movement between the authored poses.
- hold
- Settle on “Result highlighted” so the viewer can inspect the consequence.
- exit
- Carry the discovery source, original question and chosen references into the next scene.
The vocabulary
- Move a conversation into search
- The question condenses into a search chip. A matching room thumbnail rises directly under it.
Make it fit your project
Good places to use it: buyer message thread, Message choreography.
Use this when the viewer needs to follow the change from “Question in thread” to “Result highlighted”.
Watch for: Keep the subject, orientation and interface legible throughout the change.
When motion is off: Choose “Question in thread” or “Result highlighted” to inspect either still. Keep the full description available with motion off.
Implementation and accessibility
- Establish “Question in thread” using an owned photograph or an illustrative interface.
- The question condenses into a search chip. A matching room thumbnail rises directly under it.
- Return to “Result highlighted” using the end control and verify the result at phone size.
- Expose both named endpoints and a keyboard-operated control.
- Give spoken cues a readable visual equivalent.
- Load the active artwork on demand and share its frame calculation between scroll and replay.
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 #537 (Move a conversation into search, version 1) on [ELEMENT] in my existing project. Permanent reference: https://aiacceleration.ai/designrefs/537. This local brief contains the full definition. Inspect my existing stack, component, design tokens and interaction before editing. Goal: The question condenses into a search chip. A matching room thumbnail rises directly under it. DESIGN REF #537 · Move a conversation into search In everyday words: Start at “Question in thread”. The question condenses into a search chip. A matching room thumbnail rises directly under it. The look: The question condenses into a search chip. A matching room thumbnail rises directly under it. Say this to a designer: On my buyer message thread, use “Move a conversation into search”. The question condenses into a search chip. A matching room thumbnail rises directly under it. Motion direction (starting points to adapt): Trigger: Scrub “Move a conversation into search”, replay, or advance with native scrolling. Entrance: Establish “Question in thread” so the viewer can recognize the starting state. Path: The question condenses into a search chip. A matching room thumbnail rises directly under it. Timing: The complete replay takes 3.6 seconds. Keep each cue tied to its position in the sequence. Easing: Seek directly to the requested frame. Ease the movement between the authored poses. Hold: Settle on “Result highlighted” so the viewer can inspect the consequence. Exit: Carry the discovery source, original question and chosen references into the next scene. Design vocabulary: Move a conversation into search: The question condenses into a search chip. A matching room thumbnail rises directly under it. Reduced motion: Choose “Question in thread” or “Result highlighted” to inspect either still. Keep the full description available with motion off. Implement: 1. Establish “Question in thread” using an owned photograph or an illustrative interface. 2. The question condenses into a search chip. A matching room thumbnail rises directly under it. 3. Return to “Result highlighted” using the end control and verify the result at phone size. Adapt the reference to my branding and content. Preserve existing functionality and semantic HTML. Reduced motion: Choose “Question in thread” or “Result highlighted” to inspect either still. Keep the full description available with motion off. Accessibility: Expose both named endpoints and a keyboard-operated control. Give spoken cues a readable visual equivalent. Performance: Load the active artwork on demand and share its frame calculation between scroll and replay. Avoid: Keep the subject, orientation and interface legible throughout the change. 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 #537 · version 1. Pairs with #003, #501.