CreateFaceless / Motion workshop
Give your product a clear story. Build a timed launch-film prompt for Claude Code, then take it into your own workspace.
Build your promptFree · no sign-in · text output, not a generated video
A shot plan, production prompt and one-shot revision instruction. No video is rendered here.
Get six timed shots, factual guardrails, visual direction and a precise way to revise one shot.
BRIEF → STORYBOARD → PROMPT → YOUR WORKSPACE
03 / CHOOSE THE STORY
Copy a template and replace the brackets with accurate product facts. Use the Prompt builder for a personalized storyboard. These original templates target Claude Code and the local HTML/CSS starter; model output still needs review.
Introduce a product and make its value clear.
Create a product launch motion graphic for [Product name]. Audience: [Who needs this product] Outcome: [One useful, accurate outcome] Benefits: [Up to three supplied facts] CTA: [One next step] Assets: [Approved logo, captures or illustrations] Plan these six shots before coding: 0-3s: Show the useful outcome in one short statement. 3-7s: Reveal [Product name] and its value. 7-13s: Show the real mechanism; ask if the workflow is unclear. 13-19s: Demonstrate the first benefit. 19-26s: Show the remaining benefits in a different composition. 26-30s: Hold the product name and CTA. Use strong type hierarchy, one accent color and varied compositions. Deliver a self-contained scene.html using the supplied HTML/CSS starter. Use 1920x1080, 30 fps and 30 seconds; hold the final CTA for at least two seconds. Use inline CSS, seekable animations and embedded approved assets; no JavaScript or remote dependencies. Keep render.mjs unchanged. Ask for missing facts instead of inventing UI, numbers or claims. After approved local commands, render a new MP4 filename and inspect every cut and the ending. The starter is silent; sound needs separately supplied, licensed material.
Show what changed and why it matters.
Create a feature launch motion graphic for [Product name]. Feature: [Feature name] Audience: [Who uses this feature] Change: [What is now possible, compared with the previous behavior] Approved behavior: [The actual action and result] CTA: [How to try the feature] Assets: [Approved captures showing the feature] Plan these six shots before coding: 0-3s: State the specific change without invented improvement numbers. 3-7s: Reveal [Product name] and the feature name. 7-13s: Show the approved new action. 13-19s: Show its first useful result. 19-26s: Explain one supporting benefit or a supplied use case. 26-30s: Hold one clear invitation to try it. Make the feature behavior the focal point. Use a labeled illustration if a real capture is missing. Deliver a self-contained scene.html using the supplied HTML/CSS starter. Use 1920x1080, 30 fps and 30 seconds; hold the final CTA for at least two seconds. Use inline CSS, seekable animations and embedded approved assets; no JavaScript or remote dependencies. Keep render.mjs unchanged. Ask for missing facts instead of inventing UI, numbers or claims. After approved local commands, render a new MP4 filename and inspect every cut and the ending. The starter is silent; sound needs separately supplied, licensed material.
Explain the path from input to useful output.
Create a workflow demo motion graphic for [Product name]. Audience: [Who follows this workflow] Input: [What the user supplies] Action: [What the product actually does] Output: [What the user receives] Use case: [Where the output becomes useful] CTA: [How to start] Plan these six shots before coding: 0-3s: Lead with the useful output. 3-7s: Introduce [Product name]. 7-13s: Show input, action and output in order. 13-19s: Focus on the first real step. 19-26s: Show the remaining steps and the supplied use case. 26-30s: Hold the product name and next step. Ask for unknown workflow details. Do not manufacture a product interface. Deliver a self-contained scene.html using the supplied HTML/CSS starter. Use 1920x1080, 30 fps and 30 seconds; hold the final CTA for at least two seconds. Use inline CSS, seekable animations and embedded approved assets; no JavaScript or remote dependencies. Keep render.mjs unchanged. Ask for missing facts instead of inventing UI, numbers or claims. After approved local commands, render a new MP4 filename and inspect every cut and the ending. The starter is silent; sound needs separately supplied, licensed material.
Each builds six timed shots, visual direction and a local revision instruction. Original templates; Opus output quality has not been independently tested.
Opus 5.5 outputs text, including animation code. In this workflow, a product brief becomes HTML/CSS, a browser turns the animation into frames, and FFmpeg encodes an MP4. A chat response and a playable web animation are different stages from the exported file.
For Claude motion graphics, specify your audience, useful outcome, on-screen copy, approved assets and export requirements. This page prepares that brief; use the tutorial for code, preview, render and revision steps.
Anthropic model specificationsNeed a clearer story first? Start with the 30-second launch video script.
It is a free Prompt builder. It gives you text to use with Claude Code and a rendering workflow. Direct URL-to-video generation is not available here.
No. The optional link is included as background in the Prompt. Provide accurate facts; your own Claude tools may read the website if available and authorized.
The Prompt includes a targeted revision instruction. Apply it in your own workspace, compare the untouched shots and render another version. This page does not edit video files.
Building, copying and downloading the Prompt is free and requires no account. Claude access and model usage are separate. The original starter renders a silent example locally.