UI Shape Morphing Video Prompt

Build a 14-second UI motion study around one transforming surface. This video prompt explains the state sequence, cursor interactions, beat timing and loop seam so you can adapt the reference to your own product.

What You’ll Build
A square UI animation with continuous shape transitions and a deliberate loop.
What You’ll Need
Your UI states, approved labels, brand colors and a licensed soundtrack.
Creator Reference · 14 s · 1:1zero · @twoclipping ↗

Use the Prompt

Prompt
Add Your Brief

Add your context below. It will be included with the prompt when you copy or download.

Create an editable UI motion video for [PROJECT], aimed at [AUDIENCE]. Use the attached reference to study continuity and timing. Build the animation from code; keep each interface element editable rather than using the reference video as the finished output.

1. Gather the Inputs

Ask for the product name, eight to twelve UI states, approved interface labels, a single accent color and a licensed music track. Use [APPROVED_CONTENT] for text and [BRAND_RULES] for visual constraints. If music or a required asset is missing, identify the gap before rendering. For a silent draft, use a 120 BPM timing grid and label it as a timing preview.

2. Define One Continuous Object

Make a 1440 × 1440 composition on a light neutral background. A single central surface should become the next interface state through changes in width, height, corner radius and internal content. Keep its position and silhouette traceable throughout. Use dark text and consistent icon strokes. Limit the accent to the active control or data point.

  • Keep the camera still while the viewer reads a label or value.
  • Move the camera only when it helps frame a much smaller or larger state.
  • Give outgoing and incoming labels separate timing so they never overlap.
  • Use a brief, restrained spring settle; avoid repeated bouncing.

3. Plan the State Sequence

Start from this sequence, adapting labels and values to the supplied product

  1. A compact action button enters and receives a cursor click.
  2. Its surface narrows into a loading state, then resolves to a clear success mark.
  3. The same surface grows into a music player with a readable title and playback controls.
  4. The cursor scrubs the progress bar; the interaction becomes a volume control.
  5. The slider compresses into a toggle, then stretches into a tab indicator.
  6. The selected tab expands into a small chart with a moving tooltip.
  7. The chart folds into a command field; type a short approved query and show its filtered result.
  8. Confirm the action, show a concise toast, and return to the opening button.

Before coding, present a table with each state, its start time, duration, user action and transition into the next state. At 120 BPM, one beat lasts 0.5 seconds. A seven-bar phrase in 4/4 lasts 14 seconds. Use that as the initial timing budget; simplify the state list if readable text would otherwise flash too quickly.

4. Make Interaction Visible

Animate the cursor as a participant, not as decoration. A press must happen over the active target. During a drag, the control value should follow the cursor continuously. On release, settle from the actual release position. Show a visible response for every click, drag and keyboard action. Preserve stable alignment for text, icons and values as containers change shape.

5. Build a Seekable Timeline

Use the existing project stack. Prefer an explicit timeline or a pure renderAt(time) function so any timestamp produces the same frame when revisited. Calculate springs and progress from time rather than relying on accumulated timer updates. Keep a configuration object for colors, labels, states and beat positions. Reuse vector elements and local authorized assets.

  • Preview a still at every state boundary before exporting.
  • Inspect narrow controls at their smallest scale for clipped labels.
  • Verify that backward and forward seeking produce the same frame.
  • Export a 60 fps MP4 only after the composition and timings are approved.

6. Close the Loop and Deliver

Match the opening and closing composition: object size, position, corner radius, text, cursor position and motion direction. Avoid a duplicate held frame at the join. Test several consecutive loops with audio muted first, then with the licensed soundtrack. Keep the page preview paused until the viewer presses Play, and respect reduced-motion preferences in any interactive web version.

Return editable source, the state/timing table, a poster frame and the rendered video. List missing fonts, media and unimplemented behaviors. Review text legibility, cursor alignment, transition continuity and the loop seam before delivery.

Reference and Attribution

Creator reference: zero (@twoclipping). https://x.com/twoclipping/status/2103273003555402193 The prompt is an OpenDesign editorial adaptation. Creator video rights remain with the original author.

Download Prompt + Video

Download the editable prompt and the creator reference video together. Use both to guide your own motion study.

Download Files

How to Write a UI Morphing Video Prompt

Use this ui shape morphing video prompt to plan the content, motion and timing of your own adaptation. The useful idea in this reference is the relationship between a persistent shape, a visible user action and a timed response. Here is how to turn those decisions into instructions you can reuse for a different interface.

Frames below come from zero’s credited reference video. The prompt is an OpenDesign editorial adaptation; an OpenDesign reproduction has not yet been verified.

Give One Shape a Continuous Identity

A dark central surface establishes the object that later interface states inherit.

A dark central surface establishes the object that later interface states inherit.
Reference checkpoint · 01s / 14s

Define which object survives the transitions. If you only name a list of screens, the model can produce a slideshow of separate layouts. Continuity comes from a stable anchor and a visible relationship between the old and new silhouette. Let size and corner radius do most of the work; reserve opacity changes for internal labels.

In the Adapted Prompt

A single central surface should become the next interface state through changes in width, height, corner radius and internal content.

Apply It to Your Product

Name the object that persists across your own states. Specify its anchor, which edges move and when the content changes. Keep the camera still until the reader understands the current state.

Write the Interaction, Not Just the Component

The player state has controls and a timeline that give the cursor an explicit job.

The player state has controls and a timeline that give the cursor an explicit job.
Reference checkpoint · 03s / 14s

A music player is a component name, not a motion instruction. Describe the action, its target and the visible result. A believable scrub keeps the handle under the cursor while the value changes; it does not move the pointer independently and animate the bar afterward. This distinction makes a demo understandable even without narration.

In the Adapted Prompt

During a drag, the control value should follow the cursor continuously.

Apply It to Your Product

For each state, write one action/result pair: click Play → show the paused-to-playing response; drag Progress → update its position and displayed value. Remove controls that do not contribute to the story.

Turn the Sequence into a Timing Budget

A tabbed analytics card displays a line chart and a cursor-driven value tooltip.

A tabbed analytics card displays a line chart and a cursor-driven value tooltip.
Reference checkpoint · 08s / 14s

The source prompt uses a seven-bar phrase at 120 BPM. That gives 28 half-second beats, or roughly fourteen seconds. Those numbers are an initial constraint, not proof that every label will be readable. Allocate holds to important information and spend transitions on beats; simplify a state when it cannot fit without flashing.

In the Adapted Prompt

Before coding, present a table with each state, its start time, duration, user action and transition into the next state.

Apply It to Your Product

Budget a clear hold, an action and a transition for every state. Use fewer states when your real labels are longer. Ask for a timing table before the first implementation so revisions change the plan instead of patching random delays.

Check the Join as Carefully as the Reveal

A later state provides a useful checkpoint before the sequence returns to its opening form.

A later state provides a useful checkpoint before the sequence returns to its opening form.
Reference checkpoint · 11s / 14s

A matching color is not enough to make a seamless loop. The object and cursor must meet the opening in position, scale and direction; a one-frame hold or a cursor teleport can reveal the seam. A seekable timeline also makes review repeatable: the same timestamp should show the same frame regardless of the path taken to reach it.

In the Adapted Prompt

Match the opening and closing composition: object size, position, corner radius, text, cursor position and motion direction.

Apply It to Your Product

Compare the first and last exported frames side by side. Watch three loops with sound off, then with audio. If the seam still draws attention, fix the geometry or velocity before adding effects.

Review the Motion Before You Add Polish

Use the first render to validate the state sequence and interaction logic. Smooth easing cannot rescue an unclear action or unreadable label.

  • Read every label at normal playback speed without pausing.
  • Check that clicks and drags land on the control they change.
  • Seek backward and forward to the same timestamp and compare the frame.
  • Play at least three loops and inspect the object and cursor at the join.
  • Confirm media, font and soundtrack permissions before sharing the result.

Follow-Up Prompt

Use this after the first result. It narrows the revision to the most important part of this task.

Refine only the transitions between UI states. Keep the approved labels, colors and state order. Slow down any state whose text is unreadable, align every cursor click or drag to its target, and match the final surface and cursor position to the opening. Show boundary frames and a short loop preview before exporting again.

OpenDesign

Turn Your Prompt into a Design.

Bring the prompt and reference video into OpenDesign. Add your content, build the first version and refine the motion.

Download OpenDesign ↓
Pastel painting of a blue lake, green shores and a sunlit sky from the OpenDesign homepage.