Communitygithub.com

HyperFrames 註冊表管理

安裝並將註冊表區塊與元件整合至 HyperFrames 組合中。適用於執行 hyperframes add、安裝區塊或元件、將已安裝項目接入 index.html,或操作 hyperframes.json 時使用。涵蓋 add 命令、安裝位置、區塊子組合接線、元件片段合併、註冊表探索以及創作新區塊或元件以向上游貢獻(從構想到原型、驗證再到 PR)的完整流程。

HyperFrames 註冊表管理 是什麼?

這項技能提供了一個完整的 HyperFrames 註冊表管理工具,讓開發者能夠透過 `hyperframes add <name>` 命令輕鬆安裝可重複使用的區塊與元件。區塊是獨立的子組合,擁有自己的維度、時長與時間軸,透過 `data-composition-src` 引入宿主組合;元件則是效果片段,不具獨立維度,直接貼入宿主組合的 HTML 中。技能涵蓋了完整的安裝流程、組態設定(例如 hyperframes.json 中的路徑與註冊表 URL)、塊與元件的接線方式(關鍵屬性如 data-composition-id、data-start、data-track-index),以及透過 curl 瀏覽註冊表清單進行探索。此外,還支援創作全新的區塊或元件,並提供從構想到原型、驗證、預覽到提交 PR 的完整工作流程,適合需要擴充 HyperFrames 生態系的開發者。支援的平台包括 CLI 終端機與 HyperFrames 專案。

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

在你喜歡的 AI 中提問

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

說明文件

HyperFrames 註冊表

註冊表提供可透過 hyperframes add <name> 安裝的可重用區塊與元件。

  • 區塊 — 獨立的子組合(擁有自己的維度、時長、時間軸)。透過宿主組合中的 data-composition-src 引入。
  • 元件 — 效果片段(無自身維度)。直接貼入宿主組合的 HTML 中。

快速參考

hyperframes add data-chart              # 安裝一個區塊
hyperframes add grain-overlay           # 安裝一個元件
hyperframes add shimmer-sweep --dir .   # 指定目標專案
hyperframes add data-chart --json       # 輸出機器可讀格式
hyperframes add data-chart --no-clipboard  # 跳過剪貼簿(CI/無頭模式)

安裝後,CLI 會列出寫入的檔案以及一個可貼入宿主組合的片段。該片段僅為起點 — 當接線區塊時,你需要額外添加 data-composition-id(必須與區塊內部的組合 ID 一致)、data-start 和 data-track-index 屬性。

注意:hyperframes add 僅適用於區塊和元件。若需範例,請改用 hyperframes init <dir> --example <name>。

安裝位置

區塊預設安裝至 compositions/<name>.html。 元件預設安裝至 compositions/components/<name>.html。

這些路徑可在 hyperframes.json 中設定:

{
  "registry": "https://raw.githubusercontent.com/heygen-com/hyperframes/main/registry",
  "paths": {
    "blocks": "compositions",
    "components": "compositions/components",
    "assets": "assets"
  }
}

詳細資訊請參閱 install-locations.md。

接線區塊

區塊是獨立的組合 — 透過宿主 index.html 中的 data-composition-src 引入它們:

<div
  data-composition-id="data-chart"
  data-composition-src="compositions/data-chart.html"
  data-start="2"
  data-duration="15"
  data-track-index="1"
  data-width="1920"
  data-height="1080"
></div>

關鍵屬性:

  • data-composition-src — 區塊 HTML 檔案的路徑
  • data-composition-id — 必須與區塊內部的 ID 一致
  • data-start — 區塊在宿主時間軸中出現的時間(秒)
  • data-duration — 區塊的播放時長
  • data-width / data-height — 區塊畫布尺寸
  • data-track-index — 圖層排序(數值越大越上層)

詳細資訊請參閱 wiring-blocks.md。

接線元件

元件是片段 — 將它們的 HTML 貼入你的組合標記中,CSS 貼入樣式區塊,JS 貼入腳本區塊(若有):

  1. 讀取安裝好的檔案(例如 compositions/components/grain-overlay.html)
  2. 將 HTML 元素複製到你的組合的 <div data-composition-id="..."> 中
  3. 將 <style> 區塊複製到你的組合的樣式中
  4. 將任何 <script> 內容複製到你的組合的腳本中(放在你的時間軸程式碼之前)
  5. 如果元件提供了 GSAP 時間軸整合(請參閱片段中的註解區塊),將這些呼叫加入你的時間軸

詳細資訊請參閱 wiring-components.md。

探索

瀏覽可用的項目:

# 讀取註冊表清單
curl -s https://raw.githubusercontent.com/heygen-com/hyperframes/main/registry/registry.json

每個項目的 registry-item.json 包含:名稱、類型、標題、描述、標籤、維度(僅區塊)、時長(僅區塊)以及檔案清單。

關於依類型和標籤篩選的詳細資訊,請參閱 discovery.md。

貢獻新的區塊或元件

若要創作一個全新的註冊表項目(字幕樣式、VFX 區塊、轉場、下三分之一、或可重用的元件)並作為上游 PR 送出 — 而非安裝現有的項目 — 請遵循 contributing.md 中從構想到原型、建立、驗證、預覽到發佈的完整工作流程。可在 templates.md 中找到可直接複製貼上的入門模板(字幕 / VFX / 元件 / registry-item.json)。

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

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.

相關技能