№ 786 / Feed compositing workshop
Tear along an image contour
Follow the torn outline where it crosses the roof. Keep the boundary visible long enough to distinguish it from a straight wipe.

IN EVERYDAY WORDS
Start at “Exterior cover”. Follow the torn outline where it crosses the roof. Keep the boundary visible long enough to distinguish it from a straight wipe.
The look
Follow the torn outline where it crosses the roof. Keep the boundary visible long enough to distinguish it from a straight wipe.
Say this to a designer
On my property story, use “Tear along an image contour”. Follow the torn outline where it crosses the roof. Keep the boundary visible long enough to distinguish it from a straight wipe.
Direct the motion
These are starting points, not fixed rules. Match the timing to the content and the person using it.
- trigger
- Scrub “Develop the next frame”, replay, or advance with native scrolling.
- entrance
- Establish “Exterior cover” so the viewer can recognize the starting state.
- path
- Follow the torn outline where it crosses the roof. Keep the boundary visible long enough to distinguish it from a straight wipe.
- timing
- The complete replay takes 2.4 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 “Kitchen photograph” so the viewer can inspect the consequence.
- exit
- Carry the discovery source, original question and chosen references into the next scene.
The vocabulary
- Tear along an image contour
- Follow the torn outline where it crosses the roof. Keep the boundary visible long enough to distinguish it from a straight wipe.
Make it fit your project
Good places to use it: property story, Feed compositing workshop.
Use this when the viewer needs to follow the change from “Exterior cover” to “Kitchen photograph”.
Watch for: Keep the subject, orientation and interface legible throughout the change.
When motion is off: Choose “Exterior cover” or “Kitchen photograph” to inspect either still. Keep the full description available with motion off.
Implementation and accessibility
- Adapt the OutlineTear GLSL shader by gre. Keep its MIT credit and license with the edited source.
- Establish “Exterior cover” using an owned photograph or an illustrative interface.
- Follow the torn outline where it crosses the roof. Keep the boundary visible long enough to distinguish it from a straight wipe.
- Return to “Kitchen photograph” 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.
Shader by gre. Download editable GLSL · MIT license
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 #786 (Tear along an image contour, version 1) on [ELEMENT] in my existing project. Permanent reference: https://aiacceleration.ai/designrefs/786. This local brief contains the full definition. Inspect my existing stack, component, design tokens and interaction before editing. Goal: Follow the torn outline where it crosses the roof. Keep the boundary visible long enough to distinguish it from a straight wipe. DESIGN REF #786 · Tear along an image contour In everyday words: Start at “Exterior cover”. Follow the torn outline where it crosses the roof. Keep the boundary visible long enough to distinguish it from a straight wipe. The look: Follow the torn outline where it crosses the roof. Keep the boundary visible long enough to distinguish it from a straight wipe. Say this to a designer: On my property story, use “Tear along an image contour”. Follow the torn outline where it crosses the roof. Keep the boundary visible long enough to distinguish it from a straight wipe. Motion direction (starting points to adapt): Trigger: Scrub “Develop the next frame”, replay, or advance with native scrolling. Entrance: Establish “Exterior cover” so the viewer can recognize the starting state. Path: Follow the torn outline where it crosses the roof. Keep the boundary visible long enough to distinguish it from a straight wipe. Timing: The complete replay takes 2.4 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 “Kitchen photograph” so the viewer can inspect the consequence. Exit: Carry the discovery source, original question and chosen references into the next scene. Design vocabulary: Tear along an image contour: Follow the torn outline where it crosses the roof. Keep the boundary visible long enough to distinguish it from a straight wipe. Reduced motion: Choose “Exterior cover” or “Kitchen photograph” to inspect either still. Keep the full description available with motion off. Implement: 1. Adapt the OutlineTear GLSL shader by gre. Keep its MIT credit and license with the edited source. 2. Establish “Exterior cover” using an owned photograph or an illustrative interface. 3. Follow the torn outline where it crosses the roof. Keep the boundary visible long enough to distinguish it from a straight wipe. 4. Return to “Kitchen photograph” 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 “Exterior cover” or “Kitchen photograph” 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 #786 · version 1. Pairs with #505, #003.