Communitygithub.com

1345AbhishekKumar/starter-nextjs

用于创作任意长度或格式的自定义 HyperFrames 视频合成的工作流,包括品牌/精彩片段、蒙太奇、标题卡、静态循环及自由格式作品——当专业工作流不适用时的通用回退方案。

starter-nextjs 是什么?

此技能是 HyperFrames 视频创作生态中的通用回退工作流,专门用于处理不匹配任何专业化工作流的任意输入。它支持任何长度和格式的视频合成,包括品牌宣传片、精彩集锦、蒙太奇、标题卡、静态循环和自由格式作品。该技能强调严谨的设计流程:首先建立视觉规范(通过读取 house-style.md 和 video-composition.md),找到概念角度,选择字体搭配,并规划前景密度。然后进行提示扩展(针对多场景作品),制定包含叙述弧线、结构、节奏、时间线和布局的计划。最后,通过 hyperframes-animation 添加动画。技能还集成了统一的音频引擎(TTS、BGM、SFX),通过 hyperframes-media 处理音频请求,并利用音频反应式技术增强观赏体验。关键要求包括:不得发明设计系统(必须引用规范文件),构建最终状态布局(再添加动画),以及使用指定的动画技术库。

兼容平台~Claude Code~Codex CLI✓Cursor
npx skills add https://github.com/1345AbhishekKumar/starter-nextjs/tree/HEAD/.agents/skills/general-video

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

文档

media-use:在获取音频/图片之前,请先调用 /media-use 从 HeyGen 目录中解析背景音乐/音效/图片。首先运行 --adopt 注册现有资产。详见 /media-use 技能。

general-video — 通用视频工作流

在开始构建之前确认路线。 这是自定义合成创作的回退工作流。如果输入明显符合某个专业化工作流,请优先选择:营销产品 → /product-launch-video;通用网站 → /website-to-video;主题讲解 → /faceless-explainer;GitHub PR → /pr-to-video;现有素材 → /embedded-captions · /talking-head-recut;短无声动态图形 → /motion-graphics;Remotion 移植 → /remotion-to-hyperframes。超出范围:实时/渲染时数据、NLE 风格的已完成视频编辑、或生成 HyperFrames 无法捕捉的素材。不确定?先阅读 /hyperframes。

精确构建所要求的内容。 标题卡就是标题卡——不是标题卡加三个辅助场景加环境音乐加字幕。如果额外的场景或元素确实能提升作品,请_提议_它们;不要擅自添加。对于小编辑(修改颜色、调整一个时长、添加一个元素),跳过规划步骤,直接构建。

方法

探索——仅针对开放式请求

对于模糊的、探索性的请求(“为我们的品牌做点什么”、“一个很酷的片头”)——在选择颜色之前先了解意图:

  • 受众——谁观看?开发者 / 高管 / 普通消费者?
  • 平台——在哪里播放?社交媒体(15 秒)/ 网站英雄区 / 产品演示 / 内部?
  • 优先级——什么最重要?动作质量 / 内容准确性 / 品牌忠诚度 / 速度?
  • 变体——一个最佳版本,还是 2-3 个有意义的变体(不同的节奏、能量或结构——而不仅仅是颜色替换)?

对于具体请求(“添加标题卡”、“调整场景 3 的时间”),跳过探索。

第一步——设计系统 → hyperframes-creative

首先建立视觉标识。如果项目有设计规范,请阅读它(优先级 frame.md → design.md → DESIGN.md;将其视为品牌真实来源——精确的颜色、字体、约束)。

如果没有规范,在选择任何颜色或字体之前,你必须同时阅读 hyperframes-creative/references/house-style.md 和 hyperframes-creative/references/video-composition.md。 house-style.md 提供了“解释提示 / 生成真实内容”的开始、惰性默认列表和图层配方;video-composition.md 提供了视频媒介密度 / 比例 / 前景细节(数据条、注册标记、等宽元数据、“8-10 个元素,其中两个用户没有要求”),这些是将“制作的”与“生成的”区分开来的关键。只阅读其中一个是最常见的错误——video-composition.md 是智能体经常跳过的文件,而正是这个文件防止了输出扁平、居中、像网页一样的外观。不要自行发明调色板并跳过这些文件;进入 hyperframes-creative 是必须的,而不是可选分支。然后,根据需要,从 references/visual-styles.md 中提取命名的风格/情绪,或使用交互式选择器 references/design-picker.md。规范/风格定义了品牌,而不是合成规则。

找到角度(模糊简报,无规范): 在选择颜色之前,写一句话——这个名称/词/主题唤起什么,以及什么视觉_世界_(隐喻、场景、乐器、主题)能表达它?例如,网络安全工具→保险库门/周界扫描线/锁芯;冥想应用→潮汐、呼吸、缓慢的光晕,阅读主题的_含义_,而不仅仅是它的文字;选择一个具体的角度而不是字面上的重新设计。这是单场景作品中提示扩展(第二步)的廉价替代品(扩展被正确跳过)——这也是设计概念与通用渐变色 logo 之间的区别。

第二步——提示扩展 → hyperframes-creative

针对每个多场景合成运行(跳过单场景作品和微不足道的编辑)。将请求基于设计规范和 house style,形成一个一致的中介表示,使下游工作以相同方式读取。参见 hyperframes-creative/references/prompt-expansion.md。

第三步——计划

在编写 HTML 之前,从较高层面思考:

  1. 内容——观众体验:叙述弧线、关键时刻、情感节奏。
  2. 结构——多少个合成、子合成与内联、哪些轨道承载视频/音频/覆盖/字幕。关于单文件与模块化子合成的选择,参见 hyperframes-core/references/composition-patterns.md § 两种架构(经验法则:≥3 个硬场景切换,或任何重复使用的场景 → 模块化;短的单场景作品保持一个文件)。
  3. 节奏——在实现之前命名模式(例如 fast-fast-SLOW-SHADER-hold);参见 hyperframes-creative/references/beat-direction.md。
  4. 时间——哪些剪辑驱动时长、转场落在哪里、节奏。
  5. 布局——首先构建最终状态(见下文)。
  6. 动画——然后通过 hyperframes-animation 添加动作。

布局优先于动画

将每个元素放置在其最显眼时刻所在的位置——完全进入、正确放置、尚未退出。首先将其编写为静态 HTML + CSS。尚未使用 GSAP。

原因: 如果你在元素的动画起始状态(屏幕外、缩放到 0、透明度 0)定位它们,并渐变到你_认为_它们落地的位置,你是在猜测最终布局——重叠问题在渲染之前都是不可见的。先构建最终状态,你就能在添加动画之前看到并修复布局问题。

  1. 为每个场景确定英雄帧——大多数元素同时可见的时刻。那就是你要构建的布局。
  2. 为该帧编写静态 CSS。内容容器必须填充场景并使用内边距,而不是绝对偏移:
.scene-content {
  display: flex;
  flex-direction: column;
  justify-content: center;
  width: 100%;
  height: 100%;
  padding: 120px 160px; /* 内边距定位内容;填充任何场景大小 */
  gap: 24px;
  box-sizing: border-box;
}

切勿在内容容器上使用 position: absolute; top: Npx——当内容高于空间时会导致溢出。将绝对定位保留给装饰元素。

⚠ 上述的 width/height: 100% 仅在每个祖先都有确定的高度时生效。 根 <div data-composition-id> 以及它和 .scene-content 之间的任何包装器都必须设置尺寸(在根元素上设置 position: relative; width: 1920px; height: 1080px——参见 hyperframes-core → “根必须设置尺寸”)。跳过此步骤,flex 容器会塌缩到约 0,内容堆叠到左上角,并且第一个字形在 x=0 处被裁剪——而 lint/inspect 仍然报告 0 个问题。并且始终在 .scene-content 上保留 padding(≥80px):这是标题安全边距。切勿用裸 gap 替换它。

  1. 添加入场——使用 gsap.from() 从屏幕外/不可见状态动画到 CSS 位置(在子合成中建议使用 gsap.fromTo(),使起始状态明确;参见 hyperframes-core/references/sub-compositions.md)。CSS 位置是真实位置;渐变是到达它的路径。
  2. 退出由转场处理——根据 hyperframes-animation/transitions/ 中的场景转场规则,只有最终场景将元素动画退出;场景之间转场本身就是退出。

跨时间的共享空间: 如果在同一区域元素 A 在元素 B 进入之前退出,两者仍然需要为各自的英雄帧设置正确的 CSS 位置——时间线排序使它们不会共存,而布局步骤会捕捉意外的重叠。分层发光/阴影和 z 叠加深度是_有意_的重叠;该步骤的目的是捕捉_意外_的碰撞(两个标题叠加在一起、内容溢出画面)。

构建——委托给领域技能

这会将技能的完整表面(参见 description)映射到其参考资料——非详尽列表;当意图未列出时,通过 hyperframes-creative(外观/概念)、hyperframes-animation(动作)、hyperframes-core(协定)、hyperframes-media(音频/字幕)路由。第一行是追加的——请同时阅读它和你的意图行,而不是只读一个。

构建…首先阅读(按顺序)
始终——每个非平凡作品,加上下文的意图行hyperframes-creative/references/house-style.md + references/video-composition.md(也在第一步/HARD-GATE 中要求;“制作的,而非生成的”前景细节)
动态排版 / 文本优先hyperframes-animation/techniques.md(动态类型)+ adapters/gsap-easing-and-stagger.md + rules/kinetic-beat-slam.md
标题卡 / 下三分之一 / 覆盖 / 画中画 / 文字背后主题hyperframes-creative/references/composition-patterns.md +(对于居中/定尺寸的帧)hyperframes-core → “根必须设置尺寸”
Logo / 品牌标记揭示hyperframes-animation/rules/svg-path-draw.md(绘制)+ rules/3d-text-depth-layers.md + rules/scale-swap-transition.md
数据 / 统计 / 数字hyperframes-animation/rules/counting-dynamic-scale.md + rules/stat-bars-and-fills.md + hyperframes-creative/references/data-in-motion.md
产品 / 应用 / 用户界面演示hyperframes-animation/rules/3d-page-scroll.md + rules/cursor-click-ripple.md + rules/press-release-spring.md
音频反应 / 音乐驱动hyperframes-creative/references/audio-reactive.md(预提取频段;映射到动作)
旁白 / 画外音 / 音乐 / 音效 / 字幕hyperframes-media → 共享的音频引擎 scripts/audio.mjs(一次调用 = TTS + BGM + SFX → audio_meta.json);字幕创作 + 资产放置通过 hyperframes-core。参见下面的音频部分。
多场景 / 转场hyperframes-animation/transitions/overview.md 然后 transitions/catalog.md(阅读概述后并未完成——GSAP 配方在目录中)
模块化 / 子合成hyperframes-core/references/composition-patterns.md + references/sub-compositions.md

音频:单一引擎(TTS · BGM · SFX)

仅当作品需要时才使用(根据“精确构建所要求的内容”——标题卡上没有环境音乐)。不要手动实现 TTS 或使用供应商副本:编写一个中性的 audio_request.json 并调用 hyperframes-media 中的共享引擎。它会在一个开关上自动降级——存在 HeyGen 凭证 → HeyGen TTS + 音乐/SFX 检索;不存在 → ElevenLabs/Kokoro TTS,Lyria/MusicGen BGM 生成,以及捆绑的 SFX 库。完整标志列表 + 请求/元模式:见 hyperframes-media/scripts/audio.mjs 的头注释。

// audio_request.json — 每个旁白片段一行;`id` 由你指定(将 audio_meta 连接回来)
{
  "lines": [
    { "id": "s1", "text": "你的开场白。", "sfx": ["whoosh"] },
    { "id": "s2", "text": "下一个节拍。" },
  ],
  "bgm": { "query": "calm cinematic underscore" }, // 省略 "mode" → 自动(如果 HeyGen 则检索,否则生成);"none" 以禁用
}
# <MEDIA_DIR> = 已安装的 hyperframes-media 技能目录(此技能的兄弟目录)
node <MEDIA_DIR>/scripts/audio.mjs --request ./audio_request.json --hyperframes . --out ./audio_meta.json

然后读取 audio_meta.json:将每个 voices[].path +(bgm.path、sfx[])挂载为 <audio> 轨道,并使用 voices[].words 作为字幕,全部根据 hyperframes-core(音频轨道 + 字幕创作)。如果 BGM 采用了生成路径(bgm_pending: true),则在最终渲染之前运行 hyperframes-media/scripts/wait-bgm.mjs。

输出清单 → hyperframes-cli

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

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

相关技能