Communitygithub.com

AlessandroFare/fluxychat

當無專門工作流程適用,或 BRIEF.md 設定 flow: companion 時,用於創作或編輯自訂 HyperFrames 作品。適用於較長或多場景作品、品牌短片、集錦、蒙太奇、靜態循環、靜態標題卡、影片混音以及自由形式建構。對於短暫無旁白且以動作為主的單元(包含動態標題),請改用 motion-graphics。在使用此技能前,請先透過 hyperframes 進行全新創作。

fluxychat 是什麼?

此技能作為 HyperFrames 生態系統中的通用影片製作工作流程,專為處理無專門工作流程(如 motion-graphics 或特定類別)的專案而設計。它提供了一個結構化的流程,從專案初始化、素材適配(包含來自 Figma 的媒體和設計資產)到最終渲染,確保以可重現且經過審查的方式處理影片資產。此工作流程支援兩種主要操作模式:自動化模式(流程驅動)和協作模式(companion flow)。前者由 AI 獨立選擇並執行最佳路線,後者則讓 AI 扮演「導演」角色,與用戶共同創作,先提出最佳方案再讓用戶調整,而非逐步徵求批准。關鍵環節包括:強制性知識查閱(確保正確使用 HyperFrames Core、Creative 和 Animation 參考文檔)、基於依賴順序的場景建構(包含內聯建構與分派式建構的選擇),以及嚴格的媒體處理規範(要求透過 /media-use 處理所有媒體操作,而非臨時使用 CSS/SVG)。此技能也強制執行來源追蹤與偏好記錄,確保專案可重現且決策有據可查,最終產出結構化的 STORYBOARD.md 與 BRIEF.md 檔案,為後續生成最終影片提供完整藍圖。

相容平台~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 網址,請先執行 /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

然後,在專案根目錄下使用 ../hyperframes-core/references/brief-format.md 撰寫 BRIEF.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 並將已接受的 ## Assets 和 ## Customizations 與專案成品進行比對。完成仍待處理的已接受工作;跳過已完成的工作;請勿將已接受的能力再次當作新功能提供。
  • 以導演而非承包商的角色到來。 選擇參與和品質的使用者,值得得到的是你能設計出的最佳版本,而非最小版本。第一個計劃是天花板級處理:故事弧線(借用最近的類型鏡頭——選單 § 類型鏡頭)、設計規格、每個場景的動作處理名稱(§ 5 的計劃規範)、轉場、音訊身份——音樂和聲音標記,或特意選擇的寂靜——使用者素材的放置,以及精心設計的開場和結尾。用一句話說明每個層次增加了什麼;標記出昂貴的部分(渲染時間、登入、計費)。使用者應是向下修剪一個處理方案,而非逐步拼湊一個。
  • 天花板屬於概念,而非工具箱。 每個層次都必須服務於簡報的訊息——一個對任何影片都一視同仁的處理只是裝飾。工藝走向天花板;內容絕不應超出要求範圍(§ 6)。
  • 在檢查點之間,../hyperframes/references/capability-menu.md 有兩種運作方式。作為觸發清單:當使用者提及某個能力的輸入或建構進展到需要該能力時,提供相關能力。作為每次執行的升級通道:計劃、草稿或建構檢查點可以攜帶一兩個指向使用者正在查看的素材的追蹤提議(「場景 3 的統計數據想要計數處理」)。在提供之前先閱讀它;切勿傾瀉完整目錄。
  • 使用者接受某項能力後,立即產生其成品,並將決策記錄到對應的 BRIEF.md 主體區段中。僅當使用者明確變更時,才重寫 frontmatter 欄位並記錄已確認的偏好。
  • 保持相同的分鏡板、驗證、最終預覽和渲染核准閘門。協作模式改變的是誰來掌舵,而非質量要求。

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 的具名規則——動作名稱來自這些索引,絕非發明。故事的真實性決定了哪些場景存在;引用為它們穿上外衣。多場景計劃也會記錄為任務分派成品:在 STORYBOARD.md 中,每個場景一個 ## Frame N 區塊——status: outline、宣告的 src:、藍圖/規則引用以及節拍文字——即使當 storyboard: no 時也是如此。該區塊是任務分派單位;分鏡板僅是審查表面。

  2. 在要求時審查計劃。 對於 storyboard: yes,在這些區塊上執行共享的審查循環。對於 storyboard: no,在不開啟分鏡板的情況下繼續。無論如何,當計劃暫停發生時,將子代理委派授權(codex 在步驟 4 的任務分派時需要)摺疊到該暫停中,而不是稍後再次停止。

  3. 解析依賴關係。 在並行工作前安裝註冊區塊。暫存使用者資產,採用現有媒體,僅解析簡報要求的內容。當音訊的時間線驅動持續時間時,請提前開始處理音訊。

  4. 建構場景。 對於簡短的單一場景作品,在加入動作前,在其最顯著的時刻實作場景(當存在已確認的線框時,該線框即為最終狀態,不得重繪),然後根據其引用的藍圖或規則進行動畫製作——在撰寫動作前讀取完整的配方主體(/hyperframes-animation → blueprints/<id>.md、rules/<id>.md)。

    任務分派僅在大規模時才有價值。 編寫封包和啟動新的工作者上下文會消耗真實的分鐘數和令牌:一個最多約 6 個短場景的影片,在此上下文中內聯建構會更快,一個場景接一個場景(經測量:5 個短場景約 9 分鐘內聯 vs 約 21 分鐘封包化)。僅當計劃超出此範圍時才進行分派——更多場景,或個別較重的場景——然後分配給每個工作者 2–3 個場景,而非一個,並在單一波次中生成所有工作者(第二波次幾乎會使時間窗加倍)。當進行分派時:

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

    建構器會在 .hyperframes/frame-packets/ 下為每個場景寫入一個有界限的封包(場景的 exact storyboard block + the blueprint body + every cited rule recipe, inlined)和 _role.md(../hyperframes-core/references/frame-worker-role.md)。

    …

[其餘內容已截斷]

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.

相關技能