Scenario Storyboards and Comics
Overview
Asked for a comic page, an agent prompts one model for "a page with six panels" and gets a page it
cannot fix: uneven panel geometry, a hero whose face changes between cells, dialogue rendered as
garble. The unit of generation is the panel, never the page. Script first, lock the cast, one
model_run per panel anchored to the same references, letter in post, assemble the page last.
Connection and the core loop: see the scenario skill. Character lock: scenario-consistency.
Per-model image contracts: scenario-image. Lettering: scenario-text-overlay. If a sibling skill
named here is missing from your available skills, load it with skill_get (Scenario MCP) or ask the
user to install it (https://github.com/scenario-labs/skills#install); unattended, proceed from tool
schemas and flag the gap.
Quick reference
| Stage |
Do |
| 1. Script |
A beat table before any generation: per panel, the shot size and angle, the action, the setting, the dialogue |
| 2. Cast and style |
One approved hero image per character plus a style pick (search with query="comic" surfaces style LoRAs); write each baseline |
| 3. Panels |
One model_run per panel: byte-identical baselines plus that panel's clause, references wired per the schema |
| 4. Review |
jobs_wait, then check identity panel over panel before lettering |
| 5. Letter |
Dialogue, captions, and sound effects as scenario-text-overlay cards composited onto text-free art |
| 6. Assemble |
Page layout and contact sheets: layer composition in scenario-video-assembly (Image Studio), or the grid tool in scenario-image-editing |
Label the panels the way a shot list does, in that order: number, shot size, angle, lens or camera
move, then the action with each character's frame side and facing. Arrange them as coverage rather
than a row of pictures: open on a master that establishes the geography, hold one side of the axis
so screen direction never flips, climb the size ladder as tension rises, and punctuate with an
insert or a reaction.
A storyboard headed for animation stops at stage 4. Approved panels become first frames for
image-to-video (scenario-video), one clip per shot, when each shot stands on its own. When the
movement itself has to carry across the cuts, animating panels independently resets the performance
at every one: that sequence belongs in the scenario-seedance-storyboard skill, which chains each
shot's exit pose to the next shot's entry.
Worked example: a six-panel comic page
- Script the page as a table: panel, shot size and angle, lens or camera move, action, dialogue and
captions. The action column holds only what a camera sees: a thought, a smell, or backstory
renders as nothing, so it becomes visible evidence or a caption. Dialogue and captions are
written down here, never prompted into the art.
- Cast lock: generate or upload the hero and iterate until approved; unattended, the script's own
character description stands in for the approval, so take the candidate that matches it and
continue.
asset_display the hero and write its baseline enumeration (geometry, costume, palette
by name or hex) per scenario-consistency.
- Style:
search with target="models", query="comic", public=true; the public catalog
carried comic-style LoRA hits at authoring time. Confirm the pick with the user (unattended, take
it from the task instructions, else the first result in returned order), then model_schema_get
it for the reference field's name, cap, and cardinality. No reference field that fits the cast?
Capabilities may advertise adapters the schema never exposes; the schema wins. Keep the pick for
hero generation and recommend a reference-capable model for the panels, restating the style
line in every prompt.
- Six
model_run calls. Each prompt is the style line, the character baseline, and the setting
line (location, time of day), all byte-identical across the panels that share them, plus that
panel's clause (shot, action), plus "clean art, no lettering, no speech bubbles". A dropped
setting line breaks continuity the same way a dropped baseline breaks identity. Wire the hero
reference as the schema says: an array only under array: true. A batch-count field repeats one
prompt, so it cannot carry per-panel clauses.
jobs_wait on the six jobs, re-calling with pending_job_ids. Review each panel against the
hero; fix drift by tightening that panel's enumeration and re-running from the baseline, never by
chaining from a neighboring panel.
- Letter with
scenario-text-overlay, composite the cards as layers, assemble the page, then file
panels and page in a collection (scenario-asset-analysis).
Common mistakes
- Generating a page in one run: panels from a single prompt cannot be regenerated one at a time, so
one bad panel costs the whole page.
- Prompting dialogue: generated lettering drifts and garbles; keep the art text-free and letter in
post.
- Chaining panel to panel: feeding panel three panel two's output compounds drift; anchor every
panel to the same approved hero.
- Writing "same character as before": there is no memory between calls; restate the full baseline
every time.
- Carrying a lasting change (a new costume from panel four on) as a per-panel clause against the old
hero: the reference pulls the old costume back. Generate a second hero from the first with the
change described, approve it, rewrite the baseline, and anchor the later panels to it.
- Animating unapproved panels: image money is cheap, video money is not; gate the expensive stage
the way
scenario-video-ads prices its board first.
- Merged characters: with several heroes in one panel, state each reference's role in the prompt,
check the schema's reference cap fits the cast before planning the scene, and keep extras generic
and unnamed; only cast that must stay recognizable gets a baseline and a slot.
- Abandoning a moderation-blocked action beat: providers can reject a weapon or fight panel
(
moderation_blocked); soften that panel's clause, de-emphasizing the weapon, and re-run from the
baseline.
1---2name: scenario-storyboards3description: "Use when a story must unfold across a sequence of Scenario images: a comic page or strip, manga or webtoon panels, a children's storybook, a film, game, or ad storyboard, animatic pre-viz frames, or any shot list where the same characters and world must persist from panel to panel and dialogue must stay legible. Keywords: storyboard, comic, panel, sequential art, storybook, shot list, pre-viz, animatic, scene to scene, character consistency."4license: MIT5metadata:6 source: https://skillmd.com/skills/scenario-labs/scenario-storyboards7---89# Scenario Storyboards and Comics1011## Overview1213Asked for a comic page, an agent prompts one model for "a page with six panels" and gets a page it14cannot fix: uneven panel geometry, a hero whose face changes between cells, dialogue rendered as15garble. The unit of generation is the panel, never the page. Script first, lock the cast, one16`model_run` per panel anchored to the same references, letter in post, assemble the page last.17Connection and the core loop: see the `scenario` skill. Character lock: `scenario-consistency`.18Per-model image contracts: `scenario-image`. Lettering: `scenario-text-overlay`. If a sibling skill19named here is missing from your available skills, load it with `skill_get` (Scenario MCP) or ask the20user to install it (https://github.com/scenario-labs/skills#install); unattended, proceed from tool21schemas and flag the gap.2223## Quick reference2425| Stage | Do |26| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |27| 1. Script | A beat table before any generation: per panel, the shot size and angle, the action, the setting, the dialogue |28| 2. Cast and style | One approved hero image per character plus a style pick (`search` with `query="comic"` surfaces style LoRAs); write each baseline |29| 3. Panels | One `model_run` per panel: byte-identical baselines plus that panel's clause, references wired per the schema |30| 4. Review | `jobs_wait`, then check identity panel over panel before lettering |31| 5. Letter | Dialogue, captions, and sound effects as `scenario-text-overlay` cards composited onto text-free art |32| 6. Assemble | Page layout and contact sheets: layer composition in `scenario-video-assembly` (Image Studio), or the grid tool in `scenario-image-editing` |3334Label the panels the way a shot list does, in that order: number, shot size, angle, lens or camera35move, then the action with each character's frame side and facing. Arrange them as coverage rather36than a row of pictures: open on a master that establishes the geography, hold one side of the axis37so screen direction never flips, climb the size ladder as tension rises, and punctuate with an38insert or a reaction.3940A storyboard headed for animation stops at stage 4. Approved panels become first frames for41image-to-video (`scenario-video`), one clip per shot, when each shot stands on its own. When the42movement itself has to carry across the cuts, animating panels independently resets the performance43at every one: that sequence belongs in the `scenario-seedance-storyboard` skill, which chains each44shot's exit pose to the next shot's entry.4546## Worked example: a six-panel comic page47481. Script the page as a table: panel, shot size and angle, lens or camera move, action, dialogue and49 captions. The action column holds only what a camera sees: a thought, a smell, or backstory50 renders as nothing, so it becomes visible evidence or a caption. Dialogue and captions are51 written down here, never prompted into the art.522. Cast lock: generate or upload the hero and iterate until approved; unattended, the script's own53 character description stands in for the approval, so take the candidate that matches it and54 continue. `asset_display` the hero and write its baseline enumeration (geometry, costume, palette55 by name or hex) per `scenario-consistency`.563. Style: `search` with `target="models"`, `query="comic"`, `public=true`; the public catalog57 carried comic-style LoRA hits at authoring time. Confirm the pick with the user (unattended, take58 it from the task instructions, else the first result in returned order), then `model_schema_get`59 it for the reference field's name, cap, and cardinality. No reference field that fits the cast?60 Capabilities may advertise adapters the schema never exposes; the schema wins. Keep the pick for61 hero generation and `recommend` a reference-capable model for the panels, restating the style62 line in every prompt.634. Six `model_run` calls. Each prompt is the style line, the character baseline, and the setting64 line (location, time of day), all byte-identical across the panels that share them, plus that65 panel's clause (shot, action), plus "clean art, no lettering, no speech bubbles". A dropped66 setting line breaks continuity the same way a dropped baseline breaks identity. Wire the hero67 reference as the schema says: an array only under `array: true`. A batch-count field repeats one68 prompt, so it cannot carry per-panel clauses.695. `jobs_wait` on the six jobs, re-calling with `pending_job_ids`. Review each panel against the70 hero; fix drift by tightening that panel's enumeration and re-running from the baseline, never by71 chaining from a neighboring panel.726. Letter with `scenario-text-overlay`, composite the cards as layers, assemble the page, then file73 panels and page in a collection (`scenario-asset-analysis`).7475## Common mistakes7677- Generating a page in one run: panels from a single prompt cannot be regenerated one at a time, so78 one bad panel costs the whole page.79- Prompting dialogue: generated lettering drifts and garbles; keep the art text-free and letter in80 post.81- Chaining panel to panel: feeding panel three panel two's output compounds drift; anchor every82 panel to the same approved hero.83- Writing "same character as before": there is no memory between calls; restate the full baseline84 every time.85- Carrying a lasting change (a new costume from panel four on) as a per-panel clause against the old86 hero: the reference pulls the old costume back. Generate a second hero from the first with the87 change described, approve it, rewrite the baseline, and anchor the later panels to it.88- Animating unapproved panels: image money is cheap, video money is not; gate the expensive stage89 the way `scenario-video-ads` prices its board first.90- Merged characters: with several heroes in one panel, state each reference's role in the prompt,91 check the schema's reference cap fits the cast before planning the scene, and keep extras generic92 and unnamed; only cast that must stay recognizable gets a baseline and a slot.93- Abandoning a moderation-blocked action beat: providers can reject a weapon or fight panel94 (`moderation_blocked`); soften that panel's clause, de-emphasizing the weapon, and re-run from the95 baseline.