№ 517 / Message choreography
Gather the thread into a stack
Two related photographs slide under a third, keeping their staggered paper edges visible.

IN EVERYDAY WORDS
Start at “Separate replies”. Two related photographs slide under a third, keeping their staggered paper edges visible.
The look
Two related photographs slide under a third, keeping their staggered paper edges visible.
Say this to a designer
On my buyer message thread, use “Gather the thread into a stack”. Two related photographs slide under a third, keeping their staggered paper edges visible.
Direct the motion
These are starting points, not fixed rules. Match the timing to the content and the person using it.
- trigger
- Scrub “Gather the thread into a stack”, replay, or advance with native scrolling.
- entrance
- Establish “Separate replies” so the viewer can recognize the starting state.
- path
- Two related photographs slide under a third, keeping their staggered paper edges visible.
- 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 “One stack” so the viewer can inspect the consequence.
- exit
- Carry the discovery source, original question and chosen references into the next scene.
The vocabulary
- Gather the thread into a stack
- Two related photographs slide under a third, keeping their staggered paper edges visible.
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 “Separate replies” to “One stack”.
Watch for: Keep the subject, orientation and interface legible throughout the change.
When motion is off: Choose “Separate replies” or “One stack” to inspect either still. Keep the full description available with motion off.
Implementation and accessibility
- Establish “Separate replies” using an owned photograph or an illustrative interface.
- Two related photographs slide under a third, keeping their staggered paper edges visible.
- Return to “One stack” 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 #517 (Gather the thread into a stack, version 1) on [ELEMENT] in my existing project. Permanent reference: https://aiacceleration.ai/designrefs/517. This local brief contains the full definition. Inspect my existing stack, component, design tokens and interaction before editing. Goal: Two related photographs slide under a third, keeping their staggered paper edges visible. DESIGN REF #517 · Gather the thread into a stack In everyday words: Start at “Separate replies”. Two related photographs slide under a third, keeping their staggered paper edges visible. The look: Two related photographs slide under a third, keeping their staggered paper edges visible. Say this to a designer: On my buyer message thread, use “Gather the thread into a stack”. Two related photographs slide under a third, keeping their staggered paper edges visible. Motion direction (starting points to adapt): Trigger: Scrub “Gather the thread into a stack”, replay, or advance with native scrolling. Entrance: Establish “Separate replies” so the viewer can recognize the starting state. Path: Two related photographs slide under a third, keeping their staggered paper edges visible. 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 “One stack” so the viewer can inspect the consequence. Exit: Carry the discovery source, original question and chosen references into the next scene. Design vocabulary: Gather the thread into a stack: Two related photographs slide under a third, keeping their staggered paper edges visible. Reduced motion: Choose “Separate replies” or “One stack” to inspect either still. Keep the full description available with motion off. Implement: 1. Establish “Separate replies” using an owned photograph or an illustrative interface. 2. Two related photographs slide under a third, keeping their staggered paper edges visible. 3. Return to “One stack” 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 “Separate replies” or “One stack” 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 #517 · version 1. Pairs with #003, #501.