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.