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

fix(skills): align core contract with check (#2218)

Browse Source
This commit is contained in:
Miguel Ángel
2026-07-10 21:37:35 -04:00
committed by GitHub
parent 469cfb3a32
commit de4e85add6
5 changed files with 31 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
skills/hyperframes-core/SKILL.md
+1 -3
View File
@@ -72,9 +72,7 @@ Surfaced here; full rationale in the linked reference. Do not violate:
Use `hyperframes-cli` for command details
- [ ] `npx hyperframes lint` passes (0 errors)
- [ ] `npx hyperframes check` passes (0 console errors)
- [ ] `npx hyperframes check` passes (0 errors)
- [ ] `npx hyperframes check` passes (0 findings across lint, runtime, layout, motion, and contrast)
- [ ] Projects with sub-compositions: `npx hyperframes snapshot --at <midpoints>` and eyeball each frame
- [ ] `npx hyperframes preview` for review (the user can edit anything in Studio's timeline)
- [ ] `npx hyperframes render` only after the user approves
skills/hyperframes-core/references/brief-contract.md
+1 -1
View File
@@ -17,7 +17,7 @@ There are two modes. Default: **collaborative**.
1. **Preference gates** (which preset, voice, caption identity, want a preview?) — autonomous: decide yourself and state the decision with a one-line reason. Never stay silent.
2. **Checkpoint gates** (storyboard approval, pre-render review) — autonomous: post the same summary you would have asked about as an inline heads-up, then continue. One exception: before rendering, ask once — preview first, or render (§ 3).
3. **Quality gates** (`lint` / `validate` / `inspect`, capture completeness, fetch failures, workflow-specific verification checklists) — never skip these in any mode. Errors still stop the run. Reasoning like "autonomous means bias toward action, so I'll skip verification" misuses the mode — bias toward action applies to deciding _what to build_, not _whether to verify_.
3. **Quality gates** (`hyperframes check`, capture completeness, fetch failures, workflow-specific verification checklists) — never skip these in any mode. Errors still stop the run. Reasoning like "autonomous means bias toward action, so I'll skip verification" misuses the mode — bias toward action applies to deciding _what to build_, not _whether to verify_.
4. **Routing and sign-in decisions** — wrong routing is a quality problem: an ambiguous-intent confirmation, such as `/slideshow`'s "is this a deck?", still happens in autonomous mode. Auth sign-in follows `/media-use` → Preflight: show the status as-is; collaborative waits for the user's choice, while autonomous notes it and continues offline.
**Autonomous is not silent.** Every question absorbed by the mode becomes a decision with a receipt — state the choice and its one-line reason inline as you go. Final delivery always includes the contact sheet, so review happens after the fact instead of not happening at all.
skills/hyperframes-core/references/minimal-composition.md
+2 -1
View File
@@ -39,6 +39,7 @@ The smallest renderable HyperFrames composition — a standalone (top-level) roo
<div
id="root"
data-composition-id="main"
data-start="0"
data-width="1920"
data-height="1080"
data-duration="5"
@@ -59,7 +60,7 @@ The smallest renderable HyperFrames composition — a standalone (top-level) roo
Required elements:
- Root `<div>` with `data-composition-id`, `data-width`, `data-height`, `data-duration`
- Root `<div>` with `data-composition-id`, `data-start="0"`, `data-width`, `data-height`, `data-duration`
- At least one clip (any element with `data-start`, `data-duration`, `data-track-index`)
- GSAP timeline created paused, registered on `window.__timelines["<composition-id>"]`