Communitygithub.com

1345AbhishekKumar/starter-nextjs

建立短版、以設計為主導的動態圖形,強調動態本身即是訊息:動態字體、數字/統計計數、圖表/資料視覺化、品牌標誌、字幕卡、社交媒體覆疊、動態標題/推文/新聞、動態海報或快速頁面精選。通常長度在10秒內,最多約30秒,無旁白弧線、配音或真人主體。可輸出為 MP4 或透明背景覆疊。不適用於較長、多場景、有旁白或品牌影片(請使用 general-video)、有旁白的網站影片(website-to-video)、主題解說(faceless-explainer)、產品宣傳(product-launch-video)、公關影片(pr-to-video)或為既有素材加字幕(embedded-captions)。若不確定是快速動態優先作品還是較長/有旁白作品,請參閱 /hyperframes。

starter-nextjs 是什麼?

此技能專門建立「短版、設計導向、無旁白」的動態圖形,長度通常低於 10 秒(最多約 30 秒),適用範圍涵蓋動態字體、數字計數、圖表動畫、品牌標誌揭示、字幕卡、社交媒體覆疊、新聞標題動畫或快速頁面精選等。它與 general-video、website-to-video、faceless-explainer 等技能嚴格區分,避免用於較長、多場景、有旁白或真人主體的專案。 工作流程分為初始化、規劃、素材來源、設計、建置、渲染與驗證等階段。規劃階段會先判斷是否需要搜尋外部素材:若需要,則透過 media-use 機制處理網頁、新聞、推文或圖片等真實素材,再依內容類型選擇對應的類別(如 webpage、news、tweet、asset-fusion);若不需要,則直接在 kinetic-type、stat、charts、logo-reveal 等表單類別中由使用者提供內容。 設計與建置階段均以「先有素材再設計分鏡」為核心原則,並強化 catalog 區塊的重複使用性,最終以 hyperframes 工具渲染為 MP4 或透明背景的 WebM/MOV 檔案。此外,該技能包含完整的驗證與修復流程,確保輸出品質。

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

在你喜歡的 AI 中提問

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

說明文件

動態圖形 — 派遣入口

請在步驟 0 前確認路線。 此技能用於建立短版、以設計為主導、無旁白的動態圖形(動態即是訊息;約 10 秒內,無配音)。較長、多場景或有旁白的作品 → /general-video;有旁白的網站影片 → /website-to-video;主題解說 → /faceless-explainer;產品宣傳 → /product-launch-video;為既有素材加字幕 → /embedded-captions。超出範圍:即時/渲染時的資料,或無法截取的素材。不確定是動態優先還是有旁白?請先閱讀 /hyperframes。

短版以設計為主導的動態圖形。素材優先:在設計分鏡前先決定素材策略並取得真實素材,然後圍繞已有素材設計分鏡,再透過重複使用 catalog 功能來組成。所有成品放置於 PROJECT_DIR = videos/<project-name>/(在步驟 0 建立);以下所有路徑均為相對路徑。

階段執行方式主要成品詳細流程
initBashhyperframes.json步驟 0
plan子代理 — 決定是否搜尋? + 分類 + 素材策略shot-plan.json(草稿:類別、asset_needs 查詢、簡報)agents/director.md(第一部分)
source ◇Bash — media-use 解析(若 asset_needs 為空則跳過)assets/ + assets/index.mdphases/source/guide.md
design子代理 — 圍繞已解析素材進行分鏡設計shot-plan.json(最終版:區塊+佈局+動態+位置)agents/director.md(第二部分)
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。

金鑰用途備用方案
GEMINI_API_KEY / GOOGLE_API_KEY圖片生成(media-use 解析)跳過生成 / 僅搜尋
(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 — 規劃(子代理:導演 Part 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 — 設計(子代理:導演 Part 2)

派遣一個子代理(提示 = agents/director.md 第二部分 + 派遣上下文,包括已解析的 assets/index.md(如果步驟 2 已執行)+ catalog-map.md)。它根據現有的素材設計分鏡:挑選 catalog 區塊 + 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 都依賴 media-use 搜尋(新聞/網頁/推文/圖片),這是 media-use 文件記錄的 RWA 路徑。
  • 重複使用優先: 生態系統中相當於 LLM 生成模板的是「組成 catalog 區塊 + 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            # IR(導演輸出)
      assets/  assets/index.md  # media-use 輸出(如有來源)
      compositions/index.html   # 建置者輸出
      renders/video.mp4
    
  • 註冊: 在 hyperframes 路由器中 — 新增「以設計為主導的短版動態圖形」意圖 + Workflow 描述;從 /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-nextjs

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

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

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

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

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

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

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

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

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

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

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

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

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.

相關技能