Communitygithub.com

AlessandroFare/fluxychat

GATEWAY — 在組合任何 HyperFrames 動畫或影片前,優先載入。這條高階運動法則能讓多場景影片感覺像連續的單一鏡頭移動,而非一堆獨立動畫幻燈片的堆疊。涵蓋向量法則(如何退出決定了如何進入,包括 Z 軸縮放符號規則)、影片流、載體元素、因果運動、縫隙關卡(建置與強制執行)、禁止空轉晃動(運動必須「執行」而非「呼吸」)、高潮前的靜止,以及持續運動路線。並連結至低階技術技能(cut-the-curve — 完整目錄,含瀑布式進入 + 微調曲線、超大光標、縫隙工藝)。這些規則取代通用的/上游的運動指導。

fluxychat 是什麼?

Motion Doctrine (Gateway) 是一套為 HyperFrames 動畫和影片創作設計的高階運動法則。它解決了獨立創作場景時,視覺動量會在每個剪輯點中斷,以及場景在原地晃動的常見問題。此技能定義了核心的「縫隙法則」,包括向量法則(確保場景間退出與進入的軸向、方向和速度一致)、影片的「流向」(預設為左向,其他方向則用於特定敘事含義)、「載體」元素(讓視線跟隨具體物件穿越剪輯點)以及「因果運動」(鏈接每個動作,使其由前一個動作觸發)。它還引入了「縫隙關卡」的概念,這是一個可執行的構建關卡,通過數值化方式檢查縫隙的一致性、運動速度和方向匹配等。此外,技能詳細說明了場景內持續運動的路線(如階段性揭示、帶意圖的鏡頭移動、序列化 UI 生命週期、動畫序列、光標引導操作),禁止「空轉晃動」,並要求在重大動作和其結果之間安排「高潮前的靜止」。最後,它提供了常見的反模式對照表,幫助開發者避免常見的動畫錯誤。

相容平台~Claude Code~Codex CLI✓Cursor
npx skills add https://github.com/AlessandroFare/fluxychat/tree/HEAD/.agents/skills/motion-doctrine

在你喜歡的 AI 中提問

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

說明文件

運動法則(通道)

在組合任何動畫之前請先閱讀此文。它決定了每個縫隙處會發生什麼事,以及每個場景如何表現;技術技能則負責實現它。這些規則取代通用的/上游的運動指導。此舉旨在防止的失敗:獨立創作的場景——眼睛的動量在每個剪輯點處死亡,且場景在進入和退出之間原地晃動。

路線圖

決策(此技能)實現技能
縫隙過渡選擇 + 參數 + 代碼cut-the-curve §1–5(目錄)
文字 / 元素進入級聯cut-the-curve §6(瀑布式進入)
場景內群組重新定位(無剪輯)cut-the-curve §7(微調曲線)
光標引導動作 / 場景啟動 / 變形觸發oversized-cursor
縫隙渲染機制 / 閃白防護seam-craft
產品發佈 / 解說 / 字幕工作在 upstream 技能之上疊加 text-beat-economics、brand-faithful、captions-overlay

創作順序:向量分類帳(ledger.json) → 從分類帳中標記主縫隙(scripts/seam-stamp.mjs --ledger ledger.json --write index.html) → 按階段設定持續運動路線 → 載體和原因 → 構建合成 → 驗證(scripts/seam-gate.mjs)。 僅手動創作 Tier-A 的變形/匹配剪輯;標記過的縫隙預設通過關卡檢查。


第一部分 — 縫隙法則

向量法則

場景 A 如何退出決定了場景 B 如何進入:相同軸向、相同方向、匹配速度、雙方均在運動中途剪輯。

  1. 軸向 — x 保持 x,y 保持 y,Z 保持 Z。絕不跨剪輯交換軸向。
  2. 方向 — 絕不鏡像。在 Z 軸上,方向 = 縮放變化的符號:變大 = 推入(相機向前),變小 = 拉出(相機後退)。一個向後退出的場景由一個從小變大的進入來回應,這是一個鏡像向量——最常見的違規情況,因為從小變大是默認的元素進入方式。
  3. 速度 — 進入初始速度 ≈ 退出最終速度,透過鏡像緩動來實現(退出 power4.in + 進入 power4.out,相同距離和時長;進入方在概念路徑中接管 ≥50% 的進度)。機制詳見 cut-the-curve。
  4. 相位 — 剪輯點落在雙方運動的中途。在剪輯前靜止下來,或在剪輯後從靜止開始,都是一種死節拍。

流向

每個影片選擇一個主導方向(默認:左)。每個普通縫隙都使用它。其他向量是保留的——使用一個意味著某事:

向量含義
流向(左)"下一個節拍" — 中性的前進進度
向上提升 — 結論或揭示高於之前的內容
Z 軸向前(縮放穿越)深入到同一個想法中
Z 軸向後(反向縮放)抵達 — 更大的東西著陸
縮放爆發(向外爆炸)離開一個世界 — 表面衝過攝影機
  • 絕不連續執行相反方向的縫隙——來回擺動會被解讀為錯誤。
  • 方向的改變需要一個可見的原因(點擊 / 彈跳 / 撞擊)或一個章節邊界。

向量分類帳

在創作任何主時間線之前先寫好它——作為專案根目錄下的 ledger.json(結構:references/seam-gate.md)。每個縫隙一行:剪輯時間、退出和進入向量(軸向 + 有符號方向;Z 軸行攜帶縮放符號)、選擇器、技術。退出和進入必須匹配;如果某行不匹配,修正計劃,而非緩動。驗證器在運行時取樣之前,靜態地檢查行的連續性。

載體

眼睛跟隨物體,而非抽象概念。最強的縫隙在剪輯點處以匹配的位置和速度傳遞一個具體的載體:路徑中的光標、收縮/停靠到下一個佈局的容器、飛入精確插槽的標記、瀑布式剪輯的文字組。沒有自然載體時,場景主角承擔此任(部分移動 + 提前淡出,中途進入)。絕不使用交叉淡出——它根本沒有載體。

因果運動

鏈接運動,使每個動作都由上一個動作明顯觸發:點擊 → 擠壓 → 釋放彈簧 → 飛行 → 撞擊 → 反彈 → 揭示。

  • 效果從觸發幀開始——相同的時間線位置,絕不 "稍後再發生"。
  • 反應與隱含質量成比例:大的元素反彈較慢,小的元素反應迅速。
  • 力是改變方向的許可;無因果的翻轉是來回擺動。

縫隙關卡(構建關卡 — 運行驗證器,退出碼為 0 否則縫隙未完成)

node <SKILL_DIR>/scripts/seam-stamp.mjs --ledger ledger.json --write index.html  # 生成
node <SKILL_DIR>/scripts/seam-gate.mjs  verify --ledger ledger.json --project .  # 驗證

此腳本(用法 + 分類帳結構:references/seam-gate.md)針對每個縫隙進行數值強制檢查:分類帳行一致性、退出時仍在移動、進入時處於中途(絕非從靜止開始)、測量方向 = 分類帳方向、進入/退出速度匹配(警告)、零重疊(每幀只有一方可見——剪輯不是溶解)、Z 軸符號規則(d(scale)/dt 在雙方符號相同;掃描進入場景自身的進入點以檢查符號衝突),以及包含祖先縮放的載體矩形連續性。在撰寫分類帳時,使用 seam-gate.mjs probe --t <cut> 來找出每個縫隙真正的載體選擇器。

腳本無法檢查的規則——仍由你負責:

  1. 編輯會重新打開縫隙。 對場景首尾約 1 秒的任何更改(包括因新旁白而重新計時)會使該邊界的審核失效——重新運行驗證器。
  2. 音頻是時鐘。 根據旁白實際的文字時間戳記重新計時場景;絕不為了符合時長而倉促朗讀。重新生成旁白會重新打開其縫隙。
  3. 剪輯蓋層陷阱(導致零重疊失敗的常見原因):一個 data-start 在其進入補間之前的剪輯,會在初始不透明度下取消隱藏——請將初始 autoAlpha: 0 和 data-start 設為剪輯時間,絕不更早。

第二部分 — 表現(場景持續表現)

無空轉晃動

禁止將閒置的正弦循環(呼吸、漂浮、漂移、發光脈衝)用作持續運動——它們傳達的是 "影片在等待"。一個完成進入後還有好幾秒空白場景是規劃的 bug:增加故事,而非晃動。進入和退出之間的每個階段都由以下路線之一掌控(在計劃中命名該路線):

路線說明
階段性揭示保留內容;在敘述節拍中揭示——框架持續獲得資訊(默認適用於 ≥2 個內容組)
帶意圖的鏡頭移動一個映射的縮放+平移路徑:建立廣角 → 移動 → 到達主題
序列化 UI 生命週期產品隨時間行為:進度條前進、高亮步驟、計數器跳動
動畫序列元素演繹一個節拍:卡片歸檔進堆疊、項目被拖動、結果組合
光標引導操作一個超大光標引導眼睛到觸發點;它的點擊點燃下一個節拍(oversized-cursor)

測試:在任何一秒暫停——必須有意義的事情處於運動中途(揭示正在落地、鏡頭正在移動、UI 正在執行旁白所述的操作)。

高潮前的靜止

在主要動作及其結果之間安排 0.3–0.75 秒的暫停——戲劇性的逗號。直接從動作跳至結果的場景會失去此效果。

時間意圖

  • 單一進入 ≤ ~800ms;更長的鋪墊 = 多元素交錯,而非一個慢元素。
  • 退出 ≈ 進入的 75%。例外:cut-the-curve 反轉此比例(進入 ~127% 的退出)。
  • 總交錯 ≤ 500ms;有 8+ 個元素時,縮短每個項目的延遲或僅交錯前幾個。
  • 禁止的緩動:bounce.out / elastic.out。進入時的 back.out(1.4–1.7) 可以。
  • 相似的元素共享一個緩動+持續時間意圖——絕不為每個元素設定獨特的組合。

過渡詞彙

每個影片僅使用 2–3 種場景間過渡並重複使用;默認邊界是在流向方向上的 cut-the-curve。手寫的共享元素變形(intent: morph)不計入預算。


反模式

不要這樣做改這樣做
獨立創作每個場景的進入先寫向量分類帳
在場景之間使用交叉淡出在流向方向上使用 cut-the-curve
退出先完成,然後場景再改變雙方都在運動中途剪輯
剪輯後進入從靜止開始在概念路徑中 ≥50% 處進入
反向縮放退出 → 從小變大進入(或推入 → 超大縮回)匹配縮放速度符號(縫隙關卡規則 7)
在 Z 軸縫隙交接下,進入場景自身的彈出介紹保持其開場幀已合成,或匹配符號
使用空轉晃動 / 呼吸 / 漂浮來填充時間分配一個持續運動路線;或增加故事
無緣無故的方向翻轉使用一個力,或保持流向
將保留向量當作多樣化使用默認使用流向;為了意義而使用保留向量
在原因之後幾幀才反應在同一幀觸發
動作直接跳到結果安排高潮前的靜止(0.3–0.75 秒)

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

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 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 a website route here too — the brief carries the show-it-as-is intent. 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.

相關技能