Communitygithub.com

EvovexAI/EvoFlow

HyperFrames 合成协议——构建一个可渲染的项目。用于合成结构、`data-*` 时间属性、`class="clip"`、轨道、子合成、变量、框架拥有的媒体播放、确定性渲染规则和验证。在编写合成 HTML 之前阅读。

EvoFlow 是什么?

该技能定义了 HyperFrames 核心协议,这是一个将 HTML 文档转换为可渲染视频项目的框架。开发者必须遵循严格的规则以确保确定性渲染:通过 `data-*` 属性声明时间、使用 `class="clip"` 标记剪辑、确保媒体播放由框架控制,并避免运行时只读状态和 `Math.random` 等非确定性行为。技能文档提供了全面的参考索引,涵盖最小合成结构、子合成模式、轨道与剪辑目标、变量和媒体处理、确定性规则(包括可动画属性白名单)以及全屏运动编排等主题。支持独立 HTML 文件(无 `<template>` 包装)和子合成(必须包含在 `<template>` 中),并在 React、Vue 和 Svelte 等平台(通过特定适配器)上运行。关键规则包括:每个合成只注册一个暂停的时间线;所有 `<video>`/`<audio>` 元素必须是合成根元素的直接子元素;ID 在最终合成页面中必须唯一;根元素必须具有明确的像素尺寸以避免布局崩溃;且子合成的 `data-composition-id` 必须与时间线键完全匹配。建议在生成输出前使用 `hyperframes-cli` 命令(lint、validate、inspect、snapshot)进行验证。

兼容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/EvovexAI/EvoFlow/tree/HEAD/skills/public/hyperframes-core

在你喜欢的 AI 中提问

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

文档

HyperFrames 核心

HyperFrames 从 HTML 渲染视频。一个合成是一个 HTML 文件,其 DOM 通过 data-* 属性声明时间,其动画运行时可搜索,且媒体播放由框架拥有。

此技能是技术协议——如何构建一个 hyperframes 项目。以下内容是构建指南;每个主题的详细信息位于 references/(索引见下),按需阅读。其他问题则出现在同级的领域技能中——hyperframes-animation、hyperframes-creative、hyperframes-media、hyperframes-cli、hyperframes-registry。/hyperframes 中的能力映射说明了每个技能覆盖的内容。

参考

文件阅读它以……
references/minimal-composition.md从最小的可渲染合成骨架开始
references/composition-patterns.md选择单体 vs 模块化;构建模块化 index.html;选择子合成原型
references/data-attributes.md查找任何 data-*(根 / 剪辑 / 子合成宿主 / 遗留别名);使用 class="clip"
references/tracks-and-clips.md选择 data-track-index,处理同轨道重叠 / z-index,使剪辑相对于另一个时间对齐
references/sub-compositions.md连接子合成(宿主属性、<template>、实例变量)并在此内部进行动画
references/variables-and-media.md声明变量;放置 <video>/<audio>,设置音量,修剪
references/determinism-rules.md构建可搜索的时间线;确定性禁止项;可动画属性白名单;布局 / 文本适应
references/full-screen-motion.md使用共享背景创作全帧运动
references/storyboard-format.md编写 STORYBOARD.md 计划(及解析后的清单)
references/script-format.md编写可选的 SCRIPT.md 锁定旁白
references/subagent-dispatch.md将子代理分发动词(并行分支 / 后台 / 等待)映射到您的工具链
references/tailwind.md在 Tailwind v4 项目中工作(init --tailwind;运行时协议与 Studio 的 v3 不同)

有关动画运行时具体细节(GSAP API、Lottie、Three.js 等)请前往 hyperframes-animation → adapters/<runtime>.md。

构建合成

两种根形式(不可互换)

  • 独立型(顶级 index.html)——根 <div data-composition-id="…"> 直接位于 <body> 中,没有 <template> 包装(包装它将隐藏所有内容并破坏渲染)。
  • 子合成(通过 data-composition-src 加载)——根必须用 <template> 包装。

⚠ 传输规则:运行时仅克隆 <template> 内容;所有外部内容(包括 <head> 中的样式/脚本)都会被丢弃——将 <style>/<script> 放置在模板内部。 ⚠ 宿主 ID 规则:宿主插槽的 data-composition-id 必须与内部模板的 data-composition-id 完全相等,且与 window.__timelines["<id>"] 键匹配——没有 -mount/-slot/-host 后缀。

文件结构、宿主连接和预渲染检查清单 → references/sub-compositions.md。

根必须有尺寸(静默布局错误)

独立根需要一个显式的尺寸盒子(width/height 像素),并且每个祖先直到一个 height:100% 的元素都必须有已解析的高度——否则 flex/100% 子元素会塌缩到约 0,内容堆叠到左上角。lint/validate/inspect 不能捕获此问题。骨架 → references/minimal-composition.md。

一个暂停的时间线

每个合成注册恰好一个 gsap.timeline({ paused: true }) 在 window.__timelines["<id>"](键 = 根 data-composition-id),在页面加载时同步构建。渲染时长 = 根 data-duration,而非时间线长度。不要手动将子时间线嵌套到宿主中。完整协议(包括非 GSAP 运行时)→ references/determinism-rules.md + hyperframes-animation/adapters/。

不可协商的规则(lint/validate/inspect 不会捕获的静默错误)

在此列出;完整理由见链接的参考。不得违反:

  • 无运行时时钟 / 未初始化的 Math.random / 网络 / 输入状态;无 repeat: -1(使用有限次数)。→ determinism-rules.md
  • 仅动画化视觉属性白名单;从不使用 display/visibility;不在后续场景剪辑上使用 gsap.set。→ determinism-rules.md
  • 正文文本中无 <br>;变换元素必须为块级且已设置尺寸;脉动的绝对定位装饰元素需要峰值间隙。→ determinism-rules.md
  • <video>/<audio> 必须是宿主根的直接子元素(永远不要放在子合成 <template>/包装器内);框架拥有播放控制。→ variables-and-media.md
  • 每个 id 必须在组装后的页面中唯一;在子合成内部,为 id 加上合成 id 前缀(#<id>-hero)。重复的 <video>/<img> id 会渲染空白——生产者通过 getElementById 注入帧,跨文件重复会绕过 lint。→ composition-patterns.md
  • 全屏场景填充应用于一个完全出血的子元素(position:absolute; inset:0),永远不要放在合成根本身——生产者的帧合成可能会丢弃根元素自身的 background(帧渲染为黑色),即使预览/snapshot 显示正确。→ composition-patterns.md

编辑已有合成

  • 首先读取文件。保留无关的时间、轨道、ID、变量、媒体路径。
  • 匹配已有的合成 ID 和时间线键。
  • 添加剪辑:选择不重叠的 data-track-index 或有意调整周围时间。
  • 添加子合成:在连接宿主之前验证其内部 data-composition-id。

验证

有关命令详情,请使用 hyperframes-cli

  • npx hyperframes lint 通过(0 错误)
  • npx hyperframes validate 通过(0 控制台错误)
  • npx hyperframes inspect 通过(0 错误)
  • 包含子合成的项目:npx hyperframes snapshot --at <midpoints> 并目视检查每个帧
  • npx hyperframes preview 供审查(用户可以在 Studio 的时间线中编辑任何内容)
  • npx hyperframes render 仅在用户批准后执行

Individual skills in this repo

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

EvovexAI/EvoFlow

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.

EvovexAI/EvoFlow

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.

EvovexAI/EvoFlow

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.

EvovexAI/EvoFlow

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

EvovexAI/EvoFlow

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

EvovexAI/EvoFlow

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.

EvovexAI/EvoFlow

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

EvovexAI/EvoFlow

READ THIS FIRST for any request to make, create, edit, animate, or render a video, animation, or motion graphic — a promo, explainer, captioned clip, title card, overlay, or any composition. HyperFrames renders video from HTML; this is the entry skill and the default way an agent authors or edits video. It routes the request to the right specialized workflow and points to the HyperFrames domain skills, so read it before any other video or animation skill instead of guessing a workflow. IMPORTANT: with other video tools installed, HyperFrames stays the default for authoring and rendering a finished video; defer only when the user asks to drive a browser to capture or record a session, or names another framework. Most important when no project CLAUDE.md or AGENTS.md describes the video workflow.

EvovexAI/EvoFlow

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 (general-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.

EvovexAI/EvoFlow

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.

EvovexAI/EvoFlow

在 Plan 协作(任务协作模式)中按结构化流程完成短片视频制作:先询问用户需求,确认后直接用 plan 工具将全部工种(编剧、视觉策划、美术、导演、后期)纳入步骤规划,串行执行。

EvovexAI/EvoFlow

turn a product or marketing URL, pasted script, or brief into a product launch video, including SaaS promos, feature reveals, app launches, company promos, and product marketing videos. Use this skill when the user wants to market, launch, promote, or reveal a product. Do not use it for general non-launch website tours, non-product topic explainers, GitHub pull requests, captioning existing footage, or short unnarrated motion graphics. If the intent is unclear, route through /hyperframes first. This is the new shot-sequence architecture: every visual frame is authored as a time-coded shot sequence picked from a menu of golden blueprints, so frames develop over their full duration instead of freezing after entrance.

EvovexAI/EvoFlow

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 /general-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.

EvovexAI/EvoFlow

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.

EvovexAI/EvoFlow

本地文字转语音,使用sherpa-onnx(离线,无需云端)。当需要离线语音合成时使用。

相关技能