Communitygithub.com

AlessandroFare/fluxychat

GATEWAY — 在组合任何 HyperFrames 动画或视频之前,请先加载此技能。这是一种高级运动法则,能让多场景视频感觉像连续摄像机移动,而非独立动画幻灯片的堆叠。涵盖矢量法则(如何退出决定如何进入,包括 Z 轴缩放符号规则)、影片电流、载体元素、因果运动、接缝门(构建-门控执行)、禁止空闲晃动(运动必须“表演”,而非“呼吸”)、高潮前的静止以及持续运动路径。通向低级技术技能(cut-the-curve — 完整目录,包括瀑布式进入 + 微调曲线、超大光标、接缝工艺)。这些规则取代通用/上游运动指导。

fluxychat 是什么?

此技能“Motion Doctrine (Gateway)”是 HyperFrames 动画工作流的核心法则和决策网关。它定义了如何将多个独立场景无缝连接成一个连贯、富有叙事感的单一摄像机运动,而非简单的幻灯片切换。开发者在创作任何具体动画之前,必须首先应用此技能,通过编写矢量账本(ledger.json)来规划每个场景接缝的退出和进入方向、速度和相位。技能提供了强制性的接缝门检查脚本来验证这些规则,并完全禁止了无意义的空闲晃动(如呼吸、浮动),确保每一帧的运动都有叙事目的。该技能适用于所有 HyperFrames 项目,并提供了通往具体实现技术(如 cut-the-curve 和 oversized-cursor)的路线图,其规则优先级高于任何通用的运动指导。

兼容平台~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
产品发布/讲解器/字幕工作在上游技能之上叠加 text-beat-economics, brand-faithful, captions-overlay

创作顺序:矢量账本(ledger.json)→ 从中STAMP主接缝(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)以数字方式强制执行,每个接缝:账本行一致性、退出时仍在移动、进入时在飞行中(绝不由静止开始)、测量方向 = 账本方向、进入/退出速度匹配(WARN)、零重叠(每帧仅一侧可见——剪辑不是溶解)、Z符号规则(两侧的 d(scale)/dt 符号相同;扫描进入场景自身的入场以查找符号冲突)、以及包含祖先缩放的载体矩形连续性。在编写账本时,使用 seam-gate.mjs probe --t <cut> 查找每个接缝的真正的载体选择器。

脚本无法检查的规则——仍然由你负责:

  1. 编辑会重新打开接缝。 对场景首尾约1秒的任何更改(包括根据新的配音重新计时)都会使该边界的审计失效——重新运行验证器。
  2. 音频是时钟。 根据配音的真实时间戳重新计时场景;永远不要为了适应插槽而匆忙朗读。重新生成配音会重新打开其接缝。
  3. 剪辑门控陷阱(零重叠FAIL的常见原因):如果剪辑的 data-start 在其进入补间之前,则剪辑会在其初始不透明度处取消隐藏——设置初始 autoAlpha: 0 和 data-start = 剪辑时间,绝不能更早。

第二部分 — 表演(场景持续表演)

无空闲晃动

禁止将空闲正弦循环(呼吸、浮动、漂移、发光脉冲)作为持续运动——它们会让人感觉“视频在等待”。如果场景进入后还剩下几秒,那是计划错误:增加故事,而不是晃动。进入和退出之间的每个阶段都由以下一条路径拥有(在计划中命名路径):

路径它是什么
分阶段揭示保留内容;在叙述节拍上揭示——画面不断获得信息(默认适用于≥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.

相关技能