Guide the user from idea to merged PR for a new registry block or component.
1. Clarify → 2. Scaffold → 3. Build → 4. Validate → 5. Preview → 6. Ship
Ask what they're building. The registry has two item types:
registry/blocks/, type hyperframes:block) — a full standalone composition with fixed dimensions and duration. Caption styles, VFX effects, title cards, lower thirds.registry/components/, type hyperframes:component) — a reusable snippet with no fixed dimensions or duration. CSS effects, text treatments, overlays that adapt to any composition size.Then ask:
Create the registry structure:
For blocks:
registry/blocks/{block-name}/
{block-name}.html
registry-item.json
For components:
registry/components/{component-name}/
{component-name}.html
registry-item.json
Naming convention:
| Item name | ID prefix | Example IDs |
|---|---|---|
| ---------------- | --------- | ---------------------- |
cap-hormozi | hz | hz-cg-0, hz-cw-3 |
cap-typewriter | tw | tw-cg-0, tw-ch-0-5 |
vfx-chrome | vc | vc-canvas |
Use a 2-3 letter prefix. ALL element IDs must use this prefix to avoid collisions in sub-compositions.
registry-item.json for blocks:
{
"$schema": "https://hyperframes.heygen.com/schema/registry-item.json",
"name": "{block-name}",
"type": "hyperframes:block",
"title": "{Human Title}",
"description": "{one sentence}",
"dimensions": { "width": 1920, "height": 1080 }, // adjust: 1080x1920 for portrait/social
"duration": 10, // adjust for your composition
"tags": ["{category}", "{subcategory}"],
"files": [
{
"path": "{block-name}.html",
"target": "compositions/{block-name}.html",
"type": "hyperframes:composition"
}
]
}
registry-item.json for components (no dimensions or duration):
{
"$schema": "https://hyperframes.heygen.com/schema/registry-item.json",
"name": "{component-name}",
"type": "hyperframes:component",
"title": "{Human Title}",
"description": "{one sentence}",
"tags": ["{category}"],
"files": [
{
"path": "{component-name}.html",
"target": "compositions/components/{component-name}.html",
"type": "hyperframes:snippet"
}
]
}
Apply the correct template based on type. See templates.md for copy-paste starters.
Non-negotiable caption rules:
-webkit-text-stroke: 2-3px OR multi-layer text-shadowwindow.__hyperframes.fitTextFontSize() on every grouptl.to(wordEl, { color/scale }, WORDS[wi].start)tl.set(groupEl, { opacity: 0, visibility: "hidden" }, g.end) on EVERY grouptl.from(el, { opacity: 0 }) at the same position as tl.set(el, { opacity: 1 }) — the from clobbers the set. Use tl.to instead.Per-character animation (typewriter, scramble):
with ID {prefix}-ch-{group}-{char}tl.set at computed intervals from word timestampstl.set at intervals — NOT CSS animation (not seekable)Positioning variants:
display: flex; align-items: center; justify-content: center;position: absolute; bottom: 100px; left: 0; width: 100%; text-align: center;position: absolute; bottom: 100px; left: 120px; text-align: left;three@0.147.0 from CDN (global script)tl.eventCallback("onUpdate", renderScene); renderScene(); — NO requestAnimationFramemulberry32) for randomnessdata-composition-id MUST match window.__timelines["id"]gsap.timeline({ paused: true }) — always pausedMath.random(), no Date.now()hyperframes lint # 0 errors required
hyperframes validate --no-contrast # 0 console errors required
# Render preview video
hyperframes render -o preview.mp4
# Snapshot for visual QA
hyperframes snapshot --at "1.0,3.0,5.0,7.0"
# Publish to hyperframes.dev for review
npx hyperframes publish
Catalog preview image — The catalog card uses a PNG at docs/images/catalog/{kind}/{name}.png (where {kind} is blocks or components). Generate it from a snapshot, then:
scripts/upload-docs-images.sh (requires AWS profile engineering-767398024897)All steps are required. Missing any one produces a broken catalog entry.
{kind} is blocks or components depending on what you built in Step 1.
# 1. Create branch
git checkout -b feat/registry-{name}
# 2. Format HTML
npx oxfmt registry/{kind}/{name}/*.html
# 3. Update registry/registry.json — add entry to the "items" array:
# { "name": "{name}", "type": "hyperframes:block" } (or "hyperframes:component")
# 4. Generate catalog docs page
npx tsx scripts/generate-catalog-pages.ts
# 5. Publish to hyperframes.dev so reviewers can preview
npx hyperframes publish
# 6. Stage everything
git add registry/{kind}/{name}/ registry/registry.json docs/catalog/
# 7. Commit
git commit -m "feat(registry): add {name} — {one sentence}"
# 8. Push and open PR with hyperframes.dev link
git push origin feat/registry-{name}
gh pr create --title "feat(registry): {name}" --body "preview: {hyperframes.dev-url}"
If you don't have a GitHub account: you need one to open a PR. Sign up at https://github.com/signup, then run gh auth login.
hyperframes lint → 0 errorshyperframes validate → 0 console errorsnpx oxfmt --check passesregistry/registry.json updated with new entryscripts/generate-catalog-pages.ts run (docs page generated)npx hyperframes publish run (claim your project URL)共 1 个版本