Communitygithub.com

EvovexAI/EvoFlow

HyperFrames 合成合約 — 構建一個可渲染的專案。用於組合結構、`data-*` 時間屬性、`class="clip"`、軌道、子合成、變數、框架擁有的媒體播放、確定性渲染規則與驗證。在撰寫合成 HTML 前請先閱讀。

EvoFlow 是什麼?

此技能定義了 HyperFrames 的核心技術合約,用於指導如何構建一個可渲染的影片合成專案。HyperFrames 能將 HTML 文件渲染為影片,透過 DOM 元素上的 `data-*` 屬性來宣告時間軸,並讓動畫運行時可隨意定位(seeking),媒體播放則由框架全權控制。該技能詳細說明了兩種根表單(獨立與子合成)的規則、根元素必須明確設定尺寸以避免佈局錯誤、每個合成只能註冊一個暫停時間軸、以及一系列非協商性的確定性規則(如禁止運行時時鐘、未種子隨機數、無限重複等)。此外,它也涵蓋了從最小合成骨架、組合模式、數據屬性查詢到軌道與片段處理、子合成接線、變數與媒體管理、確定性渲染規則,以及完整畫面動畫和多種非 GSAP 動畫運行時適配器(如 Lottie、Three.js)的詳細參考文件。開發者需遵循這些規範來確保合成結果的可預測性與正確性。

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

在你喜歡的 AI 中提問

開啟一個已預先載入此 Agent Skill 的新對話。

說明文件

HyperFrames Core

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 以 px 為單位),並且每個直到 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(离线,无需云端)。当需要离线语音合成时使用。

相關技能