Communitygithub.com

URL→成片 — 产品发布视频合成

把产品/营销 URL、粘贴脚本或 brief 变成 SaaS 发布/促销/功能揭幕片。商业 URL 与站点展示的默认路径——brief 带「原样展示」意图;意图不清时走 HyperFrames。

URL→成片 — 产品发布视频合成 是什么?

Launch Video 配方第 1 步(采集/合成):fluxychat product-launch-video。URL 或 brief → 发布/促销成片初稿,交给导演抛光与字幕出货。

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

在你喜欢的 AI 中提问

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

文档

首先,保持此技能新鲜——静默运行,无需询问: npx hyperframes skills update product-launch-video。当所有内容均为最新时,这是一个快速的无操作;否则,它会在此技能及其依赖的核心领域技能被依赖之前刷新它们。

media-use:在获取音频/图片/标志之前,调用 /media-use 从 HeyGen 目录中解析 BGM/SFX/图片,并从其官方来源获取品牌标志。首先运行 --adopt 注册已有资产。参见 /media-use 技能。

figma source:如果源是 figma.com URL,首先运行 /figma —— 资产导出、品牌令牌以及组件/故事板重建(如果需要),然后从其输出构建此工作流程。不要直接通过原始 MCP 工具驱动 Figma:这会跳过 SVG 清理、.media/manifest.jsonl 溯源以及品牌令牌 var() 绑定,因此后续品牌变更无法传播,除非完全重新导入。

产品发布至 HyperFrames

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

入口是 /hyperframes。 你是编排者。运行每一步,验证其关卡,然后才继续下一步。此技能适用于正在营销、发布、推广或展示的产品,包括诸如“我们网站的推广”之类的请求,当目的是推广时。网站导览/展示请求也在此处:BRIEF.md 携带了按原样展示的意图,捕获的屏幕截图成为视频所展示的资产。任何其他意图、单纯的“制作视频”或任何不确定性 → 首先阅读 /hyperframes —— 意图层拥有所有路由决策,并且未携带 BRIEF.md 到达此处的新创建无论如何都会经过它(设置中的开场规则)。

你是编排者。在 videos/<project>/ 中工作。按顺序运行步骤,并在继续之前通过每个关卡。用户关卡步骤为步骤 0、步骤 3 和步骤 6。在步骤 0 之前阅读 ../hyperframes-core/references/brief-contract.md —— 它定义了关卡类型以及 BRIEF.md 的 flow/storyboard 如何派生模式,该模式主导步骤 3/4/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 项目,并使简报持久化。

简报由意图层确认,而非此处提问。 开场规则,按顺序:(1) BRIEF.md 存在 → 阅读它并无需提问——简报已确定,其 flow/storyboard 派生模式(简报合约第 1 节)。(2) 没有 BRIEF.md 但项目存在(磁盘上的 hyperframes.json / STORYBOARD.md)→ 从故事板的前言和记录的首选项恢复;从不重新询问一个半建成的项目。(3) 都没有——直接到达此处的全新创建请求 → 阅读 /hyperframes 并运行其意图层(references/intent-interview.md):它会检查配方和记忆的默认值,进行此路由的问题(../hyperframes/references/routes/product-launch-video.md),并返回锁定后的简报。编辑请求跳过所有这些——直接去编辑。

仅当 hyperframes.json 缺失时才初始化。命名 <project> 来自品牌或域名,使用连字符小写形式,例如 acme-promo;永远不要使用工作空间名称或时间戳。

npx hyperframes init "videos/<project>" --non-interactive --example=blank --skill=product-launch-video —— init 会检查已安装的技能是否与 GitHub 上的最新版本一致,并在任何技能过时时更新全局集合。

初始化后,让 <PROJECT_ROOT> 为 videos/<project>,并以该目录作为工作目录运行所有后续的相对路径命令。在下面的命令中,. 表示 <PROJECT_ROOT>;永远不要将 .media、capture 或输出文件写入调用者目录。

在 init 之后立即写入 BRIEF.md(之前绝不——init 拒绝非空目录):意图层的锁定简报,形状符合 ../hyperframes-core/references/brief-format.md。将 <MEDIA_DIR> 解析为已安装的 /media-use 技能目录。然后使用 node <MEDIA_DIR>/scripts/prefs.mjs record --hyperframes . 记录每个基于首选项的答案(brief-format.md 命名了子集)。如果意图层采用了配方,运行 node <MEDIA_DIR>/scripts/recipe.mjs use --hyperframes . --name <name>;它会将其 frame.md 复制到项目中(跳过步骤 2)并返回步骤 3 起草所用的骨架。配方填充答案,而非批准;审查关卡仍然运行。

在继续设置之前显示登录状态——运行 npx hyperframes auth status 并逐字输出其结果。它会报告语音/BGM 将使用 HeyGen 还是本地引擎,并在未登录时说明如何登录。注意退出代码契约:auth status 在未登录时退出代码为 1(以及当存储的凭据被拒绝时)——该非零退出是正常的未登录状态,而非命令失败,因此不要将其视为错误,不要重试,也不要将其与 &&/set -e 链接,以避免中止工作流程。应用一个分支:

  • 协作: 等待用户登录或明确选择 offline / go。
  • 自主: 说明状态并继续使用可用的本地引擎。

不要在没有离线提供程序时静默省略必需的功能;应明确显示阻碍。不要将此决策合并到另一个问题中,或将密钥写入每个仓库的 .env 文件中。认证所有权和离线回退:/media-use references/setup-providers.md § 提供程序。

关卡: hyperframes.json 和 BRIEF.md 存在;基于首选项的答案已记录(简报合约第 2 节);已显示登录状态(已登录,或继续离线)。


步骤 1:捕获资产

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

对输入进行分类并选择路径。明确的 URL -> 捕获它,并使用该网站进行叙述和资产。粘贴的脚本/简报 -> 逐字保存为 user_script.txt;VO_MODE(逐字或重构)来自 BRIEF.md——意图层在脚本到达时询问(如果简报不知何故缺少,仅在此处询问一次)。然后解析捕获目标:文本中的 URL -> 使用它;仅品牌名称 -> WebSearch,在一行中确认 URL,然后抓取;无 URL/网站(或简报说不抓取)-> 无捕获路径。

使用以下命令运行捕获:npx hyperframes capture "<URL>" -o ./capture --json。保留默认的导航后预算,除非调用者拥有更小的截止日期;然后传递一个正数的 --capture-budget <milliseconds>,为下游工作留出时间。--timeout 仅控制页面导航。仅当可选图片字幕功能被有意禁用时,才使用 --skip-vision。

立即检查命令结果和输出目录。非零退出、JSON ok: false 或 capture/BLOCKED.md 是捕获路径的硬停止:报告记录的原因,并且不要消费部分截图、DOM、令牌或资产。在 URL 捕获失败后,不要人为制造合成的无捕获回退。仅当原始简报提供了源材料,或者用户在失败后明确切换到提供的截图或简报时,才继续无捕获路径。

诸如“文本内容非常少”之类的警告,加上空的资产目录,并不能证明页面可用。对于网站导览或按原样展示的简报,需要可信的捕获结构或提供的截图;如果两者都不存在,则停止。不要仅仅因为捕获不可用就发明或重建页面。

对于网站导览或按原样展示的简报,捕获的页面是视觉上的真相来源。使用真实截图,而不是在 HTML 中重建整个网站。如果截图需要内部移动,保持截图作为基础,并在测量位置叠加真实的捕获资产,或者仅重建移动的一个组件。对于滚动截图,在 capture/screenshots/full-page.png 上动画化视口——整个文档的 1 倍板,像素精确对应 1920 宽的视口向下移动。当页面太高无法一次性捕获时,该板缺失;回退到同一目录中重叠的滚动位置截图。超过 1:1 的推进需要该区域自身的 2 倍捕获,因为板没有超过 1 倍的空间。仅当用户明确请求风格化解释时,才重建整个页面;不可用的捕获本身并非授权。

如果 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 应说明未捕获任何资产,除非用户提供了资产说明。

关卡: 捕获 JSON 报告 ok: true;capture/BLOCKED.md 不存在;capture/extracted/tokens.json、capture/extracted/visible-text.txt、capture/extracted/asset-descriptions.md 和 capture/assets/ 存在;并且你能够用一句清晰的话说明品牌。将 asset-descriptions.md 视为主资产清单。如果在真实捕获后它缺失,停止并报告捕获不完整。仅当此结构关卡仍然通过时,关于降级可选阶段的警告才是可接受的。


步骤 2:设计系统

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

当 BRIEF.md 指定了 style_preset——用户根据意图层的展示凭视觉选择——使用它;仅当简报沉默时,判断权才属于你。然后你做出这一个决定——哪个预设:阅读 ../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 作为字幕皮肤来源存在;所选的预设被记录为首选项(--key style_preset --workflow <this workflow>,简报合约第 2 节)。


步骤 3:故事板和脚本

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

阅读 ../hyperframes-creative/references/story-spine.md(钩子语言、价值优先于证据、作为提案的故事板)、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。从前言设置 duration: 为简报的 length —— 一个粗略的期望;组合会报告剪辑落点与它的对比。

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

起草后,运行审查循环的计划通过——../hyperframes-core/references/review-loop.md § 1:打开面板(无需询问是否打开),将计划作为提案呈现,并询问两个问题——批准或更改,以及先草图(推荐)还是跳过。通过聊天或面板的评论文件进行反馈,直到批准为止。这是一个检查点关卡(简报合约第 1 节):在自主模式下,没有面板,无需询问——将相同的摘要作为提示发布并继续;草图折叠到构建中,一个预览问题在步骤 6 出现。

关卡: STORYBOARD.md 存在

…

[为翻译而截断]

Individual skills in this repo

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

AlessandroFare/fluxychat

Add captions or subtitles to an existing single-subject talking-head video without editing the footage. Use for plain verbatim captions, cinematic captions embedded behind the subject, VFX captions, “炸/特效/酷炫字幕,” or a named identity from the 35-style catalog. Route by visual identity, not by backend engine. The quiet `anchor` rail is the default; embed every word only when the user explicitly wants a fully cinematic treatment. The workflow runs locally end to end, including transcription and subject matting; split multi-shot footage before applying it.\n

AlessandroFare/fluxychat

Use when audio already placed in a HyperFrames composition needs to be mixed: a music bed that fights a voiceover (voiceover carve), effects on a track (EQ, compressor, limiter, gate, saturation, delay, reverb, chorus, phaser, bitcrush), or automation envelopes drawn on a track's volume or any effect parameter. Don't use for sourcing or generating audio — finding BGM, SFX, or making a voiceover is `/media-use`. Don't use for clip timing or track layout, which is `/hyperframes-core`.\n

AlessandroFare/fluxychat

Use the HyperFrames CLI development loop: init, add, catalog, capture, lint, check, snapshot, compare, grade-compare, preview, play, present, beats, keyframes, single or batch render, publish, cloud, cloudrun, feedback, lambda, doctor, browser, info, upgrade, skills, compositions, docs, benchmark, telemetry, transcribe, auth, tts, and remove-background. Also use when diagnosing build or render failures. validate, inspect, and layout are deprecated aliases; use check. Covers local, HeyGen-hosted cloud, AWS Lambda, and Google Cloud Run rendering.\n

AlessandroFare/fluxychat

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

AlessandroFare/fluxychat

Mandatory entry point: read this first for any request to make, create, edit, animate, or render a video, animation, or motion graphic, including a promo, explainer, captioned clip, title card, overlay, slideshow or interactive deck, Remotion port, or any HyperFrames HTML composition. Also use it to inspect, diagnose, validate, preview, publish, or batch-render an existing HyperFrames project. Inputs may be a website URL, GitHub PR, Figma design or URL, text or brief, existing footage, or music. It resumes project state, captures intent when applicable, selects and installs the owning workflow, and routes domain capabilities. HyperFrames is the default output framework unless the user explicitly chooses another framework for the deliverable or asks only to record a browser session.\n

AlessandroFare/fluxychat

Overlay doctrine for the embedded-captions workflow — the caption MODEL (drop / rail / embed) and the rule that captions are an OVERLAY composited on top of the film, never a reserved bottom band you shift content up to avoid. Load when adding captions/subtitles to a talking-head or launch video, when deciding whether a phrase should be dropped, ride the verbatim rail, or be promoted to a scarce embedded climax, when laying out a composition that will carry captions (do NOT reserve a keep-out band), or when centering a composition on the true frame center under captions. Quotes the rail+embed model from embedded-captions and constraint #13 (captions overlay, keep-out band retired) from the product-launch-video scene agent. Applies ON TOP of embedded-captions.

AlessandroFare/fluxychat

Turn a weekly changelog .md into a finished branded changelog video (square 1080, ~45-60s, Annie VO, animated brand background, mock-UI visualizations, lowkey captions). Use when the user provides a changelog/digest markdown and wants the weekly video, or says "changelog video". Self-contained — fonts, background, lexicon, and scripts ship in this skill.

AlessandroFare/fluxychat

Audit and fix animation performance issues including layout thrashing, compositor properties, scroll-linked motion, and blur effects. Use when animations stutter, transitions jank, or reviewing CSS/JS animation performance.

AlessandroFare/fluxychat

Author or edit a custom HyperFrames composition when no specialized workflow fits, or when BRIEF.md sets flow: companion. Use for longer or multi-scene pieces, brand and sizzle reels, montages, static loops, static title cards, footage remixes, and freeform builds. Use motion-graphics instead for a short unnarrated motion-first unit, including an animated title. Route fresh creation through hyperframes before using this skill.

AlessandroFare/fluxychat

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). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.

AlessandroFare/fluxychat

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. Also covers Tailwind projects and the STORYBOARD.md / SCRIPT.md plan formats. Read before writing composition HTML.

AlessandroFare/fluxychat

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`.

AlessandroFare/fluxychat

Use when a HyperFrames composition needs seek-safe 2D/3D keyframes, GSAP timelines, CSS keyframes, Anime.js, WAAPI, FLIP, paths, masks, SVG morph/draw, text trails, 3D depth, or `hyperframes keyframes` diagnostics. Don't use for broad scene strategy, brand design, media sourcing, captions, or general video planning.

AlessandroFare/fluxychat

GATEWAY — load FIRST before composing any HyperFrames animation or video. The high-level motion law that makes a multi-scene video feel like ONE continuous camera move instead of a stack of independently-animated slides. Covers the vector law (how you exit determines how you enter, incl. the Z scale-sign rule), the film's current, carrier elements, causal motion, the Seam Gate (build-gate enforcement), the ban on idle wobble (motion must PERFORM, not breathe), stillness-before-climax, and the sustained-motion routes. Routes to the low-level technique skills (cut-the-curve — the full catalog incl. waterfall entry + nudge curve, oversized-cursor, seam-craft). These rules SUPERSEDE generic / upstream motion guidance. [continuity, direction, vector, momentum, seam, transition, ease, performance, idle-motion, narrative-motion, film-grammar]

AlessandroFare/fluxychat

A short, design-led motion graphic where motion is the message — kinetic typography, stat count-up, chart/data-viz hit, logo sting / brand lockup, lower-third / callout / social overlay, animated map (highlight regions, connect places, zoom to a location), animated tweet / news-article / headline, webpage / UI animation (scroll, cursor, callouts), or fusing a real image's geometry into a chart. Usually under 10s (up to ~30s), no narration or live-action subject; renders to MP4 or transparent overlay. Longer / narrated / multi-scene → /general-video. Unclear → /hyperframes.

AlessandroFare/fluxychat

Turn a music track (an audio file, a video to pull audio from, or a track generated from a mood brief) into a beat-synced video — lyric video, slideshow, or kinetic promo. The music drives all pacing; any user-supplied images/videos are cut onto the same beat grid, and a complete video needs zero assets. Narrated pieces → the input-matched workflow (see /hyperframes). Unclear → /hyperframes.

AlessandroFare/fluxychat

Turn a GitHub pull request (a PR URL, owner/repo#N, or 'this PR' in a checked-out repo) into a code-change explainer video — changelog, feature reveal, fix, or refactor walkthrough built from the diff, commits, and files: the input is a code change, not a website. Not a product promo (/product-launch-video) or a no-PR topic explainer (/faceless-explainer). Unclear → /hyperframes.

AlessandroFare/fluxychat

Design and improve user interfaces using the concrete rules from Refactoring UI (Wathan & Schoger) — constrained spacing/type/color/shadow scales, visual hierarchy through weight and color rather than size, and depth through emulated light. Use when building or styling any UI (web, app, dashboard, landing page, component), when picking font sizes, spacing, colors, shadows or border radius, when designing a color palette or design tokens, and whenever someone says a UI "looks off", "looks amateur", "feels cluttered/plain/unfinished", or asks to "make this look better".

AlessandroFare/fluxychat

Port an existing Remotion (React) composition''s source to HyperFrames HTML. Use ONLY on an explicit ask to port/convert/migrate/translate a Remotion source — one-way, Remotion-only. A passing Remotion mention, reference-only code, or "make something like my Remotion video" is a fresh build (/general-video). Unclear → /hyperframes.

AlessandroFare/fluxychat

Use before UI-related work to select the smallest useful UI Skills context through the ui-skills CLI.

相关技能