mirror of
https://github.com/heygen-com/hyperframes.git
synced 2026-11-19 11:26:02 +00:00
* feat(skills): every published skill reports its own run `hyperframes events --skill=<name>` exists so a skill can say it ran, but only reverse-any-video and figma asked the agent to call it, so the other skills' use was invisible. Each of the nine published skills now opens with a one-line usage beacon naming itself. The line says what it sends (the skill's name only) and that the telemetry opt-out applies. The router's `init` line also passes `--skill=hyperframes`, so renders of new projects carry the skill. check-core-skills fails a core skill that lacks its own beacon; each core skill's size budget grows by 192 B for the line. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(skills): say the usage beacon goes out with the CLI's usual telemetry The beacon line said it sends only the skill's name. The events command uses the CLI's normal telemetry, which also carries machine details, the install id and, when signed in, the account. The line now says so. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
5.0 KiB
5.0 KiB
name, description
| name | description |
|---|---|
| slideshow | Build a HyperFrames slideshow to present live - slides, fragment reveals, branching hotspots and presenter mode with speaker notes, served by `hyperframes present` - or turn an existing page into one. Use when the person wants a deck or presentation rather than a rendered video. |
Plugin installs: Inside a HyperFrames plugin, follow plugin execution rules.
Usage beacon: run npx hyperframes events --skill=slideshow once as this skill starts. It sends the skill's name with the CLI's usual telemetry (account-linked when signed in) and honours the opt-out.
HyperFrames slideshow
A slideshow is a normal composition (the /hyperframes contract applies) plus one JSON island that says which scenes are slides and how they connect. The deliverable is a running deck, not an MP4.
What changes from a video project
- Each slide is a top-level scene in the composition file:
data-composition-id,data-start,data-duration,data-label,data-width,data-height. There is no master root composition wrapping them. - One island per composition, near the top of
<body>, written in the HTML (never generated by script;presentreads the file statically):
<script type="application/hyperframes-slideshow+json">
{
"slides": [
{ "sceneId": "hook", "notes": "Pause on the number." },
{
"sceneId": "problem",
"fragments": [11.0, 15.0],
"hotspots": [
{
"id": "h1",
"label": "Where does $40B come from?",
"target": "market-detail",
"region": { "x": 55, "y": 60, "w": 40, "h": 20 }
}
]
}
],
"slideSequences": [
{ "id": "market-detail", "label": "Market sizing", "slides": [{ "sceneId": "mkt-math" }] }
]
}
</script>
sceneIdequals a scene'sdata-composition-id(or givestartTime/endTime).notesare presenter-only.ttsScript,ttsAudioUrlandttsDurationMsare reserved and not wired yet.- Fragments are absolute timeline times (the same clock as
data-start, not offsets inside the slide) within the slide's[start, end]. Navigation seeks, it never plays: each hold state must look right when the timeline is seeked straight to that time. A slide without fragments enters at a rest frame inside it. - Branch slides are ordinary scenes listed only in
slideSequences, never in the mainslidesarray. A hotspot'stargetis a sequenceid;regionis a percentage box (omit it for a full-slide button). Back returns to the slide that held the hotspot. - Text the audience must read is at least 40 px at 1920×1080. Before hand-building any named visual, search
npx hyperframes catalog --query "<the visual, in English>" --json: it ranks the whole registry with nothing installed.
Porting an existing page
- Keep the source's look, motion, interactions and media behaviour; port its widgets, players and visualizers rather than approximating them.
- Movement the page drove by scroll, wheel or a camera layer becomes a camera move from one focal point to the next on slide navigation, never a page visibly scrolling. Keep each move direct, without reversals the source doesn't make.
- Screenshots, posts, charts, code and any image with readable text are evidence: keep their aspect (
object-fit: contain) and check all four edges for crops. - Every copied
<video>/<audio>needsdata-startanddata-duration(data-has-audio="true"when its sound plays), and nopreload="none". Custom media chrome reads the native element's events andcurrentTime, never its own timer. - Hidden stacked slides need
opacity: 0,visibility: hiddenandpointer-events: nonetogether, or an invisible layer swallows clicks.
Present and hand off
- Never render a deck to MP4:
renderkeeps only the first scene and truncates silently. For stills,snapshot --ateach slide. - Run
npx hyperframes check --jsonuntil it is clean. The slideshow rule checks that everysceneIdresolves, every hotspottargetexists, fragments sit inside their slide, and main-line slides don't overlap. - Serve it with
npx hyperframes present <project-dir>and hand over the URL it prints: "Click Present, or press P, to open the audience tab." - The project's root
index.htmlshould open as a working deck:<hyperframes-slideshow>around<hyperframes-player src="…">, with the raw composition in a subfolder if needed. The component owns Present (P), Prev/Next, the counter, global mute, fullscreen, swipe, hotspots, presenter notes (editable, kept per deck) and stopping media on slide exit. Don't build your own versions of any of these. - Screen sharing: in Google Meet share the audience tab, which keeps rendering in the background. In Zoom drag the audience tab into its own window and share that; a fully covered window freezes.
- A deck opened from the bare player bundle without
presentneeds workarounds:references/standalone-harness.md.