Communitygithub.com

产品发布视频 — URL/Brief → 分镜序列成片

把产品/营销 URL、粘贴脚本或 brief 变成产品发布视频(SaaS 促销、功能揭幕、应用上线)。分镜序列架构:时间码黄金蓝图,让每一帧在整段时长里持续演进。

Brief → 分镜序列成片 是什么?

Launch Video 配方第 1 步(合成):starter-nextjs-product-launch-video。URL/脚本/brief → 分镜序列发布/促销/揭幕成片,交给 Apple-like Remotion 抛光与内嵌字幕出货。

兼容平台~Claude Code~Codex CLI~Cursor✓Gemini CLI
npx skills add https://github.com/1345AbhishekKumar/starter-nextjs/tree/HEAD/.agents/skills/product-launch-video

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

文档

media-use: 在获取音频/图片之前,请调用 /media-use 从 HeyGen 目录中解析 BGM/SFX/图片。首先运行 --adopt 以注册现有资源。请参阅 /media-use 技能。

产品发布到 HyperFrames

使用此技能捕捉产品、理解其品牌、规划发布视频,并在 HyperFrames 中逐帧构建。

在步骤 0 之前确认路线。 你是协调者。运行每一步,验证其关卡,然后才能继续下一步。此技能适用于正在营销、发布、推广或展示的产品,包括“我们网站的推广”等请求,如果目的是促销。将其他意图路由到别处:一般的非发布网站导览 -> /website-to-video;没有产品的主题解释 -> /faceless-explainer;GitHub PR -> /pr-to-video;现有素材上的字幕 -> /embedded-captions;简短的无声动态图形 -> /motion-graphics。如果用户只说“制作视频”或路线不确定,请先阅读 /hyperframes。

你是协调者。在 videos/<project>/ 中工作。按顺序运行步骤,并在继续之前通过每个关卡。用户控制的关卡是步骤 0、步骤 3 和步骤 6。除了步骤 5(你为每个帧分派一个子代理)之外,所有步骤都由你完成。请勿在此处放置设计或运动规则;这些规则位于帧工作者子代理、此技能的本地 ../hyperframes-animation/rules/ + ../hyperframes-animation/blueprints/ 以及 hyperframes-creative 中。

工作流程:步骤 0 设置 -> hyperframes.json;步骤 1 捕获 -> capture/;步骤 2 设计系统 -> frame.md;步骤 3 故事板/脚本 -> STORYBOARD.md 和 SCRIPT.md;步骤 3.1 音频 -> audio_meta.json;步骤 4 视觉设计 -> 增强的 STORYBOARD.md;步骤 5 帧 -> compositions/frames/NN-*.html 和 index.html;步骤 6 最终渲染 -> renders/video.mp4。


步骤 0:设置和简报

目标:锁定核心视频简报,并在需要时创建 HyperFrames 项目。

仅当 hyperframes.json 不存在时才初始化。从品牌或域中命名 <project>,使用 kebab-case,例如 acme-promo;切勿使用工作区名称或时间戳。

npx hyperframes init "videos/<project>" --non-interactive --example=blank — init 检查已安装的技能与 GitHub 上的最新版本,如果任何技能已过时,则更新全局集合。

在简报前显示登录状态 — 运行 npx hyperframes auth status 并逐字传递输出(不要转述或重写)。 它会报告语音/BGM 将使用 HeyGen 还是本地引擎,以及当未登录时如何登录。如果未登录,请停止并等待用户选择 — 登录或输入“go”/“offline”以使用本地引擎继续 — 然后再询问简报或任何其他事项。 将其视为真正的决策点,而不是一个随意的注释;不要将选择与简报问题合并,也不要将密钥写入每个仓库的 .env。(在自主模式下,记录状态并离线继续。)请参阅 ../hyperframes-media → Preflight 以获取规范指南。

关卡: hyperframes.json 存在,并且角度、时长、宽高比和语言已锁定;已显示登录状态(已登录,或继续离线)。


步骤 1:捕获资源

目标:收集视频的源材料、品牌信号和可用资源。

对输入进行分类并选择路径。显式 URL -> 捕获它并使用网站进行叙述和资源。粘贴的脚本/简报 -> 逐字保存为 user_script.txt,询问一次“逐字使用还是重新组织?”,将答案存储为 VO_MODE,然后解析捕获目标:文本中的 URL -> 使用它;仅品牌名称 -> WebSearch,在一行中确认 URL,然后爬取;无 URL/网站 -> 无捕获路径。

使用以下命令运行捕获:npx hyperframes capture "<URL>" -o ./capture

如果存在 GEMINI_API_KEY、GOOGLE_API_KEY 或 OpenRouter 密钥,捕获会自动将资源描述为 capture/extracted/asset-descriptions.md。这不是审查关卡。如果没有视觉密钥,使用 DOM 上下文并继续。

无捕获路径:手动创建 capture/extracted/tokens.json、capture/extracted/visible-text.txt、capture/extracted/asset-descriptions.md 和 capture/assets/。tokens.json 应为 { "title": "", "description": "", "colors": [], "fonts": [] };尽可能从简报中填写标题/描述。visible-text.txt 包含完整的简报或脚本。asset-descriptions.md 应说明未捕获任何资源,除非用户提供了资源说明。

关卡: capture/extracted/tokens.json、capture/extracted/visible-text.txt、capture/extracted/asset-descriptions.md 和 capture/assets/ 存在;你可以用一句清晰的话陈述品牌。将 asset-descriptions.md 视为主资源清单。如果在实际捕获后它缺失,请停止并报告捕获不完整。如果存在 capture/BLOCKED.md,请遵循它。


步骤 2:设计系统

目标:选择一个现成的帧预设;一个脚本将其转换为此视频的 frame.md + 字幕皮肤。

你需要做出一个判断决定——选择哪个预设。阅读 ../hyperframes-creative/references/design-spec.md 并选择外观最符合品牌和简报的预设。然后运行:

node <SKILL_DIR>/scripts/build-frame.mjs --preset <name> --hyperframes .

脚本确定性地完成其余工作:将预设的 FRAME.md 复制到 frame.md,并根据 capture/extracted/tokens.json 中的品牌令牌重新混音(品牌颜色按角色映射到预设的颜色键——墨水、画布、强调色——保持键/结构/组件;预设的显示字体和正文字体替换为品牌的字体),将预设的字幕皮肤复制到 .hyperframes/caption-skin.html,并自我验证(映射错误时退出代码 1)。脚本退出代码为 0 后立即继续下一步——无需手动编辑规范。

如果没有品牌颜色/字体的 tokens.json(例如,未捕获)-> 脚本保留预设自己的调色板,这是一个完整的可交付设计。如果简报中提到了品牌颜色/字体但捕获未捕获到,则在运行前将它们添加到 capture/extracted/tokens.json(或使用用户的 design.md 填充);仅在之后如果映射确实需要,才手动调整 frame.md。

关卡: build-frame.mjs 退出代码为 0 — frame.md 来自命名预设,并且(当预设附带时).hyperframes/caption-skin.html 作为字幕皮肤源存在。


步骤 3:故事板和脚本

目标:将简报和捕获的材料转化为批准的逐帧故事计划。

阅读 references/story-design.md、../hyperframes-animation/blueprints-index.md、../hyperframes-core/references/storyboard-format.md 和 ../hyperframes-core/references/script-format.md。使用它们编写 STORYBOARD.md,并在需要叙述时编写 SCRIPT.md。

使用 story-design.md 获取故事蓝图、钩子、说服逻辑、节拍、VO_MODE 和资源选择。作为软指南,查阅 ../hyperframes-animation/blueprints-index.md 中的角色到蓝图菜单:对于每个节拍,当合适时记录一个候选蓝图 ID。故事真相仍然决定哪些节拍存在——永远不要强行让节拍适应蓝图,也永远不要仅仅因为有一个可用的经过验证的形状而发明节拍。从 capture/extracted/asset-descriptions.md(规范清单)中选择每个视觉帧的 asset_candidates——不要浏览原始的 capture/assets/。除非该清单缺失或不可用,否则不要要求用户选择资源。使用故事板和脚本参考中的确切必填字段。

起草后,显示逐帧摘要。在同一条消息中向用户提出两个要求:(a) 批准或请求更改;(b) 是否想要故事板支架的实时预览(npx hyperframes preview)——只有在用户回答“是”时才打开。迭代直到获得批准,并将预览选择带到步骤 6。

关卡: STORYBOARD.md 存在,每个视觉帧都有 asset_candidates,当需要叙述时 SCRIPT.md 存在,并且用户已批准逐帧计划。


步骤 3.1:音频

目标:从已批准的脚本生成叙述、单词时间、音乐和音频元数据。

在步骤 3 批准后开始音频处理。在后台运行,然后继续到步骤 4。

node <SKILL_DIR>/scripts/audio.mjs --script ./SCRIPT.md --storyboard ./STORYBOARD.md --hyperframes . --out ./audio_meta.json &

音频脚本处理叙述、单词时间、从 HeyGen 音乐库查找 BGM 以及时间元数据。BGM 情绪来自故事板的 music: 字段。这使用 HeyGen 音频 API 进行检索,而不是生成,并使用与 TTS 相同的 ~/.heygen 凭据。有关提供商的详细信息,请阅读 ../hyperframes-media/references/tts.md。

如果没有叙述且没有 SCRIPT.md,则跳过语音生成。如果故事板有音乐情绪,BGM 仍可能运行。

关卡: 音频作业已启动,或者项目标记为无声。


步骤 4:帧视觉设计

目标:为每个故事板帧添加视觉方向、布局意图和运动选择。

就地编辑 STORYBOARD.md。不要创建另一个故事板。使用 frame.md 作为颜色、字体、布局感觉和风格的真相来源。

阅读 references/visual-design.md、../hyperframes-animation/blueprints-index.md、references/motion-language.md 和 ../hyperframes-animation/rules-index.md。使用 visual-design.md 获取方法(带时间编码的镜头序列、内联布局词汇以及必填的 ## Video direction 块)。使用 ../hyperframes-animation/blueprints-index.md 为每个帧选择镜头形状。使用 motion-language.md(运动词汇 + 运动教义)和 ../hyperframes-animation/rules-index.md(有效规则名称)进行运动——不要发明运动名称。

对于每个视觉帧,根据 visual-design.md 的方法编写一个带时间编码的镜头序列到 STORYBOARD.md 中:选择帧的蓝图(或组合),用此产品的内容实例化它,并将每个场景的揭示节奏与画外音相匹配,以便帧在其整个持续时间内展开,而不是一开始就展示所有内容然后冻结。根据场景(visual-design.md 和 motion-language.md 中的词汇)内联说明布局和运动。添加一个全视频的 ## Video direction 块。

不要更改故事、脚本、资源选择、asset_candidates、transition_in 或捕获的源材料。不要在此步骤写入 HTML。

在视觉设计锁定后暂存命名资源:

node <SKILL_DIR>/scripts/stage-assets.mjs --storyboard ./STORYBOARD.md --hyperframes .

关卡: 每个视觉帧都有一个带时间编码的镜头序列,其揭示节奏与画外音匹配(无前载);## Video direction 存在;assets/ 包含命名资源。


步骤 5:构建帧

目标:将每个故事板帧构建为 HTML 组合,并组装可播放的视频。

如果音频已启动,请等待步骤 3.1 完成。然后同步时长并获取 SFX;如果无声,则跳过两者。

node <SKILL_DIR>/scripts/audio.mjs sync-durations --audio-meta ./audio_meta.json --storyboard ./STORYBOARD.md

node <SKILL_DIR>/scripts/audio.mjs fetch-sfx --storyboard ./STORYBOARD.md --hyperframes .

时长同步是机械性的:真实语音持续时间获胜;静音帧保持估计值;切勿手动编辑同步后的时长。

在分派之前,阅读 sub-agents/frame-worker.md 和 ../hyperframes-core/references/subagent-dispatch.md。为每个帧分派一个子代理,尽可能并行;否则以批次运行工作者。每个工作者恰好处理一个帧。

每个工作者的上下文必须包括 PROJECT_DIR、frame_id、画布大小、字幕状态以及如果启用字幕则包括安全区域,以及 RULES_DIR 作为此技能 ../hyperframes-animation/rules/ 的绝对路径。每个工作者读取 frame.md、来自 STORYBOARD.md 的自己的 ## Frame N 块、每个引用运动的本地规则配方(../hyperframes-animation/rules/<id>.md)以及帧的蓝图模板(../hyperframes-animation/blueprints/<id>.md)。每个工作者只写入 compositions/frames/NN-*.html。工作者绝不能编辑 STORYBOARD.md。

当每个工作者返回时,协调者在 STORYBOARD.md 中将该帧标记为 animated。

在音频时间存在后,在后台构建字幕并组装索引:

node <SKILL_DIR>/scripts/captions.mjs build --storyboard ./STORYBOARD.md --audio-meta ./audio_meta.json --hyperframes . --out ./caption_groups.json &

node <SKILL_DIR>/scripts/assemble-index.mjs --storyboard ./STORYBOARD.md --hyperframes .

captions.mjs 使用项目的 .hyperframes/caption-skin.html(在步骤 2 中复制)作为字幕外观,从 frame.md 注入品牌令牌;如果没有皮肤,则呈现内置的默认药丸形状。captions: skipped (<reason>) 是有效的。当明确跳过时,继续操作而不带字幕。

关卡: 每个帧都标记为 animated,index.html 存在,并且字幕已构建或明确跳过。


步骤 6:最终定稿

目标:验证组装的视频,获得用户批准,并渲染最终的 MP4。

注入转场、运行检查、暂停供审查,然后渲染。

node <SKILL_DIR>/scripts/transitions.mjs inject --storyboard ./STORYBOARD.md --hyperframes .

node <SKILL_DIR>/scripts/transitions.mjs verify --storyboard ./STORYBOARD.md --index ./index.html

npx hyperframes lint

npx hyperframes validate

npx hyperframes inspect

npx hyperframes snapshot --at <frame-midpoints>

snapshot 将捕获的帧拼接成一个联系表(snapshots/contact-sheet.jpg)。浏览一下;如果没有明显问题,继续操作——不要在此停留。

如果命令失败,显示 stderr 并停止——不要堆叠恢复命令。自行修复:对 compositions/frames/NN-*.html 进行最安全的最小编辑,然后重新运行失败的检查。

检查通过后,暂停供用户审查。视频已组装完成,可在 Studio 中查看和编辑。仅在步骤 3 和步骤 6 之间管理一次预览:如果用户之前要求,则打开;如果他们之前拒绝,则提供;如果用户已经在 Studio 中审查,则不要再次询问。

预览:npx hyperframes preview

渲染

……

[为翻译截断]

Individual skills in this repo

This repo contains 13 individual skills — each has its own dedicated page.

1345AbhishekKumar/starter-nextjs

Add captions to a talking-head video. ONE catalog (CATALOG.md) of 32 visual identities behind two engines: column-flow (captions composited INTO the scene — matte occlusion + mix-blend; cream/ink/editorial/keynote/documentary/loud/neon/glitch/chrome/velocity) and themed constitutions (anchor/ordnance/terminal/neonsign/stardust/stomp/scoreboard/transit/vhs/arcade/dossier/laser/thunder/hologram/biolume/aurora/spectrum/papercut/popup/chalkboard/graffiti/brush/inkwater/ransom/lastpage/nightcity — e.g. a glyph-decode climax, a neon sign WRITTEN stroke by stroke, or the quiet `anchor` rail default). Route by identity, never by mode. Trigger on "captions/subtitles", "embed/cinematic captions", "VFX captions", "炸/特效/酷炫字幕", a named identity, or top-tier motion-graphics asks. Embedding every word is wrong for most talking-head content — `anchor` is the verbatim default. Pipeline: transcription → hyperframes remove-background matting → HTML render → ffmpeg overlay. Requires hyperframes and a single-subject clip.

1345AbhishekKumar/starter-nextjs

The fallback workflow for authoring custom HyperFrames video compositions at any length or format — longer or multi-scene pieces, brand / sizzle reels, montages, title cards, static loops, and freeform compositions. Input- and length-agnostic. If a specialized workflow clearly fits the input — a marketed product, a website, a topic explainer, a GitHub PR, existing footage, a short motion graphic, or a Remotion port — prefer it (see /hyperframes); use this only as the general fallback when none fit.

1345AbhishekKumar/starter-nextjs

All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). HyperFrames-native: single paused timeline, seek-safe, deterministic.

1345AbhishekKumar/starter-nextjs

HyperFrames CLI dev loop. Use when running npx hyperframes init, add, catalog, capture, lint, validate, inspect, layout, snapshot, preview, play, render, publish, lambda, doctor, browser, info, upgrade, skills, compositions, docs, benchmark, telemetry, transcribe, tts, or remove-background, or when troubleshooting the HyperFrames build/render environment. Entry point for AWS Lambda cloud rendering (`hyperframes lambda deploy / render / progress / destroy / policies`).

1345AbhishekKumar/starter-nextjs

The HyperFrames composition contract — build one renderable project. Use for composition structure, the `data-*` timing attributes, `class="clip"`, tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Read before writing composition HTML.

1345AbhishekKumar/starter-nextjs

Non-animation creative direction for HyperFrames videos. Use for design spec (frame.md / design.md) handling, palettes, typography, narration, beat planning, audio-reactive visuals, composition patterns, and brand / style decisions. For atomic motion patterns and scene blueprints, use `hyperframes-animation`.

1345AbhishekKumar/starter-nextjs

Audio and media assets for HyperFrames compositions, produced by one shared audio engine (`scripts/audio.mjs`) — multi-provider TTS (HeyGen / ElevenLabs / Kokoro local), background music + sound effects (HeyGen audio-library retrieval by default, with local Lyria / MusicGen BGM generation and a bundled SFX library as the no-credential fallback), Whisper transcription, background removal, and caption authoring. Use for voiceover / TTS, BGM, SFX / sound effects, transcription, captions / subtitles / lyrics / karaoke / per-word styling, voice + provider selection, and music-mood prompting.

1345AbhishekKumar/starter-nextjs

Install and wire registry blocks and components into HyperFrames compositions. Use when running hyperframes add, installing a block or component, wiring an installed item into index.html, or working with hyperframes.json. Covers the add command, install locations, block sub-composition wiring, component snippet merging, registry discovery, and authoring a new block or component to contribute upstream (idea → scaffold → validate → PR).

1345AbhishekKumar/starter-nextjs

Use when the user wants a short, design-led motion graphic where motion is the message: kinetic typography, stat or number count-up, chart/data-viz hit, logo sting, brand lockup, lower-third, callout, social overlay, animated headline/tweet/news item, motion poster, or quick captured-page highlight. Usually under 10s and up to ~30s, with no narration arc, voice-over, or live-action subject. Can render to MP4 or transparent overlay. Not for longer, multi-scene, narrated, or brand-reel pieces (use general-video), narrated website videos (website-to-video), topic explainers (faceless-explainer), product promos (product-launch-video), PR videos (pr-to-video), or captions on existing footage (embedded-captions). When unsure whether it's a quick motion-first piece or a longer / narrated treatment, see /hyperframes.

1345AbhishekKumar/starter-nextjs

Use when the user has a music track (an audio file, or a video to pull audio from) and wants a beat-synced HyperFrames video, calm to hard-hitting. The music drives everything: one analyzer reads it once, the orchestrator lays out the frames and fills a per-frame plan, and one sub-agent builds each frame. Typography and templates are the floor — a complete video needs zero assets — but any images or videos the user supplies are cut into the frames on the same beat grid (beat-cut / ken-burns). The genre (lyric video, slideshow, kinetic promo) falls out of the per-frame choices; the pipeline never branches on it.

1345AbhishekKumar/starter-nextjs

turn a GitHub pull request (a PR URL like github.com/<owner>/<repo>/pull/<N>, an <owner>/<repo>#<N> ref, or 'this PR' in a checked-out repo) into a code-change explainer video, up to ~3 min (sweet spot 30-90s) — changelog, feature reveal, fix, or refactor walkthrough, rendered from the diff / commits / files. The input is a CODE CHANGE read via the gh CLI; there is no website capture. Use this skill for a GitHub PR. Do not use it for a product launch/promo (use /product-launch-video), a tour of a real website (use /website-to-video), a topic explainer with no PR (use /faceless-explainer), captions on existing footage (use /embedded-captions), or a short unnarrated motion graphic (use /motion-graphics). If the intent is unclear, route through /hyperframes first.

1345AbhishekKumar/starter-nextjs

Port an existing Remotion (React) composition to HyperFrames HTML. Use ONLY when the user explicitly asks to port/convert/migrate/translate a Remotion source. Do NOT use: (a) authoring a new HyperFrames composition; (b) Remotion mentioned in passing; (c) Remotion code shared as reference only; (d) "same video as my Remotion one" without explicit migrate request — treat as fresh build. Doubt → `/general-video`. One-way, Remotion-only: no reverse export (HyperFrames→Remotion or any framework), no non-Remotion source (After Effects, Framer Motion, plain React/CSS) → out of scope, re-create via `/general-video`. Flags unsupported patterns (useState, useEffect, async calculateMetadata, third-party React libs, `@remotion/lambda`) and recommends runtime interop over lossy translation. Unsure whether to port vs. build fresh, or only a passing Remotion mention? → /hyperframes.

1345AbhishekKumar/starter-nextjs

Capture a general website/URL and turn it into a HyperFrames video (site tour, showcase, or social clip from the site's own visuals). Uses headless Chrome screenshots + brand assets. Use when intent is general — portfolio/blog/landing-page showcase or social clip from the site. NOT for: product/SaaS launch or promo (→ /product-launch-video, even from a URL); topic explainer with no site (→ /faceless-explainer); GitHub PR (→ /pr-to-video); adding captions to existing video (→ /embedded-captions); short unnarrated page-highlight motion graphic (→ /motion-graphics). Unclear launch-vs-general-site? Ask one question or start at /hyperframes.

相关技能