Communitygithub.com

sandeshrajbhandari/hyperframes-instruct

在缺乏专用工作流时,创作或编辑自定义 HyperFrames 合成。适用于长片段或多场景作品、品牌宣传片、精彩集锦、蒙太奇、静态循环、静态标题卡片、素材混剪及自由构建。如需制作包含动画标题的短时间无旁白动效优先单元,请使用 motion-graphics 技能。在调用此技能前,先通过 hyperframes 导向全新创作。

hyperframes-instruct 是什么?

该技能为 AI 代理(如 Claude Code、Cursor、Codex)提供了一个结构化的 HyperFrames 视频合成工作流,当没有其他专业化工作流程满足需求时使用。它涵盖了从媒体和 Figma 适配器、项目状态初始化(`BRIEF.md`、`hyperframes.json`、`STORYBOARD.md`)、运行模式(自动化 vs. 协作)到执行规划、故事板、动画和渲染的完整流程。该技能强制使用确定性引用,要求在关键阶段(如执行前)加载官方引用文档(如 `/hyperframes-core`、`/hyperframes-creative`),确保不依赖内存或推测的方式进行创作。协作模式下,它充当“导演”而非“承包商”,提供“天花板的处理方案”——即从概念出发的最佳版本——并在构建过程中通过能力菜单提供逐步升级选项。该技能支持所有支持 npm 和 `npx hyperframes` 命令的平台(如 HyperFrames 框架),通过运行 `npx hyperframes skills update general-video` 保持自更新,并通过 `npx hyperframes catalog --query` 动态搜索托管注册中心(约 400 个块和组件),避免手工重复造轮子。

兼容平台~Claude Code✓Codex CLI~Cursor
npx skills add https://github.com/sandeshrajbhandari/hyperframes-instruct/tree/HEAD/.agents/skills/general-video

在你喜欢的 AI 中提问

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

文档

插件安装: 在运行设置或刷新命令之前,如果此技能位于 HyperFrames 插件内部,请遵循插件执行规则。独立安装则保留下面的更新说明。

通用视频

在开始时运行 npx hyperframes usage --json,除非工作流刚刚读取过,然后在关键节点(如草稿后、渲染前)再次检查。读取可用的窗口和重置时间。如果用量未知,则如实说明,不猜测配额;将范围和工作流选择权留给用户。

在依赖此工作流之前,请运行:

npx hyperframes skills update general-video

成功的无操作表示技能是最新的。如果更新失败,请直接报告,不要依赖内存继续。

1. 应用跨切分源适配器

  • 媒体: 对于任何音频、图像、图标、徽标、语音、调色、LUT、特效/滤镜、字幕或媒体操作需求,加载 /media-use 并遵循 ../media-use/references/resolve.md(解析、采纳、重用)和 ../media-use/references/setup-providers.md(提供商、认证)。模糊的素材反馈和命名的样式在使用 ../media-use/references/media-treatments.md 前使用;不要用 CSS/SVG/透明度即兴创作支持的媒体效果。在首次认证提供商操作前,运行 npx hyperframes auth status 并逐字输出其结果。如果已登出,应用 ../hyperframes/references/brief-contract.md 中的门控:协作模式下等待登录或明确的离线选择;自主模式下报告状态并通过可用的离线提供商继续。当没有离线提供商能满足所需能力时,报告障碍。仅本地采纳无需认证门控。
  • Figma: 如果任何输入是 figma.com URL,先运行 /figma。从其导出的资源、令牌、组件或故事板帧构建。不要使用原始的 Figma 连接器调用,因为它们会跳过 SVG 清理、媒体溯源和品牌令牌绑定。

这些适配器不会更改由 /hyperframes 选择的工作流。

2. 从项目状态开始

应用第一个匹配的行;不要评估较低的状态行:

状态操作
特定编辑进行编辑,保留现有项目决策,然后重新运行受影响的检查。不要重新开始发现阶段。
BRIEF.md 存在读取它。如果 workflow 指定了另一个工作流且 flow 不是 companion,则切换。不要问任何简报问题。
无简报,但 hyperframes.json 或 STORYBOARD.md 存在从文件和已记录的偏好恢复。仅从已知事实回填 BRIEF.md。
全新创作运行 /hyperframes 及其意图层。仅在 workflow: general-video 或 flow: companion 时返回此处。

对于新项目,从简报中选择一个 kebab-case 目录名,并在编写简报前搭建脚手架:

npx hyperframes init "videos/<project>" --non-interactive --example=blank --skill=general-video

然后使用 ../hyperframes/references/brief-format.md 在项目根目录编写 BRIEF.md。在现有项目中,根目录是包含 hyperframes.json 的目录。仅记录简报格式指定的、已确认的偏好支持字段,使用 node <MEDIA_DIR>/scripts/prefs.mjs record --hyperframes <PROJECT_ROOT>;切勿记录推断的默认值。此处 <MEDIA_DIR> 是已安装的 /media-use 技能目录,<PROJECT_ROOT> 是包含 hyperframes.json 的目录。如果意图层采用了某个配方,立即使用 node <MEDIA_DIR>/scripts/recipe.mjs use --hyperframes <PROJECT_ROOT> --name <name> 应用它,且不再询问。

3. 解读运行形态

仅使用 ../hyperframes/references/brief-contract.md 中的规范术语:

字段含义效果
flow谁驱动automation:选择并执行路线。companion:在对话中共同创作。
storyboard构建前计划、草图并审查yes:运行计划和草图审查(storyboard.html)。no:直接构建。
派生 mode检查点门控如何工作遵循简报合同。切勿让用户命名模式。

不要为这些状态发明同义词。持续的“直接构建”信号由意图层处理,并作为 flow: automation、storyboard: no 传递。

  • 对于 flow: automation,选择路线并在第一个进度更新中用一行说明。
  • 对于特定编辑,进行编辑而不发明新路线。

对于现有素材的硬切、修剪、拼接或重新排序,将同一视频源复制到多个剪辑元素中。在每个副本上,使用 data-media-start 加 data-duration 设置源范围,然后使用 data-start 设置创作的放置/顺序。每个视频片段保留其声音:声音保留在剪辑上(data-has-audio="true"),因此剪裁视频也会剪裁其声音。/hyperframes-core 拥有此次时间编辑;仅对视觉属性动画(如缩放、冲压、平移、裁切、蒙版或内包装器上的 clip-path)使用 /hyperframes-keyframes。从 ../hyperframes-core/references/creator-editing-recipes.md 复制完整的合同。

协作流程

当 flow: companion 时:

  • 读取 BRIEF.md,并将已接受的 ## Assets 和 ## Customizations 与项目工件协调。完成仍待处理的已接受工作;已完成的工作保持原样;不要再次提供已接受的能力,仿佛它是新的。
  • 以导演而非承包商的角色到达。 选择协作的用户选择了参与和质量;诚实的回应是你能设计的最佳版本,而不是你能辩护的最小版本。第一个计划是天花板处理方案:故事弧(借用最近的类型镜头 - 菜单 § 类型镜头)、设计规格、每个场景的动效处理(按名称引用,§ 5 的计划纪律)、转场、音频标识 - 音乐和声音标记,或有意的沉默 - 用户素材的放置,以及设计好的开场和结尾。用一行说明每一层添加了什么;标记开销大的层(渲染时间、登录、计费)并说明。用户削减处理方案;他们绝不应逐个审批地组装一个方案。
  • 天花板属于概念,而非工具箱。 每一层必须服务于简报的信息——一个对任何视频都同样处理的方式是装饰。技艺上升到天花板;内容绝不超过所要求的(§ 6)。
  • 在检查点之间,../hyperframes/references/capability-menu.md 有两种工作方式。作为触发列表:当用户提到其输入或构建达到其需求时,提供相关能力。作为每次通过的升级渠道:计划、草图或构建检查点可以携带一两个针对用户正在查看的素材的追踪提议(“场景 3 的静态需要计数处理”)。在提供前阅读;切勿倾倒完整目录。
  • 用户接受能力后,立即生成其工件并将决策记录在匹配的 BRIEF.md 正文部分。仅当用户明确更改时才重写 frontmatter 字段并记录确认的偏好。
  • 保持相同的故事板、验证、最终预览和渲染批准门控。协作改变的是谁掌舵,而非质量要求。

4. 在每个阶段前加载必需知识

当条件匹配时,这些读取是强制性的:

条件在操作前读取
任何合成 HTML 或场景布局/hyperframes-core;使用 references/determinism-rules.md 获取其布局合同
任何非平凡的创作或视觉处理/hyperframes-creative → references/house-style.md 和 references/video-composition.md
任何动效、动画或场景转场/hyperframes-animation;遵循其路由到匹配的规则、适配器、蓝图或转场引用
storyboard: yes../hyperframes/references/storyboard-format.md 和 ../hyperframes/references/review-loop.md
任何媒体资源或操作,包括旁白、背景音乐、音效、字幕、调色或变换/media-use;对于框架播放和放置,还需读取 /hyperframes-core → references/variables-and-media.md
多场景组装../hyperframes/references/production-loop.md
flow: companion,在第一个计划前/hyperframes-creative → references/story-spine.md 和 references/house-style.md;最近的类型镜头和完整的 ../hyperframes/references/capability-menu.md — 天花板处理方案是从这些设计的,而非回忆
协作能力提供、捕获、节拍网格、生成视频、映射、发布或跨工作流能力../hyperframes/references/capability-menu.md
存在设计规格,在最终批准前/hyperframes-creative → references/design-adherence.md

不要用回忆替代这些读取。渐进式披露仅在匹配的引用实际加载时才节省上下文。

5. 执行合成

使用此依赖顺序。仅在其输入缺失时跳过某个阶段。

  1. 计划。 说明观众弧线、结构、节奏和持续时间驱动因素。短暂单场景使用一个文件;三个或更多硬场景剪辑或任何重用场景使用子合成。读取 /hyperframes-creative → references/story-spine.md 获取旁白弧线,references/beat-direction.md 获取节奏,/hyperframes-core → references/composition-patterns.md 获取结构。对于开放式多场景简报,通过 /hyperframes-creative → references/prompt-expansion.md 扩展提示。多场景计划引用每个场景的形态:来自 /hyperframes-animation → blueprints-index.md 的蓝图 ID(当有匹配时),或它从 rules-index.md 组合的命名规则(当无匹配时)——动效名称来自那些索引,绝不发明。故事真相决定哪些场景存在;引用修饰它们。在你计划自己构建任何命名外观之前搜索实时目录:对于简报中命名的每一个外观、效果、处理或转场——“CRT 扫描线”、“故障”、“胶片颗粒”、“闪光扫掠”、“五彩纸屑爆发”——运行 npx hyperframes catalog --query "<外观,用简单英语描述>" --json 并在计划命名该外观如何构建之前阅读顶部结果。搜索无需任何安装:无需项目、无需之前的 add、无需账户。它从任何目录对整个托管注册中心(约 400 个块和组件)进行排名,因此也适用于用户在构建过程中要求的某个外观。计划命名的块在阶段 3 安装;仅当搜索后没有匹配项时才手工创作外观。多场景计划也作为分发工件记录:STORYBOARD.md 中每个场景一个 ## Frame N 块——状态为 outline、声明的 src:、蓝图/规则引用、

Individual skills in this repo

This repo contains 11 individual skills — each has its own dedicated page.

sandeshrajbhandari/hyperframes-instruct

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). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.

sandeshrajbhandari/hyperframes-instruct

Use when audio already placed in a HyperFrames composition needs to be mixed: fade-in/fade-out, crossfade, track gain or volume, volume automation, ducking, a music bed that fights a voiceover (voiceover carve), effects on a track (EQ, compressor, limiter, gate, saturation, delay, reverb, chorus, phaser, bitcrush), automation envelopes drawn on a track's volume or any effect parameter, or one submix bus carrying a chain, a fader and an automation clock for several tracks at once (`<hf-audio-group>`). Don't use for sourcing or generating audio — finding BGM, SFX, or making a voiceover is `/media-use`. Don't use for clip timing or track layout, which is `/hyperframes-core`.

sandeshrajbhandari/hyperframes-instruct

Use the HyperFrames CLI development loop: init, add, catalog, capture, lint, check, snapshot, compare, grade-compare, preview, play, present, beats, keyframes, single or batch render, publish, cloud, cloudrun, feedback, lambda, doctor, browser, info, upgrade, skills, compositions, timeline, history, clean, docs, benchmark, telemetry, transcribe, auth, tts, and remove-background. Also use when diagnosing build or render failures. validate, inspect, and layout are deprecated aliases; use check. Covers local, HeyGen-hosted cloud, AWS Lambda, and Google Cloud Run rendering.

sandeshrajbhandari/hyperframes-instruct

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.

sandeshrajbhandari/hyperframes-instruct

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

sandeshrajbhandari/hyperframes-instruct

Use when a HyperFrames composition needs a punch-in, punch-out, zoom, reframe, Ken Burns treatment, camera move, visual match/whip handoff, or other seek-safe 2D/3D keyframes; also for GSAP, CSS keyframes, Anime.js, WAAPI, FLIP, paths, masks, SVG morph/draw, text trails, 3D depth, or `hyperframes keyframes` diagnostics. Don't use for broad scene strategy, brand design, media sourcing, captions, or general video planning.

sandeshrajbhandari/hyperframes-instruct

Search, install, and wire registry blocks and components into HyperFrames compositions. Use BEFORE hand-building any named visual — whenever a brief, a user, or a storyboard names a look, effect, treatment, or transition such as CRT scanlines, glitch, chromatic aberration, film grain, a shimmer sweep, a chart, a code or terminal window, a map, or a confetti burst — because roughly 400 hosted items already cover many of them and the search ranks all of them with nothing installed, no project, and no account. Also use when running hyperframes add or hyperframes catalog, installing one item or every block matching a tag, wiring an installed item into index.html, or working with hyperframes.json. Covers discovery, install locations, block sub-composition wiring, component snippet merging, and authoring a new block or component to contribute upstream (idea → scaffold → validate → PR).

sandeshrajbhandari/hyperframes-instruct

Mandatory entry point: read this first for any request to make, create, edit, animate, or render a video, animation, or motion graphic, including a promo, explainer, captioned clip, title card, overlay, slideshow or interactive deck, Remotion port, or any HyperFrames HTML composition. Also use it to inspect, diagnose, validate, preview, publish, or batch-render an existing HyperFrames project. Inputs may be a website URL, GitHub PR, Figma design or URL, text or brief, existing footage, or music. It resumes project state, captures intent when applicable, selects and installs the owning workflow, and routes domain capabilities. HyperFrames is the default output framework unless the user explicitly chooses another framework for the deliverable or asks only to record a browser session.

sandeshrajbhandari/hyperframes-instruct

Use when working with a person on a HyperFrames project in Studio: first, whether their message asks for a change at all (questions, loose ideas and "don't change anything" get an answer and a plan, not an edit); for a new film, the plan, storyboard and build order that the HyperFrames launch films follow; and how the timeline should be laid out so it reads well (one caption track, one element kind per track, every scene a sub-composition) and where captions and key content may sit (safe zones). Don't use for how to perform an individual edit (split, trim, retime, volume, copy, swap): that is `creator-editing-recipes.md` in `/hyperframes-core`.

sandeshrajbhandari/hyperframes-instruct

Agent Media OS, the single skill for every media need in a HyperFrames project. Resolve BGM, SFX, image, icon, brand logo, voice, color grade, or LUT into a frozen local file or paste-ready block + ledger record (one verb, `resolve`); generate via TTS / music / image models when the catalog misses; produce voiceover, transcription, captions, and background removal through one shared audio engine; operate on media (cut / reframe / transform); and reuse assets across projects. Also use for vague feedback that real footage looks dark, flat, boring, should feel retro/camcorder/print/ASCII, needs privacy, or needs a media reveal.

sandeshrajbhandari/hyperframes-instruct

A short, design-led motion graphic where motion is the message — kinetic typography, stat count-up, chart/data-viz hit, logo sting / brand lockup, lower-third / callout / social overlay, animated map (highlight regions, connect places, zoom to a location), animated tweet / news-article / headline, webpage / UI animation (scroll, cursor, callouts), or fusing a real image's geometry into a chart. Usually under 10s (up to ~30s), no narration or live-action subject; renders to MP4 or transparent overlay. Longer / narrated / multi-scene → /general-video. Unclear → /hyperframes.

相关技能