Communitygithub.com

AlessandroFare/fluxychat

当没有专门工作流适用,或 BRIEF.md 设置 'flow: companion' 时,创作或编辑自定义 HyperFrames 合成作品。适用于较长或多场景片段、品牌和宣传短片、蒙太奇、静态循环、静态标题卡、素材混剪以及自由形态构建。如需短篇无旁白的动效优先单元(含动画标题),请改用 motion-graphics。在使用此技能之前,请通过 hyperframes 路由新作品。

fluxychat 是什么?

Fluxychat 是一个通用视频创作技能,专为 HyperFrames 框架设计,当没有更专业的工作流可用或 'flow: companion' 模式被激活时作为备选。它自动处理媒体和 Figma 适配器,在开始创作前确保正确认证和资产导入。该技能会读取项目状态(BRIEF.md、现有项目文件或全新项目)并相应地引导工作流。它强制执行严格的依赖顺序——先规划、再审查(如启用故事板)、解决依赖、构建场景,最后渲染——并为 `flow: companion` 提供详细的导演式指导,鼓励高质量、有概念驱动的成果,而非单纯的工具性操作。技能支持多场景装配、动画、媒体处理,并通过能力菜单提供渐进式功能发现,确保在最小化人工干预的同时保持创作的完整性。

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

在你喜欢的 AI 中提问

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

文档

通用视频

在依赖此工作流之前,请运行:

npx hyperframes skills update general-video

如果成功且无操作,说明技能是最新的。如果更新失败,请显示错误,不要从内存继续。

1. 应用跨领域源适配器

  • 媒体: 对于任何音频、图像、图标、标志、语音、调色、LUT、处理/效果、字幕或媒体操作需求,请加载 /media-use 并按照 ../media-use/references/resolve.md(解析、采用、复用)和 ../media-use/references/setup-providers.md(提供商、认证)操作。对于模糊的素材反馈和命名风格,请在编辑前使用 ../media-use/references/media-treatments.md;不要使用 CSS/SVG/不透明度即兴创作支持的媒体效果。在首次认证的提供商操作之前,请运行 npx hyperframes auth status 并逐字输出其内容。如果已注销,请应用 ../hyperframes-core/references/brief-contract.md 中的门控:协作模式等待登录或明确的离线选择;自主模式则报告状态并通过可用的离线提供商继续。当没有离线提供商能够满足所需能力时,显示阻塞提示。仅本地采用不需要认证门控。
  • Figma: 如果任何输入是 figma.com 的 URL,请先运行 /figma。从导出的资产、令牌、组件或故事板帧构建。不要使用原始的 Figma 连接器调用,因为它们会跳过 SVG 清理、媒体来源和品牌令牌绑定。

这些适配器不会更改由 /hyperframes 选择的工作流。

2. 从项目状态开始

应用第一个匹配的行,不要评估更低的状态行:

状态操作
特定编辑进行编辑,保留现有项目决策,然后重新运行受影响的检查。不要重新开始探索。
BRIEF.md 存在读取它。如果 workflow 命名了另一个工作流且 flow 不是 companion,则移交。不要询问简报问题。
没有简报,但 hyperframes.json 或 STORYBOARD.md 存在从文件和记录的首选项恢复。仅从已知事实回填 BRIEF.md。
全新创作运行 /hyperframes 及其意图层。仅在 workflow: general-video 或 flow: companion 时返回此处。

对于新项目,从简报中选择一个 kebab-case 的目录名,并在编写简报前创建项目结构:

npx hyperframes init "videos/<project>" --non-interactive --example=blank --skill=general-video

然后在项目根目录下编写 BRIEF.md,使用 ../hyperframes-core/references/brief-format.md。在现有项目中,根目录是包含 hyperframes.json 的目录。仅记录由简报格式命名的、经确认且基于首选项的字段,使用 node <MEDIA_DIR>/scripts/prefs.mjs record --hyperframes <PROJECT_ROOT>;永远不要记录推断的默认值。此处 <MEDIA_DIR> 是已安装的 /media-use 技能目录,<PROJECT_ROOT> 是包含 hyperframes.json 的目录。如果意图层采用了某个配方,现在使用 node <MEDIA_DIR>/scripts/recipe.mjs use --hyperframes <PROJECT_ROOT> --name <name> 应用它,并且不要再次询问。

3. 解释运行形态

仅使用 ../hyperframes-core/references/brief-contract.md 中的规范术语:

字段含义效果
flow谁驱动automation:选择并执行路线。companion:在对话中共同创作。
storyboard故事板是否是审查界面yes:运行计划和草图审查。no:无需故事板直接构建。
派生的 mode检查点门控如何运作遵循简报契约。永远不要要求用户命名模式。

不要为这些状态发明同义词。持续出现的“直接构建”信号由意图层处理,并作为 flow: automation、storyboard: no 到达。

  • 对于 flow: automation,选择路线并在第一个进度更新中用一行说明。
  • 对于特定编辑,进行编辑而不要发明新路线。

协作流程

当 flow: companion 时:

  • 读取 BRIEF.md,并将已接受的 ## 资产 和 ## 自定义设置 与项目工件进行核对。完成仍待处理的接受工作;已完成的工作保持不变;不要再次将已接受的能力当作新能力提供。
  • 以导演而非承包商的身份出现。 选择协作的用户选择了参与和质量;诚实的回应是你能够设计的最佳版本,而不是你能辩护的最小版本。第一个计划是顶层处理方案:叙事弧(借用最近的类型视角——菜单 § 类型视角)、设计规范、每个场景的运动处理名称(第 5 节的规划规范)、转场、音频标识——音乐和声音标记,或刻意的静音——用户素材的放置,以及设计好的开场和结尾。用一句话说明每一层增加了什么;标记出昂贵的部分(渲染时间、登录、计费)。用户是在裁剪一个处理方案;他们不应该逐个批准地拼凑一个处理方案。
  • 天花板属于概念,而非工具箱。 每一层都必须服务于简报的信息——一个会以相同方式装扮任何视频的处理方案只是装饰。工艺上升到天花板;内容永远不会超过被请求的范围(第 6 节)。
  • 在检查点之间,../hyperframes/references/capability-menu.md 有两种工作方式。作为触发器列表:当用户提到其输入或构建达到其需求时,提供相关的能力。作为每次迭代的升级渠道:计划、草图或构建检查点可能会附带一两个指向用户正在查看的素材的追踪提议(“场景 3 的 stat 想要计数处理”)。在提供之前阅读它;永远不要倾倒完整的目录。
  • 在用户接受某个能力后,立即生成其工件并将决策记录到匹配的 BRIEF.md 主体部分。仅当用户明确更改时,才重写前端字段并记录确认的首选项。
  • 保持相同的故事板、验证、最终预览和渲染批准门控。协作改变的是谁在引导,而不是质量要求什么。

4. 在每一阶段前加载所需知识

当条件匹配时,这些读取是强制性的:

条件在行动前读取
任何合成 HTML 或场景布局/hyperframes-core;使用 references/determinism-rules.md 了解其布局契约
任何非平凡的创作或视觉处理/hyperframes-creative → references/house-style.md 和 references/video-composition.md
任何动态、动画或场景转场/hyperframes-animation;按照其路由到匹配的规则、适配器、蓝图或转场参考
storyboard: yes../hyperframes-core/references/storyboard-format.md 和 ../hyperframes-core/references/review-loop.md
任何媒体资产或操作,包括旁白、背景音乐、音效、字幕、调色或变换/media-use;对于框架播放和放置,还请阅读 /hyperframes-core → references/variables-and-media.md
多场景装配../hyperframes-core/references/production-loop.md
flow: companion,在第一个计划之前/hyperframes-creative → references/story-spine.md 和 references/house-style.md;最近的类型视角和完整的 ../hyperframes/references/capability-menu.md——顶层处理方案是根据这些设计的,而非回忆
一个协作能力提供、捕获、节奏网格、生成视频、地图、发布或跨工作流能力../hyperframes/references/capability-menu.md
设计规范存在,在最终批准之前/hyperframes-creative → references/design-adherence.md

不要用回忆代替这些读取。仅在匹配的参考实际被加载时,渐进式信息公开才节省上下文。

5. 执行合成

使用此依赖顺序。仅当某阶段的输入缺失时才跳过它。

  1. 规划。 说明观众弧、结构、节奏和时长驱动因素。对于短的单一场景使用一个文件;对于三个或更多硬场景切换或任何重复使用的场景,使用子合成。阅读 /hyperframes-creative → references/story-spine.md 了解有旁白的弧,references/beat-direction.md 了解节奏,以及 /hyperframes-core → references/composition-patterns.md 了解结构。对于开放式多场景简报,通过 /hyperframes-creative → references/prompt-expansion.md 扩展提示。一个多场景规划引用每个场景的形态:当有适用的蓝图时,来自 /hyperframes-animation → blueprints-index.md 的蓝图 ID,或者当没有时,它组成的命名规则来自 rules-index.md——运动名称来自这些索引,从不发明。故事的真相决定了哪些场景存在;引用为它们装扮。一个多场景规划也被记录为分派工件:每场景一个 ## Frame N 块在 STORYBOARD.md 中——status: outline,声明的 src:,蓝图/规则引用,以及节拍文本——即使 storyboard: no 也是如此。该块是分派单元;故事板仅是审查界面。

  2. 在请求时审查规划。 对于 storyboard: yes,在这些块上运行共享的审查循环。对于 storyboard: no,继续而不打开故事板。当计划暂停无论如何发生时,将子代理委派授权(步骤 4 的分派所需)折叠进该暂停中,而不是稍后再次停止。

  3. 解决依赖。 在并行工作前安装注册表块。暂存用户资产,采用现有媒体,仅解决简报所需的依赖。当其时间线驱动时长时,尽早开始音频。

  4. 构建场景。 对于短的单一场景片段,在其最可见的时刻实现场景(确认的线框(如果存在)就是该结束状态,不得重绘),然后根据引用的蓝图或规则进行动画制作——在编写动画之前阅读完整的配方主体(/hyperframes-animation → blueprints/<id>.md、rules/<id>.md)。

    分派仅在规模化时才物有所值。 编写数据包和预热新的工作器上下文会花费实际的时间和令牌:一部最多约 6 个短场景的电影在此上下文中一个接一个地 INLINE 构建更快(测量:5 个短场景 ≈ 9 分钟内联对比 ≈ 21 分钟打包)。仅在计划超过该范围时——更多场景,或单个重场景——才进行分派,然后给予每个工作器 2–3 个场景,而非一个,并在 一次波次 中生成 所有工作器(第二次波次几乎使时间窗口加倍)。分派时:

    node <SKILL_DIR>/scripts/frame-packets.mjs --project "$PROJECT_DIR" --storyboard "$PROJECT_DIR/STORYBOARD.md"

    构建器在 .hyperframes/frame-packets/ 下为每个场景写入一个有限的数据包(场景的确切故事板块 + 蓝图主体 + 引用的每个规则配方,内联)和 _role.md(../hyperframes-core/references/frame-worker-...

…[为翻译截断]

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

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

相关技能