create-ai-promo-video

Create AI Promo Video

Treat the work as motion direction and compositing, not as a screen recording or slide deck. The host model is the creative director and writes the unique scene source; local tools execute deterministic instructions.

Composition Model

Every new production is authored directly as one unrestricted Revideo TypeScript composition. For a short promo, keep one master engine scene and organize its narrative shots as modular generators or groups so persistent camera, environment, light, particles, shared objects, and transition overlaps can cross logical shot boundaries. Scaffold once, search the reusable motion vocabulary, add only the source helper groups selected for this production, and use only components that serve the specific story. Every library rig is optional: customize, combine, replace, or ignore it, and write any compatible nodes, timing, geometry, transitions, camera systems, shaders, SVG, or Three.js behavior the scene needs. Read component-library.md and advanced-motion.md.

Library-first does not mean template-first: never render a generic draft and replace its contents later. The neutral scaffold contains no visual design. Decide the art direction before choosing components, and do not inherit sample palettes, copy, card counts, layouts, music, or scene arcs from prior videos.

The version 1 JSON renderer is legacy compatibility only. Use it when the user supplies an existing v1 spec or explicitly requests maintenance of that format. Never use it to start a new production or as a disposable intermediate render. Read video-spec.md only for that compatibility case.

Workflow

1. Inspect the product, positioning, brand, and strongest proof. Define one audience, tension, promise, proof, and an appropriate CTA or resolution using story-direction.md.
2. Define a distinct art direction, delivery format, and timed beat plan. Choose landscape, portrait, or square composition intentionally; for social vertical work, choose the platform profile and verify current safe areas. Choose story functions and shot scales for this brief instead of copying a fixed hero/product/cards/CTA sequence. Record the intended energy curve, camera logic, transition motive, and—when prior work or references are available—what makes this production visually different. Before spreading a metaphor across the film, state why it belongs to this audience, promise, product, and brand. Read vertical-and-captions.md for portrait composition or speech-led captions.
3. When real product proof is part of the story, create a private capture spec. Keep credentials in gitignored *.local.json. Capture screenshots or meaningful live flows as described in capture-spec.md. Skip capture when the authorized brief is intentionally abstract, brand-led, or entirely based on supplied media.
4. When recording product interaction, prefer a clean source with the browser pointer hidden. Add a designed cursor, trace, click pulse, focus ring, or camera response only when the interaction needs it; none is mandatory decoration.
5. When outside media strengthens the story, search user-approved local folders and the aggregated licensed providers. For stock video and photography, prefer Pexels and Pixabay when their free API keys are available; use Openverse and Wikimedia Commons for open-license breadth, SVGs, illustrations, animations, and fallback footage. Review previews and source pages, reject unsafe licenses, and download selections with their attribution manifests. Read free-media-sourcing.md.
6. Write musical intent in plain language before searching: emotion, energy curve, instrumentation to prefer or avoid, pacing, and edit accents. For online music, search the Freesound catalog first through Openverse's freesound source, then compare Jamendo and Wikimedia Audio; include user-approved local folders when available. Do not call the Freesound API directly in the default commercial workflow unless the user has separately authorized its API terms. Bundled CC0 tracks remain available only when explicitly included. Compare at least three viable candidates, analyze the finalists, verify the license, and choose by fit rather than result order. No track is a default or fallback. Read music-sourcing.md.
7. If speech captions are requested, call prepare_caption_timing before authoring them. Prefer exact word timestamps; when only cue timing exists, keep the returned cue-interpolated precision label and do not claim exact alignment. Call scaffold_advanced_video once with the intended format and platform to create the minimal neutral Revideo composition. Complete the generated motion-plan.json before authoring: visual concept, movement principle, every shot and layer's motion, focal regions, velocity bridges, exact transition/settle moments, and every intentional still interval with a reason. Every non-final logical shot must declare boundaryToNext as continuous, motivated-cut, or intentional-stop, including the continuity carrier when applicable and a concise intent; continuity does not mean constant motion. Call validate_motion_plan and repair every exact error before the first render. Query search_motion_components for the shot's narrative needs and inspect selected entries with get_motion_component. Then call add_advanced_video_helpers once with only the exact source groups those selected mechanisms require; dependencies are resolved automatically, authored files are never overwritten, and unused helper files must not be added. When a tool, component, transition, or fragile parameter is unfamiliar or uncertain, call help for that exact target before authoring it—for example component:continuous-camera-path, topic:layout-audit, or tool:render_advanced_video. Search help only when the exact id is unknown; do not load the complete help catalog. Author the actual TypeScript timeline from selected primitives plus custom code in the same files. Register every critical text, logo, CTA, caption, and focal product ref with createReviewRegistry, including its source label, constraint, permitted overlaps, and centering intent; keep ReviewOverlay last in the scene tree. Vary compositions, camera behavior, transitions, typography systems, particle seeds, and palettes according to the art direction. Do not create or render a template that will be replaced later.
8. Call render_advanced_video, probe the result, then call create_visual_review_pack with projectFile, motionPlanPath, the same render variables, and every planned scene boundary. Inspect sourceQuality; then pass every returned exact evidenceFrames, settledFrames, overview sheet, and transition sheet to read_visual_files. Classify each marked overflow, collision, centering delta, or focal-motion lull as intentional or material; do not infer quality from successful rendering, metadata, or one contact sheet. Apply the quality gate in motion-quality.md.
9. Record each material anomaly. Before revising existing work, call list_advanced_video_files and read_advanced_video_file, then patch exact source, render only the affected interval, and create a new visual review pack for that interval. Replace the exact range only after the revised pack passes. Read revision-workflow.md.
10. Track every generated review, audit, preview, cache, and intermediate-render path during production. After the accepted final passes one last probe, call clean_delivery_output with the exact project root, the actual output directory, requested final filenames, and any nonstandard temporary paths. Project and output may be separate: an external host-level outputs directory defaults to shared, which verifies the final but never removes sibling outputs; use owned only for a dedicated per-production delivery directory. Never relocate a valid final merely to satisfy cleanup. The cleaner recursively removes generated directories at any project depth while protected source/media directories remain untouched. Keep the editable composition plus required render inputs, capture masters, downloaded media, license sidecars, attribution manifests, music licenses, references, and configuration. Never delete user-provided or irreplaceable inputs unless explicitly authorized.