Turn a product or marketing URL, pasted script, or brief into a product launch / promo video — SaaS promos, feature reveals, product demos, app and company launches. Use when the user wants to market, launch, promote, or reveal a product; the default for any commercial URL. Site tours / showcases of

First, keep this skill fresh — confirm with the user before running: npx hyperframes skills update product launch video . A fast no op when everything is current; otherwise it refreshes this skill plus the core domain skills it depends on before you rely on them. media use : Before sourcing audio/images/logos, call /media use to resolve BGM/SFX/images from the HeyGen catalog and brand logos from their official sources. Run adopt first to register existing assets. See /media use skill. figma source : If the source is a figma.com URL, run /figma first — asset export, brand tokens, and components/storyboard reconstruction if needed — then build this workflow from its output. Don't drive Figma via raw MCP tools directly: that skips SVG sanitization, .media/manifest.jsonl provenance, and brand token var() binding, so a later brand change can't propagate without a full re import. Product Launch to HyperFrames Use this skill to capture a product, understand its brand, plan a launch video, and build it frame by frame in HyperFrames. The front door is /hyperframes . You are the orchestrator. Run each step, verify its gate, and only then continue to the next step. This skill is for a product being marketed, launched, promoted, or revealed , including requests such as "promo for our site" when the purpose is promotional. A site tour / showcase ask stays here too: BRIEF.md carries the show it as is intent, and the captured screens become the assets the video features. Any other intent, a bare "make a video", or any uncertainty → read /hyperframes first — the intent layer owns every route decision, and a fresh creation arriving here without BRIEF.md goes through it anyway (Setup's opening rule). You are the orchestrator. Work in videos/<project / . Run steps in order and pass each gate before continuing. User gated steps are Step 0, Step 3, and Step 6. Read ../hyperframes/references/brief contract.md before Step 0 — it defines the gate types and how BRIEF.md 's flow / storyboard derive the mode that governs the Step 3/4/6 gates. Do every step yourself except Step 5, where you dispatch one sub agent per frame. Do not put design or motion rules here; those live in the frame worker sub agent, this skill's local ../hyperframes animation/rules/ + ../hyperframes animation/blueprints/ , and hyperframes creative . Workflow: Step 0 setup hyperframes.json ; Step 1 capture capture/ ; Step 2 design system frame.md ; Step 3 storyboard/script STORYBOARD.md and SCRIPT.md ; Step 3.1 audio audio meta.json ; Step 4 visual design enriched STORYBOARD.md ; Step 5 frames compositions/frames/NN .html and index.html ; Step 6 final render renders/video.mp4 . Step 0: Setup Goal: Enter with a confirmed brief, create the HyperFrames project, and make the brief durable. The brief is confirmed by the intent layer, not by questions asked here. Opening rule, in order: (1) BRIEF.md exists → read it and ask nothing — the brief is settled, and its flow / storyboard derive the mode (brief contract § 1). (2) No BRIEF.md but the project exists ( hyperframes.json / STORYBOARD.md on disk) → resume from the storyboard's frontmatter and the recorded preferences; never re interrogate a half built project. (3) Neither — a fresh creation request that arrived here directly → read /hyperframes and run its intent layer ( references/intent interview.md ): it checks recipes and remembered defaults, conducts this route's questions ( ../hyperframes/references/routes/product launch video.md ), and hands back the locked brief. Edit requests skip all of this — go do the edit. Initialize only if hyperframes.json is missing. Name <project from the brand or domain in kebab case, such as acme promo ; never use workspace name or timestamp. npx hyperframes init "videos/<project " non interactive example=blank skill=product launch video — init checks the installed skills against the latest on GitHub and updates the global set if any are out of date. After init, let <PROJECT ROOT be videos/<project and run every subsequent relative path command with that directory as its working directory. In the commands below, . means <PROJECT ROOT ; never write .media , capture , or output files in the caller directory. Write BRIEF.md immediately after init (never before — init refuses a non empty directory): the intent layer's locked brief, shape per ../hyperframes/references/brief format.md . Resolve <MEDIA DIR as the installed /media use skill directory. Then record each preference backed answer with node <MEDIA DIR /scripts/prefs.mjs record hyperframes . ( brief format.md names the subset). If the intent layer adopted a recipe, run node <MEDIA DIR /scripts/recipe.mjs use hyperframes . name <name ; it copies its frame.md into the project (Step 2 is then skipped) and returns the skeletons Step 3 drafts from. A recipe fills answers, not approvals; the review gates still run. Show sign in status before proceeding past Setup — run npx hyperframes auth status and relay its output verbatim. It reports whether voice/BGM will use HeyGen or local engines and, when signed out, how to sign in. Note the exit code contract: auth status exits 1 when not signed in (and when the stored credential is rejected) — that non zero exit is the normal signed out state, not a command failure, so don't treat it as an error, don't retry it, and don't chain it with && / set e in a way that would abort the workflow. Apply one branch: Collaborative: wait for the user to sign in or explicitly choose offline / go . Autonomous: state the status and continue through the available local engines. Do not silently omit a required capability when no offline provider exists; surface the blocker. Do not fold this decision into another question or write keys into a per repo .env . Auth ownership and offline fallbacks: /media use references/setup providers.md § Providers. Gate: hyperframes.json and BRIEF.md exist; the preference backed answers were recorded (brief contract § 2); sign in status was shown (signed in, or continuing offline). Step 1: Capture assets Goal: Collect the source material, brand signals, and usable assets for the video. Classify the input and choose the path. Explicit URL capture it and use the site for narration and assets. Pasted script/brief save verbatim as user script.txt ; VO MODE (verbatim or restructured) comes from BRIEF.md — the intent layer asks it when a script arrives (ask once here only if the brief somehow lacks it). Then resolve capture target: URL in text use it; brand name only WebSearch , confirm URL in one line, then crawl; no URL/site (or the brief says don't scrape) no capture path. Run capture with: npx hyperframes capture "<URL " o ./capture json . Keep the default post navigation budget unless the caller owns a smaller deadline; then pass a positive capture budget <milliseconds that leaves time for downstream work. timeout controls page navigation only. Use skip vision only when optional image captioning is intentionally disabled. Inspect the command result and output directory immediately. A non zero exit, JSON ok: false , or capture/BLOCKED.md is a hard stop for the capture path: report the recorded reason and do not consume partial screenshots, DOM, tokens, or assets. Do not manufacture a synthetic no capture fallback after a failed URL capture. Continue through the no capture path only when the original brief supplied the source material, or when the user explicitly switches to a provided screenshot or brief after the failure. Warnings such as very little text content together with an empty asset catalog are not proof of a usable page. For a site tour or show it as is brief, require trustworthy captured structure or a provided screenshot; if neither exists, stop. Do not invent or rebuild the page merely because the capture is unusable. For a site tour or show it as is brief, the captured page is the visual source of truth. Use the real screenshot instead of rebuilding the full website in HTML. If the shot needs internal movement, keep the screenshot as the base and overlay real captured assets at measured positions, or rebuild only the one component that moves. For a scroll shot, animate the viewport over capture/screenshots/full page.png — the 1x plate of the whole document, pixel exact for a 1920 wide viewport travelling down it. It is absent when the page was too tall to capture in one piece; fall back to the overlapping scroll position shots in the same directory. Pushing in past 1:1 wants its own 2x capture of that region instead, since the plate has no headroom above 1x. Recreate the whole page only when the user explicitly asks for a stylized interpretation; an unusable capture alone is not authorization. If GEMINI API KEY , GOOGLE API KEY , or an OpenRouter key exists, capture auto captions assets into capture/extracted/asset descriptions.md . This is not a review gate. Without a vision key, use DOM context and continue. No capture path: create capture/extracted/tokens.json , capture/extracted/visible text.txt , capture/extracted/asset descriptions.md , and capture/assets/ by hand. tokens.json should be { "title": "", "description": "", "colors": [], "fonts": [] } ; fill title/description from the brief when possible. visible text.txt contains the full brief or script. asset descriptions.md should say no assets were captured unless the user gave asset notes. Gate: capture JSON reported ok: true ; capture/BLOCKED.md does not exist; capture/extracted/tokens.json , capture/extracted/visible text.txt , capture/extracted/asset descriptions.md , and capture/assets/ exist; and you can state the brand in one clear sentence. Treat asset descriptions.md as the main asset inventory. If it is missing after real capture, stop and report capture incomplete. Warnings about a degraded optional phase are acceptable only when this structural gate still passes. Step 2: Design System Goal: Choose one shipped frame preset; a script turns it into this video's frame.md + caption skin. When BRIEF.md names a style preset — the user picked it by eye from the showcases at the intent layer — use it; the judgment call is yours only when the brief is silent. Then you make the one call — which preset : read ../hyperframes creative/references/design spec.md and pick the preset whose look best fits the brand and brief. Then run: The script does the rest deterministically: copies the preset's FRAME.md → frame.md and remixes it onto the brand tokens in capture/extracted/tokens.json (brand colors mapped onto the preset's color keys by role — ink, canvas, accents — keeping keys/structure/components; the preset's display + body fonts swapped for the brand's), copies the preset's caption skin to .hyperframes/caption skin.html , and self validates (exits 1 on a broken mapping). Proceed to the next step as soon as it exits 0 — no hand editing of the spec. tokens.json with no brand colors/fonts (e.g. no capture) → the script keeps the preset's own palette, a complete shippable design. If the brief names brand colors/fonts the capture missed, add them to capture/extracted/tokens.json before running (or use the user's design.md to populate it); only adjust frame.md by hand afterward if a mapping truly needs it. Gate: build frame.mjs exited 0 — frame.md exists from a named preset, and (when the preset ships one) .hyperframes/caption skin.html exists as the caption skin source; the chosen preset was recorded as a preference ( key style preset workflow <this workflow , brief contract § 2). Step 3: Storyboard and Script Goal: Turn the brief and captured material into an approved frame by frame story plan. Read ../hyperframes creative/references/story spine.md (hook

product-launch-video