hyperframes-video
Use when the user wants to generate a rendered promotional video (not just a script) for a PR, feature, or product change — produces a HyperFrames HTML composition, iterates with `npx hyperframes preview`, and outputs mp4 + poster for X/LinkedIn/social.
AlemTuzlak · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add AlemTuzlak/skills --skill hyperframes-video技能说明
name: hyperframes-video
description: Use when the user wants to generate a rendered promotional video (not just a script) for a PR, feature, or product change — produces a HyperFrames HTML composition, iterates with npx hyperframes preview, and outputs mp4 + poster for X/LinkedIn/social.
HyperFrames Video
Turn a PR into a rendered short-form promo video with a hook, code moments, and CTA, using HyperFrames. Iterate with live preview via npx hyperframes preview, then render video.mp4 and poster.jpg for X/LinkedIn/social.
Unlike /video-script (which produces a textual script), this skill produces the actual video file. Counterpart to the remotion-video skill — same workflow shape, same storytelling rules, but built on the HyperFrames stack instead of Remotion.
Triggers
Invoke when the user says: "make a video for this PR", "hyperframes video", "render a promo video", "video for X/LinkedIn", or when selected from /marketing-pipeline.
How this skill relates to the hyperframes ecosystem
This skill carries only the promo-video-from-PR logic: input resolution, narrative planning, motif derivation, hook enforcement, scene-plan auditing, render-time gates. The mechanics of authoring HyperFrames compositions, running the CLI, animating with GSAP, and installing registry components are owned by separate skills you should invoke when their topic comes up:
hyperframes— composition authoring rules: DESIGN.md gate, Layout Before Animation, palettes, transitions, typography, motion principles, captions, audio, TTS.hyperframes-cli— everynpx hyperframes <command>(init, lint, inspect, preview, render, transcribe, tts, doctor, browser, info, upgrade, compositions, docs, benchmark).gsap— GSAP timeline patterns, easing, stagger, performance, position parameter, labels, nesting, playback.hyperframes-registry— registry blocks/components and how to wire them viahyperframes add.
When this skill needs to do something covered by one of those skills, defer to that skill's instructions rather than re-deriving them here.
Process Flow
Resolve input
→ Phase 1: Discovery
→ Phase 2: Configuration
→ Phase 3: Narrative planning
→ Phase 4: Scaffold
→ Phase 5: First draft + iterate
→ Phase 6: Render
→ Phase 7: Cleanup
Phases 1, 3, 5, and 7 have explicit approval gates. Phase 2 is an interactive Q&A. Phase 5 is a freeform iteration loop that can run many rounds.
"Use Sane Defaults" / "Don't Ask Questions" — What It Does and Doesn't Override
When the user invokes the skill with phrasing like "use sane defaults", "don't ask questions", "non-interactive", "just ship it", or any equivalent — interpret it precisely:
It DOES override (skip the prompt, pick the default):
- Q2.1 duration → derive from scope using the ladder in Q2.1 (still in the 15–60s window); pick the midpoint of the matched scope band and proceed without asking
- Q2.2 aspect ratio → 16:9 landscape
- Q2.3 project location →
marketing/<feature-slug>/hyperframes/ - Q2.4 brand confirmation (the "use these / customize / provide your own?" question)
- Phase 1.4 scope confirmation
- Phase 3.0 motif confirmation
- Phase 3.1 story-pattern confirmation
- Phase 3.3 scene-plan approval
- Phase 5 freeform iteration loop (the "what would you like to change?" prompt)
It does NOT override (must always run regardless):
- Brand color/font/logo scanning (Q2.4 detection — see HARD-GATE in Q2.4). Hardcoding colors from training-data assumptions about a project is a forbidden shortcut.
- Phase 5 preview (HARD-GATE in Phase 5). Even in fully unattended mode,
npx hyperframes previewmust start and the studio URL must be opened in the browser before the render runs. The user can interrupt; the agent must not pre-decide for them. - Phase 6 pre-render audits (storytelling, hook rules, motif presence, pacing variance, value-prop timing, contrast). These exist to prevent shipping a generic video.
- Phase 7 cleanup question (the user owns project disposition).
If you're tempted to skip a HARD-GATE because the user "said no questions" — re-read this section. The user said no questions, not no gates.
Input Resolution
Resolve the argument (if provided) in this order:
- Path to a marketing brief (
.mdcontaining "Executive Summary" or "Key Messages") → marketing brief - Path to a blog post (
.mdwith blog post structure) → blog post - Path to a changelog → changelog
- GitHub PR URL or
#\d+pattern → PR - Matches
<ref>..<ref>or<ref>...<ref>(alphanumeric +/,_,.,-on each side) → git ref range - Resolves to an existing file/directory → codebase feature
- Otherwise → freeform text
If no argument is provided, ask: "What should the video be about? You can provide a PR URL/number, marketing brief, blog post, changelog, git ref range, file/directory path, or just describe the feature."
When invoked from the pipeline with a PR and upstream marketing-brief/blog-post paths, read both: PR for technical accuracy, upstream content for positioning/tone.
(Detailed phase specs begin below — see Phase 1.)
Phase 1: Discovery
Step 1.1 — Check hyperframes skills availability
Attempt to invoke the hyperframes and hyperframes-cli skills via the Skill tool. If either is unavailable, present:
"The
hyperframes/hyperframes-cliskills aren't installed. Options: a) proceed with baseline knowledge (quality may be reduced) b) wait while you install them c) cancel"
If the user picks (a), emit a warning in the final summary noting reduced quality.
Step 1.2 — Analyze input
| Input type | What to read |
|---|---|
| Marketing brief | positioning, key messages, audience |
| Blog post | headline, narrative, examples |
| Changelog | highest-impact entry |
| PR | gh pr view <n> --json title,body,files,labels, diff (gh pr diff), commit messages, linked issues |
| Git refs | `gi |