Diorama slides
A short video in one mode: a card layer that holds still for the whole
video (the kicker, the headline with its figure, the units,
the source footer, words swapping from beat to beat), drawn over a living
stage, a toy-like 2.5D diorama where the story's things change and move.
It sits between slides and a film: the card reads like a slide, the stage
never stops. One standalone HTML page plays it, exports it as MP4 (or WebM)
in the browser that opens it, saves stills, and copies the caption and alt
text. JavaScript only: Canvas 2D, WebCodecs, Web Audio. No ffmpeg,
Remotion, WebGL, render pipeline, text-to-speech, AI image or video
generator, GSAP or CDN library, stock footage or music.
<skill-dir> below is the directory holding this file
(${CLAUDE_SKILL_DIR} where the agent expands it). Resolve templates/,
references/, scripts/ and assets/ against it, never against the working
directory.
The product is the story's shape and the edit, not the renderer. You
decide what shape the story has (one thing changing, a cast compared, a
thing built, places visited, a route travelled), then write a spec: the
stage, the beats, the copy, a claims ledger. The engine plays it. Every
thing on the stage you draw yourself, for this video, from the source's
own nouns.
Rules that hold on every video
- Never invent a figure that reads as a measurement. Every number on
screen is a ledger claim with a source and a locator, or is labelled
illustrative on screen. A topic with no source gets illustrative
figures and says so in the frame and in chat, or you ask for a source.
Never fetch figures from the web unless the user asks and names or
accepts the source.
- Keep the source's certainty. Hedges survive the edit (could, up to,
estimated, projected, about, according to, alleged). A forecast is
labelled a forecast. Shortening never upgrades: no will, record,
first or best the source doesn't say.
- No cause the source doesn't state. Not on screen, not in the
caption, not in the order of beats, not in what the stage shows happening
next to what, and not in chat as a "likely" reason.
- Quotes are verbatim and attributed; a cut is marked
….
- Real things only when the source names them. A car model, a building
or a brand the source mentions may be shown as that thing; anything it
doesn't mention is generic, or a fictitious name. A logo comes only from
a file the user or the source supplies, never drawn from memory; without
one, the brand's name is set as text. Real people are never drawn as
likenesses, only as generic figures (
references/stage.md § Real things).
- Sensitive topics stay neutral and non-graphic. War, disaster,
illness: no gore, no glorifying framing; tactics are movement and
formations, never casualties (
references/stage.md § Sensitive topics).
- One idea per beat; the card states it, the world makes it happen. At most
one figure or one flat chart in the card. Values are flat charts, never
3D charts, and a share is never a grid of boxes. The video works
muted: the words on screen are the script.
- Everything is readable before it moves on. The engine holds each
text layer for max(1.2 s, 0.5 s + 0.25 s/word), a figure 1.5 s after it
lands. Never set a
dur below a beat's minimum.
- The camera has one angle. It pans and zooms on the world only; the
card and every word above or below the stage never zoom or move. One
transition for the words, every time.
- Every cut ends on a source card: each source with its date, and
"illustrative" when any figure is.
- Deterministic and offline; never post. Every frame is a pure
function of
t; one standalone file; finalize.js's exit code is the
gate. The user posts, never you.
Workflow
Read the source and build the claims ledger. Read
references/copy.md. Pull every figure and quote that could appear on
screen into claims, with verbatim, locator, kind (copied, derived
with working, or illustrative), and any hedge or forecast. List the
findings, one sentence each with its number. Note every noun the source
names that could be drawn (the things, their parts, their places).
Settle format and length, asking at most two questions. Read
references/formats.md. Ask only what changes the build: where it will
play (if unstated), and which finding leads (only when two are equally
strong and the user picked neither). Defaults: 9:16, about 30–45 s,
preset default. Never ask about style, colour, fonts or transitions.
Name the point, direct each insight, then the shape and the beats.
Read references/story.md. Write the video's point with its main figure,
and what a viewer must see happen to get it with the sound off. Then
decide the world: where the story naturally happens, how that place
behaves on its own (planets orbit, a herd grazes, a shop opens), and how
it looks (stage.setting, stage.look). Never a default board. Then,
for each insight, ask what it is a fact about and what you would see
happen in the world if it happened in front of you; think of three
actions and keep the one most specific to this source. That becomes the
beat's stage.shows. Then the shape that holds the world together:
transformation (one subject that changes), lineup (a cast
compared), assembly (a thing coming into being), episodes (a
place per item) or journey (a route on a schematic map). The shape
guides layout and framing; it never decides what happens. Then the
beats on the spine (hook → the middle → source card), about one per
3–6 s, and what you leave out.
Write the world. Read references/stage.md (the world painter, what
the engine gives it: each beat's progress, the story's clock, running
totals, the claims, the camera), references/design.md for the look and
references/motion.md for how the card and the stage each move. You draw
every thing from the source's nouns, in its natural colours and with real
volume (living things are lofted bodies, never cut-outs), and make each
beat's shows happen by its progress, its time or its rate. Each thing
the story is about is a hero, drawn so it can't be mistaken for its
nearest lookalike: its telling features pushed and posed toward the
camera. There is no library of things or
behaviours, on purpose. A value with nothing to act out gets a flat chart
in the card (references/video-charts.md) while the world keeps living.
Copy the template and write the spec. Copy
<skill-dir>/templates/video.html to ./<slug>.html (or where the user
asked) and leave its charts-lib/… and motion-lib/… script tags
exactly as written; step 8 folds them in. Read references/engine-api.md
and write the whole spec: stage (shape, world, size, the clock's start),
each beat's copy and stage directions; every figure in copy is a claim
id ("F1" or {F1}), never typed digits. Fill the caption, the alt text,
the page's <title>, heading and lede.
Then build it in stages, cheapest check first: stage
(finalize.js --stage) and run check-video.js until no FAIL, with no
browser. Then write the world a beat at a time, the hook's first
one: look at one beat's still, fix it, then the next
(references/verify-and-ship.md § Build in stages).
Sound only if asked. Read references/audio.md before turning
meta.audio.score on.
Verify before reporting done. Read references/verify-and-ship.md
and follow it in full: node <skill-dir>/scripts/check-video.js <slug>.html with no FAIL; in a browser, VideoAudit.run on every cut
with exportProbe: true until each is ok; show each hero alone to a
fresh reader who hasn't been told the topic and fix what they can't
name (the cold read; with no fresh reader, the joint check, and say
so); look at the contact sheet as
an illustrator would against stage.look, and keep going while it reads
as a board, cut-outs or greys;
re-read every figure and hedge against the source. Without a browser,
the static check and the re-read are the floor, and you say the frames
weren't checked.
Ship one file: node <skill-dir>/scripts/finalize.js <slug>.html.
A non-zero exit means you are not done. Where Node may be missing, use
sh <skill-dir>/scripts/finalize.sh (or finalize.ps1 on Windows); it
prints UNCHECKED when it couldn't run the checks, and you say so.
Output
One HTML file, standalone. Surface it however your environment does (in
Claude Code: SendUserFile with display: "render"), otherwise print its
absolute path. Make an MP4 on disk only if you can drive a browser and the
user agrees to the download (verify-and-ship.md § An MP4 on disk).
Then the handover in chat, short:
- How to use it: open in Chrome or Edge; Play, scrub, ←/→ to step
frames; Export video saves the MP4; Export stills saves a poster
and a contact sheet; Copy caption and Copy alt text. Say which
export path the probe found.
- The story's shape, and each cut's beats with
V handles, timecodes, the
figures each shows and their locators; which things on the stage are
drawn as named in the source and which are generic; what was left out;
which figures are from the source and which are illustrative; whether
sound is on.
- Nothing was posted.
- The closing line, last, nothing after it (
references/tracing.md §
Handles and the closing line):
Ask "where does V3.1 come from?" or "why is S1 drawn like that?" to see the working behind any figure or picture.
Handles are for chat only: never in the video, the caption or the alt
text.
Tracing
The video puts figures and pictures in public under the user's name. Read
references/tracing.md before answering any follow-up about a figure, a
word, a picture on the stage or a choice. It carries the handles (V1…,
V3.1, [A], V5.h, S2 for a thing on the stage), the trace block
(From your source · Working · Where it appears · What would change it),
the picture block, the choice block and the wording block. A trace
re-reads the source and corrects the video when it's wrong (spec, every
cut, caption, alt text, then steps 7–8 again). Pushback alone moves nothing.
Environment notes
Nothing here needs a specific agent or vendor: file reads from this
directory, writing an HTML file, and Node for the scripts and checks. A
browser (a built-in pane, or headless Chrome or Edge) runs the audit and
the export probe when one is available. The user's export runs in their
own Chrome or Edge, which encode H.264; other browsers fall back to WebM
or a real-time recording, and the page says which path ran.
1---2name: diorama-slides3description: Turn an article, report, history, notes or a table into a short video where a still card of words sits over a living 2.5D diorama world that acts out each insight, drawn from the source's own nouns — whether the story is one thing changing, a cast compared, a thing being built, a place per episode or a route on a schematic map — 15–60 s (lineups and journeys to 90 s), 9:16, 4:5, 1:1 or 16:9, in the same design system as chart-dashboard, with every figure and hedge faithful to the source and a dated source card. One standalone HTML file that plays and exports MP4 in the browser. Use for "make a video where the thing itself changes / evolves / is built / travels". Not for slide-style explainers with charts (explainer-video) or a cinematic 3D film (documentary-video). No other apps, no CDN, works offline; never posts.4metadata:5 source: https://skillmd.com/skills/raghuramsirigiri/diorama-slides6---78# Diorama slides910A short video in one mode: a **card layer** that holds still for the whole11video (the kicker, the headline with its figure, the units,12the source footer, words swapping from beat to beat), drawn over a living13**stage**, a toy-like 2.5D diorama where the story's things change and move.14It sits between slides and a film: the card reads like a slide, the stage15never stops. One standalone HTML page plays it, exports it as MP4 (or WebM)16in the browser that opens it, saves stills, and copies the caption and alt17text. **JavaScript only**: Canvas 2D, WebCodecs, Web Audio. No ffmpeg,18Remotion, WebGL, render pipeline, text-to-speech, AI image or video19generator, GSAP or CDN library, stock footage or music.2021`<skill-dir>` below is the directory holding this file22(`${CLAUDE_SKILL_DIR}` where the agent expands it). Resolve `templates/`,23`references/`, `scripts/` and `assets/` against it, never against the working24directory.2526**The product is the story's shape and the edit, not the renderer.** You27decide what shape the story has (one thing changing, a cast compared, a28thing built, places visited, a route travelled), then write a spec: the29stage, the beats, the copy, a claims ledger. The engine plays it. Every30thing on the stage you draw yourself, for this video, from the source's31own nouns.3233## Rules that hold on every video34351. **Never invent a figure that reads as a measurement.** Every number on36 screen is a ledger claim with a source and a locator, or is labelled37 *illustrative* on screen. A topic with no source gets illustrative38 figures and says so in the frame and in chat, or you ask for a source.39 Never fetch figures from the web unless the user asks and names or40 accepts the source.412. **Keep the source's certainty.** Hedges survive the edit (*could, up to,42 estimated, projected, about, according to, alleged*). A forecast is43 labelled a forecast. Shortening never upgrades: no *will*, *record*,44 *first* or *best* the source doesn't say.453. **No cause the source doesn't state.** Not on screen, not in the46 caption, not in the order of beats, not in what the stage shows happening47 next to what, and not in chat as a "likely" reason.484. **Quotes are verbatim and attributed**; a cut is marked `…`.495. **Real things only when the source names them.** A car model, a building50 or a brand the source mentions may be shown as that thing; anything it51 doesn't mention is generic, or a fictitious name. A logo comes only from52 a file the user or the source supplies, never drawn from memory; without53 one, the brand's name is set as text. Real people are never drawn as54 likenesses, only as generic figures (`references/stage.md` § Real things).556. **Sensitive topics stay neutral and non-graphic.** War, disaster,56 illness: no gore, no glorifying framing; tactics are movement and57 formations, never casualties (`references/stage.md` § Sensitive topics).587. **One idea per beat; the card states it, the world makes it happen.** At most59 one figure or one flat chart in the card. Values are flat charts, never60 3D charts, and a share is never a grid of boxes. The video works61 **muted**: the words on screen are the script.628. **Everything is readable before it moves on.** The engine holds each63 text layer for max(1.2 s, 0.5 s + 0.25 s/word), a figure 1.5 s after it64 lands. Never set a `dur` below a beat's minimum.659. **The camera has one angle.** It pans and zooms on the world only; the66 card and every word above or below the stage never zoom or move. One67 transition for the words, every time.6810. **Every cut ends on a source card**: each source with its date, and69 "illustrative" when any figure is.7011. **Deterministic and offline; never post.** Every frame is a pure71 function of `t`; one standalone file; `finalize.js`'s exit code is the72 gate. The user posts, never you.7374## Workflow75761. **Read the source and build the claims ledger.** Read77 `references/copy.md`. Pull every figure and quote that could appear on78 screen into `claims`, with `verbatim`, `locator`, `kind` (copied, derived79 with `working`, or illustrative), and any `hedge` or `forecast`. List the80 findings, one sentence each with its number. Note every noun the source81 names that could be drawn (the things, their parts, their places).82832. **Settle format and length, asking at most two questions.** Read84 `references/formats.md`. Ask only what changes the build: where it will85 play (if unstated), and which finding leads (only when two are equally86 strong and the user picked neither). Defaults: 9:16, about 30–45 s,87 preset `default`. Never ask about style, colour, fonts or transitions.88893. **Name the point, direct each insight, then the shape and the beats.**90 Read `references/story.md`. Write the video's point with its main figure,91 and what a viewer must see happen to get it with the sound off. Then92 decide the world: where the story naturally happens, how that place93 behaves on its own (planets orbit, a herd grazes, a shop opens), and how94 it looks (`stage.setting`, `stage.look`). Never a default board. Then,95 for each insight, ask what it is a fact about and what you would see96 happen in the world if it happened in front of you; think of three97 actions and keep the one most specific to this source. That becomes the98 beat's `stage.shows`. Then the shape that holds the world together:99 **transformation** (one subject that changes), **lineup** (a cast100 compared), **assembly** (a thing coming into being), **episodes** (a101 place per item) or **journey** (a route on a schematic map). The shape102 guides layout and framing; it never decides what happens. Then the103 beats on the spine (hook → the middle → source card), about one per104 3–6 s, and what you leave out.1051064. **Write the world.** Read `references/stage.md` (the world painter, what107 the engine gives it: each beat's progress, the story's clock, running108 totals, the claims, the camera), `references/design.md` for the look and109 `references/motion.md` for how the card and the stage each move. You draw110 every thing from the source's nouns, in its natural colours and with real111 volume (living things are lofted bodies, never cut-outs), and make each112 beat's `shows` happen by its progress, its time or its rate. Each thing113 the story is about is a hero, drawn so it can't be mistaken for its114 nearest lookalike: its telling features pushed and posed toward the115 camera. There is no library of things or116 behaviours, on purpose. A value with nothing to act out gets a flat chart117 in the card (`references/video-charts.md`) while the world keeps living.1181195. **Copy the template and write the spec.** Copy120 `<skill-dir>/templates/video.html` to `./<slug>.html` (or where the user121 asked) and leave its `charts-lib/…` and `motion-lib/…` script tags122 exactly as written; step 8 folds them in. Read `references/engine-api.md`123 and write the whole spec: `stage` (shape, world, size, the clock's start),124 each beat's copy and `stage` directions; every figure in copy is a claim125 id (`"F1"` or `{F1}`), never typed digits. Fill the caption, the alt text,126 the page's `<title>`, heading and lede.127128 Then build it in stages, cheapest check first: stage129 (`finalize.js --stage`) and run `check-video.js` until no FAIL, with no130 browser. Then write the world **a beat at a time**, the hook's first131 one: look at one beat's still, fix it, then the next132 (`references/verify-and-ship.md` § Build in stages).1331346. **Sound only if asked.** Read `references/audio.md` before turning135 `meta.audio.score` on.1361377. **Verify before reporting done.** Read `references/verify-and-ship.md`138 and follow it in full: `node <skill-dir>/scripts/check-video.js139 <slug>.html` with no FAIL; in a browser, `VideoAudit.run` on every cut140 with `exportProbe: true` until each is `ok`; show each hero alone to a141 fresh reader who hasn't been told the topic and fix what they can't142 name (the cold read; with no fresh reader, the joint check, and say143 so); look at the contact sheet as144 an illustrator would against `stage.look`, and keep going while it reads145 as a board, cut-outs or greys;146 re-read every figure and hedge against the source. Without a browser,147 the static check and the re-read are the floor, and you say the frames148 weren't checked.1491508. **Ship one file:** `node <skill-dir>/scripts/finalize.js <slug>.html`.151 A non-zero exit means you are not done. Where Node may be missing, use152 `sh <skill-dir>/scripts/finalize.sh` (or `finalize.ps1` on Windows); it153 prints `UNCHECKED` when it couldn't run the checks, and you say so.154155## Output156157One HTML file, standalone. Surface it however your environment does (in158Claude Code: `SendUserFile` with `display: "render"`), otherwise print its159absolute path. Make an MP4 on disk only if you can drive a browser and the160user agrees to the download (`verify-and-ship.md` § An MP4 on disk).161162Then the handover in chat, short:163164- How to use it: open in Chrome or Edge; **Play**, scrub, ←/→ to step165 frames; **Export video** saves the MP4; **Export stills** saves a poster166 and a contact sheet; **Copy caption** and **Copy alt text**. Say which167 export path the probe found.168- The story's shape, and each cut's beats with `V` handles, timecodes, the169 figures each shows and their locators; which things on the stage are170 drawn as named in the source and which are generic; what was left out;171 which figures are from the source and which are illustrative; whether172 sound is on.173- Nothing was posted.174- The closing line, last, nothing after it (`references/tracing.md` §175 Handles and the closing line):176177```178Ask "where does V3.1 come from?" or "why is S1 drawn like that?" to see the working behind any figure or picture.179```180181Handles are for chat only: never in the video, the caption or the alt182text.183184## Tracing185186The video puts figures and pictures in public under the user's name. Read187`references/tracing.md` before answering any follow-up about a figure, a188word, a picture on the stage or a choice. It carries the handles (`V1…`,189`V3.1`, `[A]`, `V5.h`, `S2` for a thing on the stage), the trace block190(*From your source · Working · Where it appears · What would change it*),191the picture block, the choice block and the wording block. A trace192re-reads the source and **corrects the video** when it's wrong (spec, every193cut, caption, alt text, then steps 7–8 again). Pushback alone moves nothing.194195## Environment notes196197Nothing here needs a specific agent or vendor: file reads from this198directory, writing an HTML file, and Node for the scripts and checks. A199browser (a built-in pane, or headless Chrome or Edge) runs the audit and200the export probe when one is available. The user's export runs in their201own Chrome or Edge, which encode H.264; other browsers fall back to WebM202or a real-time recording, and the page says which path ran.