+**Capstone thread** — the [Level 7 film](/prompting/capstone) stretches this chapter's callback device across its whole runtime: the `` chip typed in the opening rides the wire through every region and finally snaps into the render slot as the payoff (0:56–1:02 below, cut from the film).
+
+
+
+
*Next: [Editing existing videos](/prompting/editing-existing-videos) — the editor verbs that turn a first render, storyboard or not, into the twenty edits after it.*
diff --git a/docs/prompting/transitions.mdx b/docs/prompting/transitions.mdx
index a77da8573..a48d185c3 100644
--- a/docs/prompting/transitions.mdx
+++ b/docs/prompting/transitions.mdx
@@ -90,4 +90,10 @@ Name the block and the seam — transitions are the one place where per-seam con
- ❌ `add a page-curl transition`
- ✅ pick a real block, e.g. `sdf-iris` for an iris reveal
+
+**Capstone thread** — the [Level 7 film](/prompting/capstone) allows itself exactly one shader seam: the camera pushes through an `sdf-iris` lens into the Surface region (0:38–0:45 below, cut from the film) with the timeline wire visible through the iris the whole way — a lens the journey passes through, not a cut.
+
+
+
+
*Next: [Code animations](/prompting/code-blocks) — naming a block and pasting real code for walkthroughs, diffs, and terminal takes.*
diff --git a/docs/prompting/variables-and-templating.mdx b/docs/prompting/variables-and-templating.mdx
index 676bd2a7d..bf00a04f7 100644
--- a/docs/prompting/variables-and-templating.mdx
+++ b/docs/prompting/variables-and-templating.mdx
@@ -86,4 +86,8 @@ If total length must differ per output, that's a different root `data-duration`
+
+**Capstone thread** — the [Level 7 film](/prompting/capstone) is a working template: one single-file composition, one variable scope, and its second render — navy ground, acid-green ink, every region re-skinned including the generated mural — is nothing but one `--variables` flag. Both full renders are embedded on the capstone page.
+
+
*Next: [Storyboards](/prompting/storyboards) — for multi-scene work, prompt the plan a frame-by-frame build fills in, not the scenes one by one.*
diff --git a/docs/prompting/vfx-and-liquid-glass.mdx b/docs/prompting/vfx-and-liquid-glass.mdx
index cefd4d5bc..6d93dc245 100644
--- a/docs/prompting/vfx-and-liquid-glass.mdx
+++ b/docs/prompting/vfx-and-liquid-glass.mdx
@@ -100,4 +100,10 @@ The Effects components above have none of this — they're plain CSS and animate
- [Copy-paste examples](/prompting/examples) — a `vfx-liquid-background` social-card prompt to adapt.
- [HTML-in-Canvas guide](/guides/html-in-canvas) — how `drawElementImage` works and the flag details.
+
+**Capstone thread** — the [Level 7 film](/prompting/capstone)'s Surface region floats its inspector panels on the brand's glass tokens — translucent white over real backdrop blur, the mural visibly smearing through each panel (0:38–0:45 below, cut from the film).
+
+
+
+
*Next: [Runtimes and 3D](/prompting/runtimes-and-3d) — picking GSAP, Three.js, or Lottie by what the moment actually needs, including the real depth these effects render on.*