create-product-launch-video

Create Product Launch Video

Produce a finished shareable ad, not only a storyboard, unless the user explicitly asks for concepts or a treatment.

Default deliverable

When the brief omits technical choices, use:

• 15 seconds
• 9:16 vertical, 1080x1920
• 30 fps H.264 MP4 with stereo AAC audio
• Four product visuals: hero, macro, use/action, final reveal
• Five scenes with designed transitions
• Original non-vocal score and sound effects
• One poster JPG and one image-prompt record

Infer noncritical creative details. Ask only when missing information would change product identity, factual claims, brand ownership, or media rights.

Required companion skills

• Use imagegen for new photorealistic product images or image edits.
• Use hyperframes:hyperframes, hyperframes:hyperframes-cli, and hyperframes:gsap for composition, animation, validation, and rendering.
• If the brief is sourced from a URL, use browsing or website capture only to gather product facts and assets; keep this product-launch workflow as the production authority.

Read the complete companion skill instructions before taking their governed actions.

Workflow

1. Establish the source of truth

Classify the job:

• Real product with supplied assets: Preserve product geometry, labels, colors, logo placement, and packaging. Prefer edits or compositing when regeneration would change identity.
• Real product with URL only: Verify current facts and claims from authoritative product sources. Capture useful assets when permitted.
• Fictional or concept product: Create an original product identity and silhouette. Do not imitate protected logos or signature brand motifs.

Extract or infer: product category, audience, single promise, proof points, brand tone, launch call to action, and delivery format.

Do not invent specifications, awards, certifications, sustainability claims, medical benefits, performance percentages, prices, or availability. Replace unsupported numbers with qualitative language.

Generate a deterministic starting plan when the product fits a bundled profile:

node scripts/plan_launch.mjs --product footwear-athletic --duration 15 --mood premium --name "Product Name" --output LAUNCH_PLAN.md

Available profiles are defined in data/product-profiles.json; supported timed structures are defined in data/duration-structures.json. Treat the generated plan as a creative baseline, then refine it using supplied assets, real product facts, and the user's brief.

2. Lock the creative direction

Create DESIGN.md before composition HTML. Include:

• One-paragraph style prompt
• Two or three core colors with exact hex values
• One display face and one contrasting support face
• Camera language and lighting rules
• Motion tempo and transition family
• Three to five explicit anti-patterns

Choose direction from product material, audience, and promise rather than applying a generic dark-neon treatment. Read references/product-direction.md for category-specific camera and lighting decisions.

3. Create a canonical product lock

Write one compact description of the immutable product:

• silhouette and proportions
• materials and surface finish
• color placement
• seams, controls, closures, or packaging structure
• logo or label placement when authorized
• prohibited motifs and invariants

Generate or select the clean hero image first. Inspect it before generating other angles. Use the accepted hero as a reference for every later image and repeat the product lock verbatim in each prompt.

Never depend on generated in-image text for brand copy. Generate clean product photography without copy or watermarks, then add exact text in HTML.

Read references/image-prompting.md before generating the image set.

4. Build the narrative cut

Choose the structure matching the requested duration from references/launch-structures.md.

For the default 15-second cut, use this arc:

1. Brand or product arrival
2. Material or feature macro
3. Product in use or energetic proof
4. Full product reveal
5. Brand lockup and call to action

Keep headlines to three to seven words. Let one idea dominate each scene. Make copy product-specific and evidence-based.

5. Design sound with the edit

Use user-supplied licensed audio when provided. Otherwise create a restrained original score with scripts/generate_score.mjs:

node scripts/generate_score.mjs --output assets/launch-score.wav --duration 15 --energy high --transitions 2.8,5.8,8.9,11.9 --seed 2401

Align impacts with major reveals and transitions. Use whooshes sparingly. Keep the score supportive enough that the ad remains intelligible without voiceover.

6. Build the HyperFrames composition

• Build every scene at its fully visible hero state before animating.
• Use at least three visual layers: image/background treatment, primary content, and accent/metadata.
• Give every scene entrance animations with varied directions, durations, and eases.
• Use one primary transition family for most scene changes and one stronger accent for the hero reveal.
• Let transitions perform all non-final exits. Only the final scene may fade out independently.
• Animate image wrappers and scene containers separately to avoid transform conflicts.
• Use subtle camera movement on still imagery: pan, drift, focus pull, or scale push. Do not use the same ambient motion in every scene.
• Keep all logic deterministic. Do not use infinite repeats or random time-based behavior.
• Use a separate timed <audio> element for the score.

Default transition routing:

• Luxury, beauty, fragrance: focus pull, blur crossfade, color dip
• Athletic, automotive, energetic consumer: zoom-through plus controlled focus pulls
• Technical, precision electronics: shutter, push, focus pull
• Food, beverage, warm lifestyle: light leak or gentle blur crossfade

7. Validate and refine

Run all of the following before final delivery:

1. npx hyperframes lint
2. npx hyperframes validate
3. npx hyperframes inspect
4. Animation-map analysis when its dependencies are available
5. Draft render
6. Extract and visually inspect at least one hero frame per scene
7. High-quality final render
8. Probe the final file for duration, dimensions, frame rate, codecs, and audio presence

Fix every lint error, console error, contrast failure, and unintended layout issue. Review warnings instead of suppressing them broadly. Mark only genuinely intentional overflow or transition overlap.

Inspect the encoded draft, not just the browser composition. Watch for image inconsistency, unreadable type, unsupported claims, awkward crops, cheap-looking repeated motion, transition flashes, and an empty first or last frame.

8. Deliver

Place user-facing deliverables in the workspace output directory:

• final MP4
• poster JPG from a strong product frame
• prompt record containing the canonical product lock and final image prompts

Report the duration, resolution, codecs, image-generation mode, and validation result. Link the deliverables directly.

Quality standard

A successful result must feel art-directed rather than templated:

• Product identity remains consistent across all shots.
• Lighting explains material and form.
• Camera angles have distinct narrative jobs.
• Copy is sparse, exact, and supportable.
• Motion communicates product personality.
• Audio punctuates the edit without overpowering it.
• The final frame is usable as a brand end card.
• The exported MP4 is ready to share without additional assembly.