Previews from the publisher
Build a product announcement with room for several supported capabilities and one final reveal. Manus 2.0 Style Launch Video combines a bright porcelain stage, large moving words, black “New” chapter dividers and close views of your actual interface. Landscape imagery and frosted cards provide contrast, while the soundtrack gives the longer keynote-style story its pace.
Choose this when a launch has enough distinct substance for chapters. Write each pillar and its proof before choosing scenery or a dramatic reveal. If the product’s value is one simple action, a shorter command-and-result teaser may be clearer than stretching it into a keynote.
/manus2-0-style-launch-video Make a launch film for [product name] in this style, about 110 seconds, with generated landscape plates and music. Use the product information and materials I provide.Supply the product name or official URL and choose language, approximate length and resolution. Gather the product material and any track you want to use. The package declares Claude Opus 5.5 for its research and storyboard workflow; verify compatibility with the actual host before running it.
Research the product’s own pages and screenshots, including text hidden by animations. Identify the promise, three to five supported pillars and a genuine surprise, keeping a clear evidence source for every claim and number.
Write a new story and choose one concise divider word per pillar. Capture interface elements, desktop/mobile views and transparent logo marks at sufficient detail for camera push-ins; a higher-resolution render cannot repair a low-resolution source capture.
Set up Node.js 20 or newer, FFmpeg and playwright-core with a supported browser. Use your own media and track or review the optional FAL job list and cost before generating. Analyze the selected music, set the storyboard tempo and assign scene beats so the final reveal lands on the intended musical dip.
Build and scrub the preview, then inspect QA sheets for overflow, weak contrast, cropped cards and the camera focusing on the wrong detail. Render a short range before a long high-resolution run, check the final frame rate, size, duration and audio, and retain the editable film and source report.
Local rendering has no per-render generation fee. Landscape plates, b-roll and music submitted through the documented FAL route are provider-billed jobs. Review the requested media and costs before submission; your own imagery and a track you may use can replace generation.
Yes. Change the storyboard, rebuild and render the chosen resolution. The renderer captures scenes at specified times, so the same storyboard can be rerendered consistently. Text and interface detail still depend on the original assets; 1080p b-roll is enlarged in a 2K or 4K output rather than acquiring new detail.
The package frontmatter declares claude-opus-5-5 and its guide ties research, copy and storyboard decisions to that model. This is a package-specific prerequisite, not proof that every host can enforce it. Confirm the host’s model support rather than assuming an automatic switch.
It needs a concise claim and a visible piece of product evidence, such as an actual interface action or output. Choose the most legible part for the camera to focus on. Remove a pillar that exists only as an unsupported headline.
No. The workflow can use the product’s own imagery and supplied music. Scenic plates and b-roll are supporting material; the product interface and substantiated copy remain responsible for explaining what is new.
Select a star to share your experience.
No reviews yet. Ratings appear once readers share real experiences.
+1Use this Skill to create explainer video.
+7
Use this Skill to create social brand video.
+7Use this Skill to create explainer video.
+7Use this Skill to create explainer video.
+7Use this Skill to create explainer video.
+7Use this Skill to create social brand video.