Copy-ready prompt pack · Independent creator guide
Claude Comic Prompts: Script, Panel Layout & Character Bible
Copy practical Claude prompts for original four-panel comics, multi-page scripts, recurring characters, visual continuity and page-level editorial review.
Independent educational content. GPT-6 and Astra are OpenAI products; Claude is an Anthropic product; Gemini and Nano Banana are Google products. LlamaGen is not endorsed by those companies. Updated October 15, 2026
Quick answer
Start with a character bible prompt, generate a numbered page-and-panel script, then run a continuity audit. Treat produced visual descriptions as a handoff to an actual image-generation tool rather than a claim that Claude rendered artwork.
Claude is strongest in this workflow when its output is treated as a structured production brief. These reusable prompts produce scripts, layouts and continuity checks that a creator can send to a visual editor.
What the evidence supports Anthropic Skills and prompting documentation supports reusable instructions; results still require editorial review. Verify the source ↗
Worked example · editable production brief
Worked example: script schema you can send to an editor
A small example of the *format* a Claude prompt should produce. Exact fields make revision and rendering handoffs much easier.
| Field | Panel 1 | Panel 2 |
|---|---|---|
| Shot | Wide establishing shot of rainy station | Close-up of a torn ticket |
| Action | C01 enters from left holding map | C01 discovers handwritten clue |
| Dialogue | C01: 'We have one hour.' | C01: 'This is not my ticket.' |
| Character lock | Dark-green coat, bronze glasses | Same coat, glasses and right-side mole |
| Art direction | Room for bubble at top left | No in-image lettering |
Use this as an editorial schema, not a Claude image sample. Maintain a separate visual prompt for every panel.
Practical walkthrough
Follow the sequence using an original or authorized project. The workshop above is an editorial plan, not output falsely attributed to a model.
Step 1
Choose a production scope
Pick a short 4-panel strip or a 2-page scene before expanding a series.
Step 2
Create the character bible once
Include age range, face landmarks, outfit, color palette and one unique prop per recurring character.
Step 3
Generate panel-level output
Require exactly numbered pages and panels, with action, camera angle, dialogue and scene continuity fields.
Step 4
Editorially trim balloons
Read the dialogue aloud, cut excessive words and inspect the order of speech bubbles.
Step 5
Handoff to the comic editor
Render or assemble visuals with a suitable tool, then QA details against the original script.
Copy-ready prompts
Replace placeholder details with your own original story and reference assets. Paste into a compatible model or workflow; available tools and results differ.
1. Character bible for recurring cast
You are my comic continuity editor. Create a character bible for an original slice-of-life story with two recurring characters. For each give a stable ID, silhouette, face anchors, hairstyle, outfit colors, repeated props, speaking style and things that must never change. Avoid existing fictional IP.
2. Convert story to panels
Adapt the following original 300-word story into exactly 2 comic pages, each with 3–5 panels. For each panel output: page number, panel number, purpose, shot type, action, dialogue, SFX, background, character IDs, image prompt and continuity note. Put all visible text in a separate lettering field.
3. Fix a weak page
Audit this comic script for repeated shot types, balloon overload, confusing reading order, impossible character positions and missing emotional beats. Suggest the minimum revisions; preserve names and scene facts.
Failure → Cause → Fix
When your comic workflow goes wrong
Specific failure patterns matter more than a generic 'try again'. These fixes target the output you can inspect.
1. Dialogue gets embedded into the image prompt
Likely cause Script and drawing fields were mixed.
What to do Put exact spoken text in a dedicated lettering field.
2. Scene continuity breaks
Likely cause Prompt does not carry character IDs or props.
What to do Reference the same bible and scene state across pages.
3. Panel count balloons uncontrollably
Likely cause Page and panel limits are omitted.
What to do Set exact maximum page count and per-page panel count.
What to check before publishing
Review progress: 0 of 4 checks complete
A personal QA worksheet, not an automated pass/fail evaluation of your image.
Frequently asked questions
Can I paste these into Claude?
Yes. Add your original story and adapt requirements to the actual Claude product and available tools.
Will Claude export a finished comic?
These prompts specify a script/brief. A final rendered comic requires image generation, layout and export tools.
How are these different from a Skill?
Prompts are one-off instructions; a Skill packages reusable behavior and reference files for recurring work.
Sources and further reading
Primary documentation and public creator discussions; not a substitute for hands-on results.