Launch Video Hyperframes
Create launch-video prompts and assembly instructions around text-safe motion frames.
Core Principle
Every shot must reserve a readable text zone before generation or filming. Do not add overlays after the fact onto busy footage and hope they fit.
Inputs
- Product, audience, launch moment, CTA, proof points, and forbidden claims.
- Duration, aspect ratio, platform, voiceover preference, and output format.
- Existing footage, product screenshots, brand assets, or generated-media preference.
Workflow
- Write the launch spine: hook, product reveal, mechanism, proof, momentum, CTA.
- Create a beat board with shot duration, visual, text zone, overlay line, audio line, and transition.
- For each shot, reserve a clear third of the frame or another explicit safe zone.
- Generate footage or use supplied media. Verify the safe zone remains clean.
- Build overlays with consistent type, spacing, and motion. Keep text short enough for mobile.
- Assemble, then verify playback, readable overlays, audio sync, contrast, and platform dimensions.
- Deliver source prompts, render path, and known limitations.
Capability Map
- Video generation: use the discovered best video capability for the requested style.
- Motion graphics: use local code/HTML/Remotion/FFmpeg/GSAP when available rather than flattening everything into prompts.
- QA: use video-render checks and screenshot sampling before claiming final.
Safety
- Do not invent traction, revenue, customer logos, compliance claims, or endorsements.
- Ask before uploading private screenshots or unreleased product footage.
- Do not publish without approval and receipt.
Provenance
This is a HivemindOS-authored clean-room skill inspired by a public skill catalog. No unlicensed upstream text, JSON, or scripts are copied.