From 2ab72e5d14c59d9d24190ab25806204df7bf047f Mon Sep 17 00:00:00 2001 From: Vance Ingalls Date: Wed, 22 Jul 2026 12:28:29 -0700 Subject: [PATCH] =?UTF-8?q?docs(prompting):=20level=203=20=E2=80=94=20life?= =?UTF-8?q?=20chapters=20with=20bridges?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- docs/prompting/motion.mdx | 4 +++- docs/prompting/transitions.mdx | 4 ++++ 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/docs/prompting/motion.mdx b/docs/prompting/motion.mdx index fd21d217ea..635d5f3ee1 100644 --- a/docs/prompting/motion.mdx +++ b/docs/prompting/motion.mdx @@ -3,7 +3,7 @@ title: Motion that reads premium description: "Seven motion-grammar rules from frame-by-frame study of professional work — nothing stops, the camera acts, action overlaps, imperfection stays reproducible." --- -Static frames can be perfect and the video still feels cheap if the motion is dead. Professional motion design follows a grammar you can put directly in prompts: +By now you can specify a frame precisely — exact copy, exact colors, exact layout, exact timing. This level makes it feel alive. Static frames can be perfect and the video still feels cheap if the motion is dead. Professional motion design follows a grammar you can put directly in prompts: 1. **Nothing ever fully stops.** Every "hold" carries ambient idle motion — a 1-2% breathing scale, slow drift, a shimmer. Never write "holds motionless"; write "settles into a gentle ambient idle." A frozen final second is the single biggest cheap-motion tell. 2. **The camera is an actor.** Give each scene one continuous camera move — a 4-8% push-in, a slow orbit, parallax between layered planes — easing gently but never settling on screen (compute the ease over a window slightly longer than the render). @@ -32,3 +32,5 @@ Rule 1's ambient idle is *continuous* — a slow, smooth breathing scale. Rule 7 > A paper-cutout garden scene: flowers, leaves, and a bee drifting on visible wires, like stop-motion. Seed a random offset per element at the start (same seed every render) so each leaf sways to a slightly different rhythm, but hold each position for exactly two frames before stepping to the next — discrete jumps, not a smooth tween. It should read as intentionally handmade, not glitchy. Name the seed and the hold length explicitly — "seeded" and "two-frame hold" are the two words that keep an agent from reaching for `Math.random()` and quietly breaking every re-render. Ask for it, and seeking to frame 214 twice gives you the identical frame twice, exactly like every other HyperFrames render — the imperfection is designed in, not left to chance. + +*Next: [Transitions](/prompting/transitions) — the same grammar applied to the cut between scenes, not just the motion inside one.* diff --git a/docs/prompting/transitions.mdx b/docs/prompting/transitions.mdx index d7cd49449d..a77da8573a 100644 --- a/docs/prompting/transitions.mdx +++ b/docs/prompting/transitions.mdx @@ -3,6 +3,8 @@ title: Transitions description: "Map energy and mood to named shader and CSS transition blocks, and prompt them per seam." --- +[Motion](/prompting/motion)'s seven rules were written for what happens inside one scene. Rule 2's camera and rule 3's overlap apply *between* scenes too — a transition is that same grammar aimed at the cut itself, not a separate feature to bolt on afterward. + ## What transitions do and when they trigger A transition tells the viewer how two scenes relate — a crossfade says "this continues," a whip pan says "next point," a burn says "something changed." Any composition with more than one scene needs them: without a transition, a scene change reads as an unintentional jump cut (see [rules and anti-patterns](/prompting/rules-and-anti-patterns)). The skills add transitions by default, so prompts trigger this layer whenever you describe scene changes, crossfades, wipes, reveals, or a mood ("warm," "clinical," "glitchy") — or when you name a block directly. @@ -87,3 +89,5 @@ Name the block and the seam — transitions are the one place where per-seam con **Don't invent transition names.** Only the blocks in the [shader](/catalog/blocks/cross-warp-morph) and CSS transition groups exist; a made-up name (`page-curl`, `star-iris`) sends the agent guessing at raw GLSL or an unsupported CSS effect. - ❌ `add a page-curl transition` - ✅ pick a real block, e.g. `sdf-iris` for an iris reveal + +*Next: [Code animations](/prompting/code-blocks) — naming a block and pasting real code for walkthroughs, diffs, and terminal takes.*