Communitygithub.com

1345AbhishekKumar/starter-supabase

用於製作簡短、以設計為主、無旁白的動態圖形,時間約10秒內,適合動態字體、數字計數、圖表動畫、標誌揭示等。

starter-supabase 是什麼?

這個技能(skill)專門用來生成「簡短、以設計為主、無旁白」的動態圖形影片,長度通常在10秒以內,最長約30秒。它適合處理動態字體(kinetic typography)、數字計數(stat count-up)、圖表/數據視覺化動畫、標誌揭示(logo sting)、品牌鎖定(brand lockup)、下方三分之一標題(lower-third)、社交媒體疊加、動態標題/推文/新聞項目、動態海報或快速捕捉的頁面亮點等。輸出格式可以是標準的 MP4 或透明背景的 WebM/MOV 疊加層。 此技能不適用於有旁白敘事、多場景、品牌宣傳片、網站解說、產品宣傳、公關影片或為現有影片添加字幕的場合(這些應使用其他對應的技能,如 `/general-video`、`/website-to-video` 等)。如果無法確定是否屬於動畫優先還是旁白優先的專案,建議先參考 `/hyperframes`。 此技能基於「資源優先(asset-first)」的工作流程:先決定資源策略並取得實際素材,再圍繞現有資源設計鏡頭,最後透過重複使用目錄中的功能來進行組合。它支援 macOS Apple Silicon 和 Linux x64 系統,並使用 `hyperframes` 命令列工具進行初始化和渲染。整個流程分為初始化、計劃、素材獲取(可選)、設計、構建、渲染和驗證等階段。

相容平台~Claude Code~Codex CLI✓Cursor✓Gemini CLI
npx skills add https://github.com/1345AbhishekKumar/starter-supabase/tree/HEAD/.agents/skills/motion-graphics

在你喜歡的 AI 中提問

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

說明文件

motion-graphics — 派遣入口

在步驟 0 之前確認路線。 此技能製作 簡短、以設計為主、無旁白的動態圖形(動態即訊息;約 10 秒內,無畫外音)。較長、多場景或有旁白的處理 → /general-video;網站的旁白影片 → /website-to-video;主題解說 → /faceless-explainer;產品宣傳 → /product-launch-video;為現有影片添加字幕 → /embedded-captions。超出範圍:即時/渲染時數據,或無法捕捉的鏡頭。不確定是動畫優先還是旁白優先?請先閱讀 /hyperframes。

一個簡短、以設計為主的動態圖形。資源優先:先決定資源策略並取得真實素材,_然後_設計鏡頭,再圍繞你所擁有的進行設計,最後透過重複使用目錄功能來組合。所有成品置於 PROJECT_DIR = videos/<project-name>/(在步驟 0 建立);以下所有路徑皆相對於此。

階段執行方式主要成品詳細流程
initBashhyperframes.json步驟 0
plan子代理 — 決定是否搜尋? + 分類 + 資源策略shot-plan.json(草案:類別、asset_needs 查詢、簡述)agents/director.md (第 1 部分)
source ◇Bash — 媒體使用解析 (若 asset_needs 為空則跳過)assets/ + assets/index.mdphases/source/guide.md
design子代理 — 圍繞已解析的資源進行鏡頭設計shot-plan.json(最終版:區塊 + 佈局 + 動態 + 位置)agents/director.md (第 2 部分)
build子代理 — 重複使用優先的組合compositions/index.htmlagents/builder.md
renderBash — hyperframes render (MP4,或使用 --format webm/mov 製作疊加層)renders/video.mp4步驟 5
verifyBash — lint / inspect -> 失敗時呼叫修復子代理(就地修復)agents/finalize.md

◇ source 僅在選擇的類別宣告有資源需求時執行。純代碼/文字類別(例如 kinetic-type、大部分 charts/stat)的 asset_needs: [],會直接從計劃跳到設計。

類別 — 根據搜尋決定進行劃分

plan 的第一個決定是:這是否需要搜尋? 這個分支將類別分成兩組;然後選擇具體類別 — 對於搜尋驅動的類別,取決於搜尋傳回的內容類型。每個類別是一個 categories/<id>/module.md(其規劃 + 建置規則);共享的動態詞彙位於 references/motion-vocabulary.md(→ hyperframes-animation 規則/藍圖 + 註冊區塊)。

形式類別 — 無需搜尋;使用者提供內容:

類別意圖依賴於
kinetic-type有力的一行 / 引言 / 標題,動態優先文字caption-* 區塊 + 動畫規則
stat單一主數字 / 計數器 + 環圈圖apple-money-count / rules/{counting-dynamic-scale, stat-bars-and-fills}
charts來自數據的長條圖 / 折線圖 / 圓餅圖 / 競賽圖 / 百分比data-chart 區塊
logo-reveal標誌閃現 / 品牌鎖定(使用者標誌)logo-outro / rules/svg-path-draw
lower-thirds姓名 / 標題條、呼叫框、社交媒體疊加層caption-* + 註冊區塊的疊加層

搜尋驅動的類別 — 先搜尋,再按內容類型製作動畫(RWA 路徑):

傳回的內容類別動畫
網頁 / 連結webpage網頁 / UI 動畫(滾動、揭示、游標、呼叫框)
新聞文章news標題揭示 + 來源卡片 + 關鍵事實呼叫框
推文tweet動畫推文卡片
圖片 / 實體asset-fusion資源的幾何形狀 變成 圖表(RWA 敘事融合)

建置順序:一次一個,以覆蓋率優先(粗糙即可)。kinetic-type 從原型移植;其餘類別依此類推。

先決條件

macOS Apple Silicon 或 Linux x64。系統工具:brew install node ffmpeg。執行一次 npx hyperframes doctor。macOS GPU 渲染:export PRODUCER_BROWSER_GPU_MODE=hardware。

可選金鑰(若未設定則使用本地備用)— 僅供那些透過媒體使用(media-use)來獲取/生成資源的類別需要:

金鑰用途備用方案
GEMINI_API_KEY / GOOGLE_API_KEY圖片生成(媒體使用解析)跳過生成 / 僅搜尋
(asset_scout / 搜尋提供者)webpage/news/tweet + asset-fusion 真實資源搜尋類別降級為無資源狀態

流程

步驟 0 — 初始化

當前工作目錄是代理工作區根目錄;將所有成品寫入 PROJECT_DIR = videos/<project-name>/。<project-name>:使用使用者提供的目錄名稱,否則根據意圖取一個簡短的 kebab-case 名稱(<subject>-motion)。不要使用工作區基本名稱或時間戳。

僅當 $PROJECT_DIR/hyperframes.json 不存在時:

PROJECT_DIR="${MOTION_GRAPHICS_DIR:-videos/<project-name>}"
mkdir -p "$(dirname "$PROJECT_DIR")"
npx hyperframes init "$PROJECT_DIR" --non-interactive --example=blank

init 會檢查已安裝的技能與 GitHub 上的最新版本,如果任何技能過時,則會更新全域技能集。

限制: 切勿在工作區根目錄執行 hyperframes init;切勿在 PROJECT_DIR 內嵌套另一個 hyperframes/;每個 Bash 命令(主代理 + 子代理)都是 (cd "$PROJECT_DIR" && ...) 子 shell — 絕不使用裸 cd。

步驟 1 — 計劃(子代理:導演第 1 部分)

派遣一個子代理。提示 = 完整的 agents/director.md + ## Dispatch context(SKILL_DIR / PROJECT_DIR / 使用者的請求 / Schema: <SKILL_DIR>/references/shot-plan-ir.md)。它必須:

  1. 決定:這是否需要搜尋?(第一個分支)
    • 否 → 選擇一個形式類別(kinetic-type / stat / charts / logo-reveal / lower-thirds);內容由使用者提供;asset_needs: []。
    • 是 → 將一個搜尋計劃輸出到 asset_needs[](新聞 / 網頁 / 推文 / 圖片;兩極查詢)。具體的搜尋驅動類別(webpage / news / tweet / asset-fusion)將由步驟 2 傳回的內容類型確認,並在步驟 3 最終確定。
  2. 寫入一份草稿 shot-plan.json(信封 + 選定的形式類別 或 搜尋意圖 + asset_needs + 一段鏡頭簡述)。結構:references/shot-plan-ir.md。

驗證:[ -s "$PROJECT_DIR/shot-plan.json" ] && echo ok || echo missing。

步驟 2 — 獲取來源 ◇(Bash: media-use,條件性)

如果 shot-plan.json.asset_needs 不為空,則解析資源(搜尋 / 生成 / 獲取 → 凍結的專案本機路徑 + 分類帳)。詳見 phases/source/guide.md(包裝 media-use resolve;搜尋驅動的類別使用新聞/網頁/推文/圖片搜尋)。如果 asset_needs 為空,則跳到步驟 3。

# 說明性 — 詳見 phases/source/guide.md
(cd "$PROJECT_DIR" && node <SKILL_DIR>/phases/source/resolve.mjs --plan ./shot-plan.json --out ./assets)

優雅降級:如果搜尋/提供者不可用,類別會退回到無資源狀態(在 context.log 中註明)。

步驟 3 — 設計(子代理:導演第 2 部分)

派遣一個子代理(提示 = agents/director.md 第 2 部分 + 派遣上下文,包括已解析的 assets/index.md(如果步驟 2 已執行)+ catalog-map.md)。它圍繞可用資源設計鏡頭:選取目錄區塊 + hyperframes-animation 規則/藍圖、佈局、動態、節拍,以及(對於 asset-fusion)element_positions + 滴管調色盤。最終確定 shot-plan.json(content.block + content.customize + 每個類別的內容)。

步驟 4 — 建置(子代理:建置者,重複使用優先)

派遣一個子代理。提示 = 完整的 agents/builder.md + 派遣上下文(shot-plan.json、catalog-map.md、該類別的 module.md、references/motion-vocabulary.md、references/builder-contract.md)。重複使用優先:npx hyperframes add <block> + 就地客製化;僅手動編寫缺口部分 + asset-fusion 輔助功能。輸出 compositions/index.html,符合 HF 合約(暫停的 GSAP 時間軸在 window.__timelines 上、class="clip" + 穩定的 ID、tl.seek(0)、確定性)。

步驟 5 — 渲染(Bash)

(cd "$PROJECT_DIR" && npx hyperframes render . --skill=motion-graphics -q draft -o ./renders/video.mp4)
# 透明背景疊加層變體:--format webm (或 mov)

步驟 6 — 驗證(Bash → 失敗時呼叫修復子代理)

(cd "$PROJECT_DIR" && npx hyperframes lint . && npx hyperframes inspect .)

exit 0 → 完成。發生 lint/inspect 錯誤時,派遣修復子代理(agents/finalize.md:快照 QA + 一次就地修復處理 + 重新渲染)。絕不在修復過程中更改固定的持續時間。

報告 + 可選預覽

報告最終輸出(renders/video.mp4,或 .webm / .mov 疊加層變體)+ 持續時間。在運行期間不要打開預覽。 僅在要求時提供,並在渲染後啟動,以便提供最終檔案:

(cd "$PROJECT_DIR" && npx hyperframes preview)   # Studio UI;或 `npx hyperframes play` 以獲取可分享的連結

標誌存在於 hyperframes-cli 技能中(references/preview-render.md)。

恢復表

狀態從此處繼續
無 shot-plan.json步驟 1 (計劃)
shot-plan.json 有 asset_needs,無 assets/步驟 2 (獲取來源)
shot-plan.json 最終版,無 compositions/index.html步驟 3/4 (設計+建置)
compositions/index.html 存在,無 renders/video.mp4步驟 5 (渲染) + 步驟 6
renders/video.mp4 存在報告 + 停止

設計說明(維護者 — 執行時不讀取此內容)

  • 資源優先理由: 資源獲取提前進行,並為鏡頭設計提供資訊(RWA 流程:分析 → 搜尋 → 審查 → 組合)。搜尋驅動的類別(webpage/news/tweet)和 asset-fusion 都依賴於媒體使用搜尋(新聞/網頁/推文/圖片),這是媒體使用有記錄的 RWA 譜系。
  • 重複使用優先: 生態系統中類似於 LLM 生成模板的方法是「組合目錄區塊 + hyperframes-animation 規則」。HF 的暫停 GSAP 時間軸 ≙ Remotion 的 useCurrentFrame。
  • 類別模組合約: 一個 categories/<id>/module.md(規劃 + 建置),共享 references/motion-vocabulary.md(+ 可選評估)。增加一個類別 = 放入資料夾 + 在 agents/director.md 註冊其分類器行 + 在 catalog-map.md 註冊其行;階段流程保持不變。
  • 目錄結構:
    videos/<project-name>/
      hyperframes.json  context.log
      shot-plan.json            # 中間表示 (導演輸出)
      assets/  assets/index.md  # 媒體使用輸出 (如果已獲取)
      compositions/index.html   # 建置者輸出
      renders/video.mp4
    
  • 註冊: 在 hyperframes 路由器中 — 新增「以設計為主的簡短動態圖形」意圖 + 工作流程描述;從 /general-video 中劃出 motion-graphics 觸發條件;新增反向「請勿使用」邊緣。詳見 motion-graphics-genre.md §5-7。

Individual skills in this repo

This repo contains 13 individual skills — each has its own dedicated page.

1345AbhishekKumar/starter-supabase

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.

1345AbhishekKumar/starter-supabase

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.

1345AbhishekKumar/starter-supabase

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.

1345AbhishekKumar/starter-supabase

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

1345AbhishekKumar/starter-supabase

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. Read before writing composition HTML.

1345AbhishekKumar/starter-supabase

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

1345AbhishekKumar/starter-supabase

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.

1345AbhishekKumar/starter-supabase

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

1345AbhishekKumar/starter-supabase

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.

1345AbhishekKumar/starter-supabase

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.

1345AbhishekKumar/starter-supabase

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 /website-to-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.

1345AbhishekKumar/starter-supabase

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.

1345AbhishekKumar/starter-supabase

Capture a general website/URL and turn it into a HyperFrames video (site tour, showcase, or social clip from the site's own visuals). Uses headless Chrome screenshots + brand assets. Use when intent is general — portfolio/blog/landing-page showcase or social clip from the site. NOT for: product/SaaS launch or promo (→ /product-launch-video, even from a URL); topic explainer with no site (→ /faceless-explainer); GitHub PR (→ /pr-to-video); adding captions to existing video (→ /embedded-captions); short unnarrated page-highlight motion graphic (→ /motion-graphics). Unclear launch-vs-general-site? Ask one question or start at /hyperframes.

相關技能