Communitygithub.com

1345AbhishekKumar/starter-supabase

HyperFrames CLI 開發循環。在使用 `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` 或 `remove-background` 等指令,或對 HyperFrames 建置/渲染環境進行故障排除時使用。 AWS Lambda 雲端渲染的入口點(`hyperframes lambda deploy / render / progress / destroy / policies`)。

starter-supabase 是什麼?

本技能作為 HyperFrames CLI 的完整參考,HyperFrames 是一個用於建立和渲染基於 HTML 合成影片的強大框架。它定義了開發循環,從初始化專案、編寫合成、檢查錯誤,到預覽及最終渲染影片。此技能詳細說明 CLI 的約定,例如普遍可用的 `--json` 輸出旗標、用於非互動式環境的自動 TTY 偵測,以及讓渲染流程安全適用於 CI/CD 管線的嚴格門控選項。它還涵蓋了透過 `hyperframes lambda` 子命令進行 AWS Lambda 雲端渲染,讓使用者能將大型或長時間的渲染作業卸載至可擴展的雲端基礎設施。此外,它指定了處理 Tailwind 專案、註冊表區塊、資產預處理和參數化渲染等其他技能的交接點,使其成為任何 HyperFrames 開發者的核心技能。

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

在你喜歡的 AI 中提問

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

說明文件

HyperFrames CLI

所有操作都透過 npx hyperframes 執行,除非專案說明指定了本地包裝器。請嚴格遵守本地包裝器。需要 Node.js >= 22 和 FFmpeg。

工作流程

  1. 建立專案 — npx hyperframes init my-video(或從 URL capture)
  2. 撰寫 — 編寫 HTML 合成(參見 hyperframes-core 技能)
  3. Lint — npx hyperframes lint
  4. 驗證 — npx hyperframes validate(執行時期錯誤 + 對比度)
  5. 視覺檢查 — npx hyperframes inspect
  6. 預覽 — npx hyperframes preview 會開啟Studio,一個時間軸編輯器,使用者可以手動編輯任何內容(不僅是觀看)。在那裡審查,然後再詢問是否開始渲染。
  7. 渲染 — 選擇變體:
    • 迭代:npx hyperframes render --quality draft
    • 交付:npx hyperframes render --quality high --output out.mp4
    • CI / 跨主機重現:npx hyperframes render --docker --strict --output out.mp4
    • 雲端(長時間 / 大型):npx hyperframes lambda render ./my-project --width 1920 --height 1080 --wait(參見下面的 Lambda)

在預覽之前執行 lint、validate 和 inspect。lint 能捕捉遺失的 data-composition-id、重疊的軌道和未註冊的時間軸。validate 會在無頭 Chrome 中載入合成,並報告執行時期控制台錯誤以及 WCAG 對比度問題。inspect 會瀏覽時間軸,並報告文字溢出氣泡/容器或超出畫布的情況——而且,當存在 *.motion.json 附屬檔案時,它會根據相同的瀏覽時間軸驗證動作意圖(進入點在瀏覽時觸發、交錯順序、在畫面內、活躍度)。

對於動作密集型工作,偏好基於快照的迭代和 *.motion.json 附屬檔案——請參閱 references/lint-validate-inspect.md 了解規範和動作驗證規格。

代理約定

適用於每個指令的橫切規則:

  • --json 在所有指令上都可用,除了 render、preview 和 play。 對任何支援指令的代理 / CI 調用使用它;輸出包含一個 _meta 信封(cli 版本、最新可用版本、更新建議)。render 僅透過 stdout + 退出碼報告狀態——使用下面的渲染後檢查驗證成功;preview / play 是伺服器,沒有 JSON。
  • doctor --json 始終以狀態碼 0 退出,即使環境已損壞。根據 payload 的 ok 欄位進行閘控:npx hyperframes doctor --json | jq -e '.ok' > /dev/null。這能使管道免受 CLI 發布變動的影響。
  • 非 TTY 模式是自動偵測的。 當 stdout 不是 TTY(CI、代理、管道輸出)時,CLI 會自動切換到非互動式;init 接著需要 --example。傳遞 --non-interactive 即使在 TTY 上也能強制使用此模式。
  • CI 渲染閘控:--strict 遇到 lint 錯誤時失敗,--strict-all 遇到警告時也失敗,--strict-variables 遇到未宣告的 --variables 鍵時失敗。
  • --json 中的路徑會被脫敏 — $HOME 會被替換為字面上的 $HOME,以便輸出可以安全地貼上到錯誤報告和代理上下文中。
  • 渲染需要使用者閘控。 檢查通過後絕不能自動渲染。在 preview 時暫停,告訴使用者影片在 Studio 中是可編輯的,然後只有在他們批准後才渲染。
  • 渲染後驗證。 在 render 返回退出碼 0 後,在報告成功之前確認輸出檔案存在且大小合理:[ -s "$OUTPUT" ] || echo "render produced no output"。CLI 會在成功時列印 ◇ <path>;對於長時間渲染,也使用 ffprobe -i "$OUTPUT" -show_format -v error 進行完整性檢查時長。

路由

想要…請閱讀
建立專案 (init, capture, skills)references/init-and-scaffold.md
檢查正確性 (lint, validate, inspect, snapshot)references/lint-validate-inspect.md
預覽或渲染 (preview, play, render, publish)references/preview-render.md
診斷環境 (doctor, browser)references/doctor-browser.md
在 AWS Lambda 上進行雲端渲染 (lambda deploy / sites / render / progress / destroy / policies)references/lambda.md
其他 (info, upgrade, compositions, docs, benchmark, telemetry, 資源預處理)references/upgrade-info-misc.md

跨技能交接

  • Tailwind 專案 (init --tailwind) → 在編輯類別或主題令牌之前,使用 hyperframes-core(Tailwind 參考)。
  • 註冊表區塊/元件 (hyperframes add, hyperframes catalog) → 使用 hyperframes-registry 來處理安裝路徑、子合成接線和程式碼片段合併。
  • 資源預處理 (tts, transcribe, remove-background) → 使用 hyperframes-media 來處理語音選擇、Whisper 模型規則、字幕以及 TTS 轉字幕鏈。
  • 參數化渲染 (--variables) → 透過 <html> 上的 data-composition-variables 宣告;請參閱 hyperframes-core 了解完整架構。

Lambda (雲端渲染)

hyperframes lambda 將分散式渲染部署到 AWS Lambda,並從您的筆記型電腦或 CI 驅動渲染。端到端需要三個指令:

npx hyperframes lambda deploy                                             # 佈建 SAM 堆疊 (Lambda + Step Functions + S3)
npx hyperframes lambda render ./my-project --width 1920 --height 1080 --wait
npx hyperframes lambda destroy                                            # 拆除 (S3 儲存桶會被保留)

當渲染時間過長 / 檔案過大而無法在單一主機上完成時(例如數分鐘長的影片、4K、大型並行批次),並且您已配置 AWS 憑證,請使用 Lambda。對於開發循環迭代,請繼續使用本地端的 render。

請參閱 references/lambda.md 了解先決條件、所有 6 個子指令 (deploy, sites create, render, progress, destroy, policies)、IAM 政策驗證、狀態檔案以及成本/清理規則。

最低完成閘控

靜態閘控

npx hyperframes lint
npx hyperframes validate

對於佈局敏感的工作,請新增 inspect;在 CI 中,請新增 render --strict 以在 lint 錯誤時失敗。

視覺冒煙測試 — 當專案使用子合成時必需

lint / validate / inspect 各自獨立評估每個合成。它們從不載入 index.html 並透過 data-composition-src 掛載子合成,因此無法捕捉跨檔案掛載失敗(請參閱 hyperframes-core → references/sub-compositions.md 中的「常見陷阱」)。唯一能捕捉它們的閘控是實際載入 index.html 並瀏覽時間軸的測試。

使用 hyperframes snapshot——它如同 render 一樣載入專案(因此會執行相同的掛載路徑),但只會捕捉您要求的時間點,因此只需幾秒鐘,而非完整的渲染:

# 在每個子合成的中點捕捉一個影格。
# 中點 = index.html 中每個主機位置的 data-start + data-duration/2。
npx hyperframes snapshot --at <t1>,<t2>,<t3>,...

# 或者,如果您不需要針對每個場景,可以使用均勻分佈的樣本:
npx hyperframes snapshot --frames 9

輸出會存放在 snapshots/frame-NN-at-Xs.png。對照場景計畫目視檢查每個影格。

每個影格的紅旗(每個都對應到靜態閘控遺漏的特定失敗模式):

您看到的現象根本原因
文字在左上角以微小且無樣式的形式顯示<style> 區塊遺留在 <head> 中,位於 <template> 外部(陷阱 1)—— 沒有 CSS 到達即時 DOM
SVG/圖示元素放大到畫布大小同上——未套用寬度/高度限制
場景的主角元素完全遺失;僅顯示背景和浮水印主機 id ≠ 模板 id(陷阱 2)—— 時間軸從未執行,影格在初始狀態時被捕捉
Snapshot 指令記錄 Sub-composition timelines not registered after 45000ms陷阱 2——直接確認

目視檢查後可以刪除 snapshots/;面向使用者的最終渲染是使用 npx hyperframes render 進行的單獨步驟。

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

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 wants a short, design-led motion graphic where motion is the message: kinetic typography, stat or number count-up, chart/data-viz hit, logo sting, brand lockup, lower-third, callout, social overlay, animated headline/tweet/news item, motion poster, or quick captured-page highlight. Usually under 10s and up to ~30s, with no narration arc, voice-over, or live-action subject. Can render to MP4 or transparent overlay. Not for longer, multi-scene, narrated, or brand-reel pieces (use general-video), narrated website videos (website-to-video), topic explainers (faceless-explainer), product promos (product-launch-video), PR videos (pr-to-video), or captions on existing footage (embedded-captions). When unsure whether it's a quick motion-first piece or a longer / narrated treatment, see /hyperframes.

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.

相關技能