Skip to content

armgit / hypit

Public Imported from GitHub
0

Clone any viral video with AI agents. Not just a script, the whole workflow: swap the face, the words, the B-roll, ship 100 variants in one command, and get your 100M views.

docs: remove stale package source-reading guidance

rpone48b92a18e545
diff --git a/.agents/skills/hypit/references/local-author-package.md b/.agents/skills/hypit/references/local-author-package.md
index 49c57800..89951d5e 100644
--- a/.agents/skills/hypit/references/local-author-package.md
+++ b/.agents/skills/hypit/references/local-author-package.md
@@ -129,10 +129,9 @@ only Studio interpretation and operations through `hypit.studio-adapter@1`; it n
`packages/studio`, and the author package never imports Studio. A generic block is valid while no
special interpretation is needed.
-Know what that fallback gives it, because it is enough for a lot of packages. The `visual-track` rule
-in `packages/studio-video-adapters/src/generic.ts` declares no module filter, and a rule that
-declares none matches whatever the module is, so a project-local Track producing a `VisualTrack`
-lands there and gets `role: "track"`. Studio draws it in a flat media lane and exposes five timing
+Know what that fallback gives it, because it is enough for a lot of packages. A project-local Track
+producing a `VisualTrack` lands in the generic `role: "track"` lane when no companion claims the
+Module. Studio draws it in a flat media lane and exposes five timing
parameters — `start`, `end` and `for` writable, `during` and `at` read-only — over a read-only
interaction: the block can be selected and seeked, not dragged or trimmed. A companion package is
what buys anything past that: parameters named for what the component actually has, child entities,
diff --git a/.agents/skills/hypit/references/playbooks/craft/captions.md b/.agents/skills/hypit/references/playbooks/craft/captions.md
index ca342f14..f1239d7f 100644
--- a/.agents/skills/hypit/references/playbooks/craft/captions.md
+++ b/.agents/skills/hypit/references/playbooks/craft/captions.md
@@ -91,7 +91,7 @@ property, since the Style admits exactly the required keys plus the documented o
A Recipe holds no rule for where one Cue ends and the next begins. **The Script does**, as a `||`
between two complete Alignment Units — `docs/quickstart/script.md` is authoritative for it, and
-`packages/script/src/parser.ts` reads it into the breaks the Caption Document carries.
+the Script parser carries those breaks into the Caption Document.
```
<PRESENTER> It's generally good || at a lot of || different things, ||
diff --git a/docs/guide/author-packages.md b/docs/guide/author-packages.md
index d2f66948..79160548 100644
--- a/docs/guide/author-packages.md
+++ b/docs/guide/author-packages.md
@@ -111,8 +111,8 @@ export const decodeMyComponentSurface: StructuredSurfaceHandler = ({ element, re
};
```
-[Component Anatomy](./component-anatomy.md) names every role a component package fills and where to
-find each one in an existing package, since the filenames differ between packages.
+[Component Anatomy](./component-anatomy.md) names every role a component package fills and points to
+the minimal fixture's corresponding role, so a new package does not need to inspect a business package.
For a generic package, use the complete fixture at
`examples/minimal-author-package/packages/example-component/` rather than copying an unrelated
diff --git a/docs/guide/component-anatomy.md b/docs/guide/component-anatomy.md
index c3887607..b5b340fe 100644
--- a/docs/guide/component-anatomy.md
+++ b/docs/guide/component-anatomy.md
@@ -1,12 +1,12 @@
---
title: Component Anatomy
-description: The roles a component package fills, and how to find them in an existing package.
+description: The roles a component package fills, illustrated by the minimal author-package fixture.
---
# Component Anatomy
-Every component package fills the same set of roles. The filenames differ from package to package, so
-find a role by what it exports, not by what its file is called. This page describes the roles;
+Every component package fills the same set of roles. This page describes the roles and their
+canonical fixture locations;
[Adding an Author Package](./author-packages.md) is the step-by-step.
Read this instead of reading a neighbouring package end to end. One package's specifics are a worse
diff --git a/docs/zh/guide/author-packages.md b/docs/zh/guide/author-packages.md
index b7ff5613..a186209e 100644
--- a/docs/zh/guide/author-packages.md
+++ b/docs/zh/guide/author-packages.md
@@ -87,10 +87,11 @@ export const decodeMyComponentSurface: StructuredSurfaceHandler = ({ element })
};
```
-可以参考已有的 Surface 实现:
-- `packages/seedance/src/surface.ts` —— Prompt、Speech 和 Video Surface
-- `packages/caption/src/surface.ts` —— 公共 Program Surface;具体 Style/Track Surface 属于各样式族包
-- `packages/media-track/src/surface.ts` —— Track、Item 和 Sequence Surface
+通用包不要从业务包源码推断写法。使用仓库内的最小完整 fixture:
+`examples/minimal-author-package/packages/example-component/`。它包含完整的
+Surface 返回值、Fragment literal、Manifest ports、Producer 和 activation 形状。
+只有 `inspect_svml_vocabulary` 已证明存在高度相似的结构性 sibling 时,才允许读取该
+sibling 的 README 和实现所需的少数 role 文件,并将其复制为新的 Module;不得比较无关业务包。
## 5. 声明 Surface 词表与预览图
@@ -124,13 +125,16 @@ vocabulary: {
`appearance` 和 `preview` 回答的是两个不同的问题,谁都替代不了谁:`appearance` 说的是这个元素在所有情况下都会画出什么,预览图给出的是其中一个诚实的实例。
-完整词表可研究 `packages/media-track/src/manifest.ts`;`preview/` 目录可参考 `packages/typography-track/`、`packages/caption-fine/`、`packages/deck-track/`、`packages/comment-sticker/`、`packages/screen-overlay/`、`packages/ranking/` 和 `packages/speech-track/`。
+完整词表和预览声明以最小 fixture 为权威示例。生产路线应使用
+`hypit-reference-video-tools inspect_svml_vocabulary` 读取已安装包的公开声明,
+而不是打开业务包源码。
### 预览图怎么产出
预览图是你自己这个组件在本地渲染出来的真实一帧。没有任何工具会替你生成它,而手工画的示意图比没有预览图更糟,因为它冒充了真实产出。
-按仓库自身视觉测试的做法渲染即可 —— `packages/hyperframes/test/browser-visual.test.ts` 就是可运行的示例,步骤是:
+用 `hypit-reference-video-tools render_previews` 渲染 fixture 的 preview Source;新包沿用同一套
+package-owned preview Source,不需要阅读仓库的视觉测试源码。步骤是:
1. 用你自己包的 render 函数,在一个封好的 ProgramSpace 上构造出 Track 值;
2. `sealComposition({ id, canvas, tracks })`,再用 `@hypit/hyperframes` 的 `compileHyperframesDocument(composition, space)`;
@@ -204,14 +208,11 @@ pnpm install --frozen-lockfile
`<import>` 只会 activate 作者词汇。它绝不授予网络、文件系统或凭据权限。
-## 可供研究的现有示例
-
-| 包 | 它展示了什么 |
-|---|---|
-| `packages/seedance/` | 带多个 Surface(Prompt、Speech、Video)的模型族 |
-| `packages/seedance-speaker/` | 组合 Script、Text Template 和 Seedance 的更高层绑定 |
-| `packages/caption/` | 公共 Program、Cue/字段合同和整 Atom 定时 |
-| `packages/caption-fine/` | 一种无字段的 Style 与 Track Surface 样式族 |
-| `packages/media-track/` | 带 Item/Sequence、图层、动效和交接行为的 Track |
-| `packages/typography-track/` | Typography 叠加 Track |
-| `packages/film/` | 消费同级 Track 的合成 target |
+## 实现分流
+
+没有高度相似 sibling 时,只读规范文档、已安装包的 vocabulary 输出和
+`examples/minimal-author-package/packages/example-component/` fixture。
+
+当 vocabulary 证明输入/输出 Type、timing contract、终端 Track 和 Surface ports 高度相似,
+才可走 close-sibling 路径:读取该 sibling 的 README 与必要 role 文件,复制结构,重建
+Module/Producer identity,并继续通过 package-ready、Source-use、preview 和最终 gate。