mirror of
https://github.com/heygen-com/hyperframes.git
synced 2026-09-04 16:42:27 +00:00
docs(prompting): level 4 — capability chapters framed as additive
Add entry bridges (each naming a specific Level 1-3 artifact the capability slots into) and literal exit bridges across the 7 Level 4 Substance pages, per the novice-to-advanced restructure plan. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Sonnet 5
parent
2ab72e5d14
commit
cd8c98e92d
@@ -3,6 +3,8 @@ title: Runtimes and 3D
|
||||
description: "GSAP is the default and you rarely name it — but real 3D, existing animation files, and scene transitions each have a runtime worth pinning in the prompt."
|
||||
---
|
||||
|
||||
Level 2's copy-paste examples include an isometric-cards prompt that asks to "Build the scene in Three.js via the adapter" — this chapter is why that line is there, and the rest of the runtime map for when GSAP, the default, isn't the right tool.
|
||||
|
||||
HyperFrames animates through the [frame-adapter](/concepts/frame-adapters) pattern: any runtime that can answer "what should the screen look like at frame N?" plugs in and renders deterministically. [GSAP](/guides/gsap-animation) is the default adapter and covers most motion — you rarely need to name it. The cases below are the ones where the default choice can go wrong, so the prompt should pick the runtime for you.
|
||||
|
||||
## Real 3D → Three.js via the adapter
|
||||
@@ -81,3 +83,5 @@ The rule of thumb: anything the video needs to *know* must be present before ren
|
||||
Naming the scene-to-scene handoffs worth a shader transition.
|
||||
</Card>
|
||||
</CardGroup>
|
||||
|
||||
*Next: [Media and audio](/prompting/media-and-audio) — precise phrasing for voiceover, music, sound, and assets, instead of motion and rendering.*
|
||||
|
||||
Reference in New Issue
Block a user