Search the Tabler icon library by name substring. Returns icon names usable in scene specs (e.g. 'IconShield', 'IconAlertTriangle'). All Tabler icons are line-style and use a consistent visual language.

List the canonical scene examples bundled with the kit. Returns an array of { name, kinds, orientation } entries — one per spec in examples/. ALWAYS call this before authoring a new scene so you can pick the closest example to clone instead of writing from scratch. PICK THE TRACK KIND BY CONTENT SHAPE, not by default. Do not reach for 'list-reveal' unless the content is genuinely a flat enumeration of >=3 peer items. Use 'flow' when describing a pipeline / sequence / before→after path (A → B → C). Use 'hub' when one central concept connects to 2-4 related satellites. Use 'comparison' for a two-sided contrast (old vs new, before vs after). Use 'title-overlay' for a hero text card with no diagram. Call list_examples first to see a canonical spec for each kind before authoring. Both portrait (1080x1920, default — reels / shorts / TikTok) and landscape (1920x1080 — YouTube / LinkedIn / web embeds) are supported; ask the user or infer from context which they want. Layouts auto-flip (e.g. 'flow' is vertical in portrait, horizontal in landscape).

Fetch the full JSON spec of a named example (from list_examples). Use the returned spec as a starting template — change icons, labels, title text, and durations, but keep the track structure that matches your content shape.

Validate a scene spec against the schema without rendering. Returns { ok, errors? }. Useful to check structure before render_scene. PICK THE TRACK KIND BY CONTENT SHAPE, not by default. Do not reach for 'list-reveal' unless the content is genuinely a flat enumeration of >=3 peer items. Use 'flow' when describing a pipeline / sequence / before→after path (A → B → C). Use 'hub' when one central concept connects to 2-4 related satellites. Use 'comparison' for a two-sided contrast (old vs new, before vs after). Use 'title-overlay' for a hero text card with no diagram. Call list_examples first to see a canonical spec for each kind before authoring. Both portrait (1080x1920, default — reels / shorts / TikTok) and landscape (1920x1080 — YouTube / LinkedIn / web embeds) are supported; ask the user or infer from context which they want. Layouts auto-flip (e.g. 'flow' is vertical in portrait, horizontal in landscape).

Render a scene spec to an MP4 (or .mov if background is 'transparent'). Returns { ok, outPath, durationSeconds, codec }. Defaults to 9:16 portrait (1080x1920) at 30fps; set width=1920, height=1080 for landscape. Duration must be 4-6 seconds. PICK THE TRACK KIND BY CONTENT SHAPE, not by default. Do not reach for 'list-reveal' unless the content is genuinely a flat enumeration of >=3 peer items. Use 'flow' when describing a pipeline / sequence / before→after path (A → B → C). Use 'hub' when one central concept connects to 2-4 related satellites. Use 'comparison' for a two-sided contrast (old vs new, before vs after). Use 'title-overlay' for a hero text card with no diagram. Call list_examples first to see a canonical spec for each kind before authoring. Both portrait (1080x1920, default — reels / shorts / TikTok) and landscape (1920x1080 — YouTube / LinkedIn / web embeds) are supported; ask the user or infer from context which they want. Layouts auto-flip (e.g. 'flow' is vertical in portrait, horizontal in landscape).