ext/hyperframes
2
0
Fork 0
mirror of https://github.com/heygen-com/hyperframes.git synced 2026-09-14 00:00:17 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs(skills): surface Code Animations blocks to agents (#1485)

Browse Source 
The 9 Code Animation blocks shipped to the registry but were referenced
in zero agent-facing skills, so agents rebuilt code scenes from scratch
instead of installing them.

- discovery.md: add a Code Animations (9) section to the block inventory
  and fix the stale block count (88 -> 97)
- motion-graphics/catalog-map.md: add a code / code-reveal row to the
  Director -> block map
- pr-to-video visual-design: install code-diff / code-morph /
  code-highlight / code-typing / code-scroll before hand-authoring a code window
This commit is contained in:
Miguel Ángel
2026-06-16 01:25:22 -04:00
committed by GitHub
parent 36b24acf20
commit d595010388
3 changed files with 39 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files
skills/pr-to-video/agents/visual-design.md
+2
View File
@@ -13,6 +13,8 @@ You are the **faceless-explainer** Phase 3 / visual-design subagent. The full co
> **Output file shape (mandatory):** `section_plan.md` = an optional one-line H1 title + **one `## Film Direction` block** (film-level invariants written once — palette system, type roles, motion defaults + budget, ambient system, film negative list, transition vocabulary, asset coverage table, stillness allocation; guide §4.1) + `## Scene N:` blocks of **delta prose only** (≤150 words target; guide §4.2), **nothing else**. Film Direction IS read downstream (prep forwards it to every worker + finalize); any **other** preface — "Project-level system commitments" / cross-scene summary — is a validator fatal (guide §2 "Whole-file shape"). The litmus test for every scene sentence: could it appear verbatim in another scene? Yes → it belongs in Film Direction. (Per scene you apply the `voice.md` register to DOM text; keep that judgment in your head, not in the file.)
> **Code beats — reach for a Code Animation block first (mandatory):** this is a code-change film, so the **Code Animations** registry blocks are your primary vocabulary — before hand-authoring any code-window / diff / before-after / code panel, name the block whose motion matches the beat: a diff hunk → `code-diff`; a refactor (one state → another) → `code-morph`; spotlight a changed line → `code-highlight`; type the change on screen → `code-typing`; walk a long changed file → `code-scroll`; a hero/title code moment → `code-3d-extrude` / `code-shader-dissolve` / `code-particle-assemble`. The worker installs via `npx hyperframes add <block>` and customizes the baked code/diff content in place; hand-author a code panel only for a custom layout no block covers (side-by-side diff, file-tree + panel).
## Self-Validation
The `Schema validator:` provided by dispatch is an absolute path. After writing: