Claude Opus 5.5 video prompts for motion graphics, explainers, 3D scenes and interactive demos. Browse by use case, with previews, required inputs and tools. (説明はリポジトリ自身のドキュメント由来です。)
An actively updated Claude prompt library for motion graphics, product videos, explainers, 3D scenes and interactive demos. Explore a growing collection of creator-shared prompts, with selected visual previews, practical setup notes and editable templates for MP4 export.
New here? Start with the 15-second Product UI template: change the copy, colors and screenshot, preview in your browser, then export with Node.js, Playwright and FFmpeg.
Community prompts include original sources and setup notes; they have not been independently reproduced by this collection. Editable templates include source code and export instructions.
Featured creations
Read the prompt here on GitHub, or watch the preview and check setup notes on the website.
💡 Pro Tip Please make a self-introduction movie for me. Make it really cool, please!: Add duration, aspect ratio, assets and delivery format to the short production brief.
💡 Pro Tip make me a beautiful premium card to show off in society: The public fragment gives a creative direction only; add subject motion, visual constraints and delivery format without assuming the full production process.
💡 Pro Tip Use only: JavaScript, Playwright, and FFmpeg: Fix the production and export toolchain; prepare the product assets and portrait format specified in the prompt.
💡 Pro Tip Every scene is made out of the previous one: Require each scene to transform out of the previous one instead of relying only on an Apple-style reference.
💡 Pro Tip avoid the border text or frames: Explicitly exclude borders and edge text so the reference ad's decorative elements are not copied wholesale.
💡 Pro Tip break them down into components/icons so we can animate those too: Split product screenshots into independently animated components instead of moving a flat screenshot as one slide.
💡 Pro Tip Do not stop at a storyboard, still images, or an implementation plan: Explicitly require a rendered and inspected result rather than accepting storyboards, stills or a plan as delivery.
💡 Pro Tip Pull some online data to see why it was hot and how it compares to other years: Require real data and year-to-year comparisons before visualization; check sources and dates.
💡 Pro Tip Give the photon a personality: Personify the photon to give the audience a character to follow; verify the scientific explanation separately.
💡 Pro Tip Before animating, study articles from the last three months: Research recent material before scripting the animation, then verify citations and conclusions.
💡 Pro Tip Don't feel the need to represent everything in the lyrics literally: Allow metaphor and cultural references so visuals interpret the lyrics rather than illustrating words mechanically.
💡 Pro Tip This is not a game and not combat-focused: Exclude combat and quests to focus the scene on exploration, architecture, atmosphere and discovery.
💡 Pro Tip No Three.js/Babylon.js, Canvas2D, external assets, video/GIF, or CSS-only deformation: Exclude prerecorded video and CSS deformation as substitutes for physics; check that meshes and simulation are implemented.
💡 Pro Tip 1-on-1 card game like Hearthstone: Specify a one-on-one card battle, then add turn rules, costs and victory conditions missing from the public fragment.
Interactive 2D/3D Floor Plan and Interior Design Web Tool
💡 Pro Tip according to the dimension markings (mm) in the image: Use floor-plan dimensions and millimeter units to keep rooms and furniture proportional.
Pick a result and copy its public prompt from the card or detail page.
Supply any inputs listed by the creator, then use the prompt with your Opus agent.
Follow the creator’s renderer/tool setup. A shared fragment may need additional instructions.
About this collection & source checks
Opus directs or writes the code for these videos, animations and interactive recordings. The detail page distinguishes prompt-required tools, author-confirmed tools and unconfirmed inferences. Author claims and media consistency checks do not establish repository reproduction. Reference cases may have unverified model version or production details; they are not counted as fully verified cases. We do not reconstruct missing author prompts.