hyperframes
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.
1How It Works & Mechanism
Acts as the mandatory entry point and routing layer across the 20+ skill ecosystem: SKILL.md uses a table-driven decision process based on existing project state (port / specific operation / edit / BRIEF.md / hyperframes.json / fresh creation), stopping at the first matching row instead of re-running intent interviews every time.
Apply the first matching row; do not evaluate lower state rows:
Directs fresh creations to a dedicated intent interview layer (references/intent-interview.md 8 steps: memory → triage → pick route → pitch → must-haves → run-shape → write BRIEF.md → wrap-up), crystallizing interview findings into BRIEF.md—making the brief the sole routing artifact, after which this skill is never re-read.
For fresh creation the intent layer (`references/intent-interview.md`) runs the full conversation — memory, triage, pitch round, must-haves, run-shape, hand-off — and **ends by writing `BRIEF.md`. The brief is the only routing artifact the workflow reads**
Matches distribution routes by deliverable rather than keywords: 10 workflow rows (remotion port → slideshow → embedded-captions → talking-head-recut → music-to-video → motion-graphics → pr-to-video → product-launch-video → faceless-explainer → general-video) accompanied by 7 disambiguation rules.
Use the first matching row. Match the requested **deliverable**, not a word or file type mentioned in passing.
Mandates refreshing or installing target workflows and core domain skills prior to entering a workflow via `npx hyperframes skills update <workflow-name>`; fails hard on error and prohibits reconstructing workflows from memory, enforcing the CLI as the single source of truth.
Before reading the selected workflow, install or refresh it and the core domain skills: ```bash npx hyperframes skills update <workflow-name> ``` Use the bare name without `/`. If the command fails, surface the error; do not reconstruct the workflow from memory.
Provides an on-demand domain skill loading table (composition structure → core, motion → animation, keyframes, creative, media-use, audio, cli, registry, figma) with a precise loading matrix for cross-domain requests like 'Creator edit phrases'; domain skills never assume ownership of end-to-end deliverables.
| zoom in here, punch-in / punch-out, smooth multi-state zoom or reframe, Ken Burns, or camera move | `/general-video` + `/hyperframes-core` + `/hyperframes-keyframes`; animate the inner visual/crop wrapper, not the timed clip. |
Integrates version discipline: checks for outdated pins upon resuming a project via a read-only probe (`npx hyperframes@latest upgrade --project . --check`), upgrades if outdated, and verifies using `npx hyperframes check`—the CLI version pin is owned by project package.json scripts and never drifts automatically.
A scaffolded project pins `hyperframes@<version>` in its `package.json` scripts so renders stay reproducible; the pin never advances on its own, and a pinned run of an older CLI prints no warning about it.
2Core Capabilities
3External Dependencies
| Kind | Dependency / Endpoint |
|---|---|
| cli | hyperframes CLI(skills update / upgrade --check / 项目内 npx hyperframes) |
| cli | media-use 的 prefs.mjs/recipe.mjs(意图层 step 1 读用户记忆/配方;intent-interview.md 指引) |
| network | (间接)npx 首次拉取 / skills update 与 GitHub 最新版比对 |
4Recommended Governance & Evidence
- scripts/: Execute local scripts or commands: node <MEDIA_DIR>/scripts/prefs.mjs get / recipe.mjs list (reads user preferences/recipes, read-only)
- 外部 API: Publish posts, create resources, or modify data on external platforms
- 环境变量 / API Key: Read vendor service API keys: intent layer reads user memory (prefs.mjs/recipe.mjs access project .media/preferences.json, recipes/, and ~/.me)
- 本地工作目录: File read/write and artifact output: writes BRIEF.md (interview deliverable, the sole routing artifact for workflows)
5Second-Pass Verification
- [ok] 『入口/路由』定位与 README/生态描述一致 — README.md:'Read `/hyperframes` first — it's the router and capability map';CLAUDE.md/AGENTS.md 亦把 hyperframes 列为入口(仓库级 grep 复核)。
- [ok] 八步访谈与 step 1 读记忆脚本调用 — intent-interview.md 原文 'Run `node <MEDIA_DIR>/scripts/prefs.mjs get --hyperframes <MEMORY_ROOT> --json`' 复核一致;prefs.mjs/recipe.mjs 存在于 media-use/scripts/。
- [ok] 是否有隐藏脚本/网络(纯文档声称) — find 实测 skills/hyperframes 仅 SKILL.md + references/(10 文件 + routes/ 9 文件),零可执行文件;URL 扫描零第三方域命中。
- [discrepancy] BRIEF.md 指令载体风险是否遗漏 — 首轮未单列『BRIEF.md 作为可信指令』的注入视角;二轮补充进 injection_surface:项目内既有 BRIEF.md 会被直接执行其 workflow/flow,来源不可信时属项目文件信任面。
- [ok] 工作流/域技能不越权承诺(end-to-end 归属) — SKILL.md 'Domain skills never take ownership of the end-to-end deliverable. Load only what the active workflow needs.' 与加载矩阵共存,职责边界自洽。
6Verdict & Scenarios
90b6328fc5285f0f…