№ 569 / Story gestures
Raise a link from the reply field
The link slides out of the composer, expands to a readable target and takes the arrow with it.

IN EVERYDAY WORDS
Start at “Reply field”. The link slides out of the composer, expands to a readable target and takes the arrow with it.
The look
The link slides out of the composer, expands to a readable target and takes the arrow with it.
Say this to a designer
On my property story, use “Raise a link from the reply field”. The link slides out of the composer, expands to a readable target and takes the arrow with it.
Direct the motion
These are starting points, not fixed rules. Match the timing to the content and the person using it.
- trigger
- Scrub “Raise a link from the reply field”, replay, or advance with native scrolling.
- entrance
- Establish “Reply field” so the viewer can recognize the starting state.
- path
- The link slides out of the composer, expands to a readable target and takes the arrow with 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 “Link ready” so the viewer can inspect the consequence.
- exit
- Carry the discovery source, original question and chosen references into the next scene.
The vocabulary
- Raise a link from the reply field
- The link slides out of the composer, expands to a readable target and takes the arrow with it.
Make it fit your project
Good places to use it: property story, Story gestures.
Use this when the viewer needs to follow the change from “Reply field” to “Link ready”.
Watch for: Keep the subject, orientation and interface legible throughout the change.
When motion is off: Choose “Reply field” or “Link ready” to inspect either still. Keep the full description available with motion off.
Implementation and accessibility
- Establish “Reply field” using an owned photograph or an illustrative interface.
- The link slides out of the composer, expands to a readable target and takes the arrow with it.
- Return to “Link ready” 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 #569 (Raise a link from the reply field, version 1) on [ELEMENT] in my existing project. Permanent reference: https://aiacceleration.ai/designrefs/569. This local brief contains the full definition. Inspect my existing stack, component, design tokens and interaction before editing. Goal: The link slides out of the composer, expands to a readable target and takes the arrow with it. DESIGN REF #569 · Raise a link from the reply field In everyday words: Start at “Reply field”. The link slides out of the composer, expands to a readable target and takes the arrow with it. The look: The link slides out of the composer, expands to a readable target and takes the arrow with it. Say this to a designer: On my property story, use “Raise a link from the reply field”. The link slides out of the composer, expands to a readable target and takes the arrow with it. Motion direction (starting points to adapt): Trigger: Scrub “Raise a link from the reply field”, replay, or advance with native scrolling. Entrance: Establish “Reply field” so the viewer can recognize the starting state. Path: The link slides out of the composer, expands to a readable target and takes the arrow with 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 “Link ready” so the viewer can inspect the consequence. Exit: Carry the discovery source, original question and chosen references into the next scene. Design vocabulary: Raise a link from the reply field: The link slides out of the composer, expands to a readable target and takes the arrow with it. Reduced motion: Choose “Reply field” or “Link ready” to inspect either still. Keep the full description available with motion off. Implement: 1. Establish “Reply field” using an owned photograph or an illustrative interface. 2. The link slides out of the composer, expands to a readable target and takes the arrow with it. 3. Return to “Link ready” 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 “Reply field” or “Link ready” 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 #569 · version 1. Pairs with #031, #003.