A script + beat map pairs a lightweight script (dialogue and action) with a structured beat list that maps story intent to visuals.

Why it works for AI comics:

• Beats localize intent: who, goal, conflict, outcome per panel or micro-sequence.
• Prompts stay consistent: characters, props, setting, camera, lighting.
• Pacing is measurable: beats per page, panel density, page-turn reveals.
• Hand-off is clean: LLMs draft beats; image models render per-beat shots; layout tools place panels.

Use this minimal schema for each beat.

Project:

• Title • Genre • Tone • Theme
• Style refs (manga/manhwa/western), aspect ratio, color profile
• Cast: name, tags (age, outfit, hair, accessories), reference URLs

Beat fields:

• ID: S1-B03 (Sequence 1, Beat 3)
• Type: action | dialogue | reveal | transition | montage | inset
• Synopsis: one line of what changes
• Intent: character goal; Stakes: why it matters
• Setting: location, time, weather
• Visual: key pose/action, facial expression, props
• Camera: shot size (WS/MS/CS), angle (low/high/eye), lens feel
• Composition: panel size, position, gutters, page-turn? true/false
• Continuity: must-keep details (outfit, damage, prop state)
• Dialogue/FX: exact text; SFX cues
• Prompt: positive tokens; negative tokens; style refs; LoRA/embeds
• Seed/Vars: seed, CFG, sampler, control refs (pose/depth/lineart)
• Output: panel index, expected dimensions, file name
• Outcome: state change that advances story

1. Box the story: write a one-sentence logline; list cast and their visual anchors.
2. Sequence the arc: Break into 3–5 sequences; mark page-turn reveals at sequence ends.
3. Draft beats: 6–9 beats per 8–10 pages; tag each beat’s Type and Outcome.
4. Map beats to pages: plan 4–7 panels per page; reserve whitespace for emphasis.
5. Write dialogue last: keep balloons ≤25 words; 1–2 per panel.
6. Create prompt blocks: per-beat tokens for character, setting, mood, camera, lighting.
7. Generate thumbnails: low-res frames from prompts; adjust shot sizes and staging.
8. Lock continuity: fix seeds, LoRAs, outfits; store as Beat.Seed and Beat.Refs.
9. Final renders: upscale, line harmonization, color pass; keep file names from the beat map.
10. Lettering/layout: place balloons; check reading order (Z-path or right-to-left for manga).
11. QA pass: verify beat outcomes, page turns, and prop continuity.

• Panels/page: 4–7 (average 5). Dialogue-heavy pages: 4–5; action: 6–7 small panels.
• Beats: often 1 beat = 1 panel; reveals may consume a full page; montages can compress 3–5 micro-beats.
• Page-turn reveals: land cliffhangers on the right-hand page; reveal on the next left page.
• One-shots: 12 pages ≈ 55–70 panels ≈ 50–60 beats.
• Chapter rhythm: open wide (WS), tighten to CS for emotion, release with a reveal panel.
• Density checks: if WPM > 120 per page, split beats or add an inset panel.

• LLM: expand Beat.Synopsis into Prompt, Dialogue, SFX; keep a style-safe vocabulary list.
• Diffusion: use ControlNet/Control-LLite for pose/lineart to maintain continuity across beats.
• Character locks: dedicated LoRA/embeddings per main character; store version in Beat.Refs.
• Camera consistency: reuse seeds for consecutive shots; vary only angle or lens tokens.
• Compositing: generate clean characters + background separately; merge for consistent line weight.
• File system: /seq-01/p-03/S1-B03_panel02.png; export a JSON of beats with path pointers.

Panel/action (character close-up): "manga, clean lineart, dramatic close-up, {CHAR_NAME} {EXPR}, {OUTFIT_TAGS}, rim lighting, {CAMERA_ANGLE} angle, {LENS} lens, detailed eyes, screen tone, {ARTIST_STYLE}, sharp inks" Negative: "blurry, extra fingers, off-model face, inconsistent outfit, watermark"

Wide establishing shot: "cinematic wide shot of {LOCATION} at {TIME}, {WEATHER}, depth haze, leading lines, {COLOR_PALETTE}, subtle grain, manga backgrounds, consistent perspective"

Action beat: "dynamic pose, motion lines, speed effects, debris, dramatic lighting, tilted horizon, panel-breaking composition, sharp inks, high contrast"

S1-B01 (P1-Panel1) Type: establishing — Outcome: city at dawn sets mood

• Visual: WS rooftop; Camera: WS, eye-level; Dialogue: none

S1-B02 (P1-Panel2) Type: action — Outcome: hero discovers device

• Visual: Hero kneels; prop glows; Camera: MS; Dialogue: "What is this?"

S1-B03 (P1-Panel3) Type: reveal — Outcome: mark page-turn hook

• Visual: Shadow figure reflected; Camera: CU; Dialogue: whisper SFX

S1-B04–B06 (P2-Panel1–3) chase micro-beats; S1-B07 (P2-Panel4) pause CS for emotion

S1-B08 (P3-Panel1) setup; S1-B09 (P3-Panel2) misdirection; S1-B10 (P3-Panel3) cliffhanger

• Land cliffhanger on right page; reveal deferred to next spread.

• Every beat has a state change (Outcome) that justifies its panel.
• Composition supports reading order; balloons placed last.
• Character anchors match model sheet: hair, outfit, accessories.
• Camera variety per page: WS → MS → CS; avoid monotony.
• Seeds and LoRAs logged; exact prompts saved with outputs.
• Page-turn reveals placed intentionally; no accidental spoilers.

• Formats: JSON (beats, prompts, file paths), CSV (print sheets), Markdown (review).
• Naming: S{seq}-B{beat}_P{page}-PN{panel}.png; include seed in EXIF or sidecar JSON.
• Bundle: /beats.json, /thumbs/, /finals/, /fonts/, /model_refs.md

• Bloated beats: merge if Outcome repeats; delete if no state change.
• Off-model characters: lock LoRA strength; pin hairstyle/accessory tokens in every Prompt.
• Flat staging: add foreground shapes or change angle; vary lens tokens.
• Dialogue walls: convert to two beats or add an inset reaction panel.
• Inconsistent lighting: add a per-sequence lighting bible and reuse tokens.