Communitygithub.com

1345AbhishekKumar/starter-nextjs

安裝並連接註冊區塊與元件至 HyperFrames 組合。使用於執行 hyperframes add、安裝區塊或元件、將已安裝項目連接到 index.html,或處理 hyperframes.json 時。涵蓋 add 指令、安裝位置、區塊子組合連接、元件片段合併、註冊發現,以及編寫新區塊或元件以便向上游貢獻(構想 → 框架 → 驗證 → PR)。

starter-nextjs 是什麼?

此技能專為 HyperFrames 生態系統設計,讓 AI 代理能透過 `hyperframes add` 指令安裝、連接和管理可重複使用的區塊與元件。區塊是獨立的子組合,擁有自己的尺寸、持續時間和時間軸,透過 `data-composition-src` 包含在主組合中;而元件是效果片段,直接貼入主組合的 HTML。技能引導代理處理安裝位置、區塊子組合連接(需指定 `data-composition-id`、`data-start` 和 `data-track-index` 屬性)、元件片段合併(需複製 HTML、CSS 和 JS),以及註冊發現(可透過 curl 讀取 registry.json)。此外,技能也支援貢獻流程,從構想到原型、驗證到發送 PR,附有範本參考。支援平台包括 HyperFrames CLI,適用於 Cursor、Claude Code 等代理環境。

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

在你喜歡的 AI 中提問

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

說明文件

HyperFrames 註冊中心

註冊中心提供可透過 hyperframes add <名稱> 安裝的可重複使用區塊與元件。

  • 區塊 — 獨立的子組合(擁有自己的尺寸、持續時間、時間軸)。透過 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 <目錄> --example <名稱>。

安裝位置

區塊預設安裝到 compositions/<名稱>.html。 元件預設安裝到 compositions/components/<名稱>.html。

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

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

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

連接區塊

區塊是獨立的組合 — 透過 data-composition-src 包含在主 index.html 中:

<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 中的完整工作流程:構想 → 框架 → 構建 → 驗證 → 預覽 → 發布。複製貼上的入門範本(字幕 / VFX / 元件 / registry-item.json)可在 templates.md 中找到。

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

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

相關技能