A useful motion prompt is a production brief: it tells the agent what viewers should understand, which assets exist, and how to judge the result. The original examples below target the whaleyxbt toolkit with Remotion. Adapt the creative brief for other tools, but use the commands and project files belonging to that tool.
Start with constraints and missing information
Before describing a visual style, specify the audience, one message, duration, canvas size, exact on-screen copy, asset paths, and deliverable. A logo filename is more actionable than “use our branding.” Add the instruction below to your brief. Ask for a storyboard when the message is still unsettled. Ask for implementation only after you can describe what each scene contributes. This keeps a polished animation from concealing an unclear story.
List missing assets or contradictory requirements before implementing; do not invent screenshots, testimonials, statistics, or product features.Prompt for a storyboard before code
Use the prompt below to develop a new idea. Review whether the story still makes sense as four still images. Replace vague benefit language with a visible action the scene can actually demonstrate.
Plan a 20-second video for independent designers introducing our fictional scheduling app. The sole message is that a weekly view makes availability easy to scan. Return four scenes with start/end times, exact copy, focal object, motion, and reading hold. Use an abstract calendar, not a fabricated screenshot. End with ‘Plan your week.’ Do not write code yet.Prompt for a concrete product explanation
Use the prompt below when approved assets are available. Replace these example paths with files you own. A reference image guides appearance; it does not prove a product capability.
Create a 15-second 1080 × 1920, 30 fps explanation using public/assets/calendar.png and public/assets/logo.png. Show the calendar, highlight one available slot, then show the supplied booking confirmation. Preserve the screenshot’s text and proportions. Use navy and cream; yellow marks only the selected slot. Do not add customer counts or speed claims. Keep the final invitation readable for the last three seconds. Report missing files before building.Prompt for restrained typography and a targeted edit
The first prompt below creates a text-led piece; the second requests a targeted revision. Separating creation from correction helps you assess whether the requested change happened.
Animate ‘One idea. One clear story.’ over ten seconds. Use two typographic sizes, a plain background, and a single accent. Let each phrase settle before the next arrives. Avoid simultaneous competing entrances. Provide frames showing the longest line and the transition.
At 6.2 seconds the subtitle overlaps the card. Move only the subtitle below the card and shorten its entrance. Preserve wording, logo scale, palette, and scene order. Re-render the affected interval.Ask for evidence with the delivery
Add the delivery requirements below to the end of your prompt. Use the toolkit’s frame-review workflow and Remotion’s actual render controls to check the answer. An agent’s prose is a report, not the video itself. If a result misses the brief, change the smallest relevant constraint first; rewriting every style instruction makes comparisons much harder.
Provide the composition ID, output filename, dimensions, fps, duration, and the frames you inspected. List any unresolved clipping, missing font, or asset-loading issue. Do not call an export complete until the file exists and has been opened.Your next step
The strongest prompt names a visible outcome, preserves approved material, and asks for evidence that the exported result matches the brief.
Explore the workspaceSources & further reading
References link to original documentation and creators. Product availability can change; check the linked source before subscribing or installing.
- Claude Motion toolkitwhaleyxbt
- Importing assetsRemotion
- Visual review loopwhaleyxbt
- Render your videoRemotion