Opus 5.5 Motion Engineering · Launch Videos, Prompts and a Blender Extension

Quick Summary

• The original Motion Engineering article was written by beamnxw and published on X on October 9, 2026. Its central lesson is simple: describe a product film as editable events on a frame timeline, not as a vague request to make something cinematic.
• The worked example is a 20-second square launch clip at 1080 by 1080 and 30 fps. It moves from an opening headline to one visible product action, then gives the result a readable hold before the closing card.
• Reference analysis has a narrow job. The agent measures an entrance, landing, hold and cut, while the creator supplies original product screens, copy, logo and design decisions.
• A written brief locks delivery format, assets, layout, timing, animation curves, sound events and review frames before implementation begins.
• Remotion makes each frame reproducible through useCurrentFrame(), interpolation, springs and seeded variation. Stills and short interval renders expose layout and transition defects before the expensive final export.
• Corrections stay local. A useful note names the location, visible defect, single requested change, affected frames and the properties that must remain fixed.
• A second Beam post extends the method into 3D character animation with Blender MCP, Poly Haven assets, Remotion finishing and FFmpeg delivery.
• Ren Proton shared another motion example and referred to a PDF, but the public reply available at the evidence cutoff resolves to a Google Drive MP4. This post embeds the public video and does not claim access to an unavailable PDF.

Credit and evidence · What comes from the original article

The primary source is beamnxw's X article, Motion Engineering with Opus 5.5: Build Launch Videos You Can Sell. beamnxw receives credit for the article structure, worked example, prompt concepts, frame plan and productized Launch Clip idea. The original X post remains the canonical source and is embedded above.

This JQ VISIONS post is an independent educational reorganization. The prompt pack below is newly worded from the public method instead of reproducing the article's long prompts verbatim. Short commands and technical values are retained where they are necessary to run or understand the example.

The supplemental character-animation stack comes from beamnxw's October 22 post. Ren Proton's post supplies a separate motion example and quotes Beam's article. Creator demonstrations show what their projects produced, but they do not prove universal quality, speed, client demand or earnings.

Evidence was checked on October 22, 2026 against the public X posts, Remotion documentation, the MCP for Blender repository, Poly Haven's license and FFmpeg documentation. Tool commands, availability and licensing can change, so verify the current source before installation or commercial delivery.

The product · One feature, one action, one 20-second film

The strongest idea in the source is restraint. The worked example does not attempt a complete SaaS explainer. It demonstrates one export action: show the filled report, move the cursor to Export, register the press, reveal the finished file and hold the result long enough to read.

That event chain creates visible cause and effect. A viewer can follow the starting state, action and outcome without relying on a paragraph of copy. The opening line establishes the benefit, while the closing card supplies one next action.

Beam's example uses a 600-frame composition at 30 fps, which produces 20 seconds. The opening occupies frames 0 through 119, the product demonstration frames 120 through 419 and the closing frames 420 through 599. These are starting values for the exercise, not universal pacing rules.

Before animation, collect a real logo, report screen, exported-file state, approved font and authorized audio. Confirm that the action remains readable after the screenshots are fitted into the intended layout. If the control is too small, request a better crop instead of inventing an interface.

Reference analysis · Measure decisions, not surface decoration

A reference should answer one production question. You might study how a card enters and settles, how a transition preserves the product, or how a cursor makes a response obvious. Following one object from its first visible position to its landing reveals more than a generic request to copy the style.

Create an overview at two frames per second, then inspect consecutive frames around the important event. Record source timestamps, source frame rate, object bounds, direction, duration, scale, opacity, overshoot and the first point at which text becomes readable.

Keep three evidence labels in the notes: measured, visually estimated and newly proposed. Claude's spatial estimates can be approximate, so confirm important coordinates against extracted frames. The resulting shot should use your own product, words and assets rather than copying the source brand or sequence.

The adapted reference-analysis prompt below generates REFERENCE.md and requires the agent to return its proposed shot before writing implementation code. That pause is a useful approval gate because a wrong interpretation is cheaper to fix as notes than as hundreds of rendered frames.

The brief · Lock layout, timing and review frames

A useful motion brief combines creative direction with coordinates and event timing. It names the viewer, goal, opening copy, closing action, canvas, frame rate, duration, required assets, palette, safe margin, headline box, product-card box and layer order.

The animation section defines both movement and holds. In Beam's exercise the headline and card enter separately, the layout settles, the cursor approaches the button, the press registers, the result appears and the finished state remains stationary for reading. The closing scene begins at a known global frame.

The review plan is part of the brief. Render the opening at several states, inspect text wrapping and margins, and wait for approval. Only then build the product and closing scenes. A long headline should be tested before animation because a third line can break the complete composition.

The adapted BRIEF.md template in the prompt pack keeps this structure but replaces the original example's fixed brand details with placeholders. Use real dimensions from your assets and update event frames when the story, copy or frame rate changes.

Deterministic Remotion · Make any approved frame reproducible

Remotion renders React components according to the current frame. Drive position, scale, opacity, cursor state and product state from useCurrentFrame(), interpolation and spring values. A fixed frame should always create the same image.

Use a fixed seed for any variation. Avoid an independent CSS transition or uncontrolled random call that produces a different result when the renderer jumps directly to frame 240. Store each entrance's offset, destination, duration and landing behavior together so one revision changes one coherent set of values.

Remotion currently recommends Agent Skills for coding agents including Claude Code and Codex. The documented install command is npx skills add remotion-dev/skills, while a new blank project can also offer skills during setup. Read the current Remotion documentation because its project and skill commands can evolve.

Keep motion purposeful. The entrance introduces the object, the hold creates reading time, the cursor identifies the action and the transition carries attention into the result. If decorative movement competes with the label the viewer needs to read, reduce it during the hold.

The review loop · Three stills, one interval and a scoped correction

Start with three images: an opening frame, a product-result frame and a closing frame. Check the message, crop, overlap, hierarchy and call-to-action space before adding more detail. In the source example those checkpoints are frames 60, 240 and 540.

Next, render a short interval around a scene boundary. At 30 fps, frames 90 through 149 give a two-second view across the end of the opening and the beginning of the product scene. A still can look correct while the transition contains a jump, smear or unreadable intermediate frame.

A repair request should name the composition and visible defect, then change one thing. Preserve approved timing, card geometry, copy and audio cues. Ask for stills before, during and after the affected event, plus a short preview that includes surrounding motion.

Fix missing information and unreadable text before timing polish, then fix timing before decorative detail. Keep accepted rules in the brief so later revisions do not quietly reverse earlier decisions.

Sound and export · Every audible hit needs an event frame

Put the click transient on the visible button press and the reveal accent on the moment the finished result appears. An audio file can contain silence before its strongest hit, so inspect the waveform and adjust the clip offset rather than assuming the file start is the event.

Keep music and effects on separate tracks with independent timing and level controls. After the picture and sound passes are approved, render the full composition to H.264 and inspect the exported MP4 at normal speed.

Use FFprobe to verify width, height, average frame rate and duration. For the worked example the intended result is 1080 by 1080, 30 fps and roughly 20 seconds. Technical metadata does not prove creative correctness, so also check spelling, product behavior, audio balance and rights.

Archive the approved brief, event list, cue list, source assets and render command with the delivery. This makes the film easier to revise and gives the next launch clip a trustworthy starting point.

Supplemental workflow · Blender MCP plus Remotion

Beam's second post applies the same directing discipline to character animation. Start with one character, one setting and one visual joke. Specify shots, expressions, camera movement and the final pose before building the 3D scene.

MCP for Blender lets a coding agent inspect a Blender scene and write Blender Python. The current repository documents both Claude Code and Codex setup. It also states that the project is a third-party integration and is not made by the Blender Foundation.

The sequence is practical: block the set and character, add performance and prop actions, light the scene with authorized assets, render the 3D shots, then use Remotion for titles and audio and FFmpeg for the delivery file. Poly Haven states that its HDRIs, textures and models are CC0, while its website copy, logos and example renders are not automatically covered by that asset license.

Security matters. The Blender MCP server can execute Python inside Blender, and its documentation warns that the socket has no authentication or encryption. Keep it on localhost, review unfamiliar scripts and consider BLENDER_MCP_SAFE_MODE=1 for validation of risky operations.

Supplemental example · Ren Proton's motion clip and the missing PDF

Ren Proton shared a 20-second motion example on October 22 and quoted Beam's Motion Engineering article. The post tells viewers to place a PDF into Opus 5.5, but the public self-reply available when this article was checked links to a Google Drive file titled clawd_no_adobe_unique.mp4.

The video is embedded below from the public X media source. The Google Drive MP4 is linked in the sources for provenance. Because no public PDF was accessible from the supplied thread, this article does not invent its contents or present an unrelated document as the promised guide.

The claim that one model has eliminated all motion-design jobs is promotional opinion, not demonstrated labor-market evidence. The examples do show that code agents can accelerate technical execution. Concept, reference selection, typography, product truth, revision judgment, rights and client accountability still require human direction.

Productize carefully · The Launch Clip offer

Beam packages the exercise as a Launch Clip for a developer releasing one feature: one approved script, one 20-second square MP4, one cover image and one revision round. Extra formats, scenes and source files are separate scope.

The article uses $150 as an illustrative pilot price for testing workload and buyer feedback. It is not a guaranteed market rate. Track discovery, asset preparation, scripting, reference analysis, implementation, review, rendering, revisions, project management, software, taxes and client acquisition before deciding what you can sustainably charge.

Build a complete rights-cleared sample before outreach. Find a buyer with a real feature and release date, identify one action the audience needs to understand and propose that action as the clip. Agree on script, assets, deadline, payment, usage, portfolio permission and revision scope before production.

Send stills for direction approval, then a moving preview and final export. Tie feedback to frame numbers and preserve the approved brief. That converts a subjective request into a bounded service without promising fully autonomous production or guaranteed commercial results.