LlamaGen Logo

Copy-ready prompt pack · Unabhängiger Leitfaden für Kreative

Claude-Prompts für Comics, Figuren und Storyboards

Kopierbare Vorlagen für Figurenbibeln, Seitenskripte, Panel-Planung und Kontinuitätskontrollen.

Unabhängige Lerninhalte. GPT-6 und Astra gehören zu OpenAI, Claude zu Anthropic, Gemini und Nano Banana zu Google. Keine dieser Firmen befürwortet diese Seite offiziell. Aktualisiert am 15. Oktober 2026

Original story adapted into sequential illustrated comic frames, supporting a story-script-to-panel workflow
Bildquelle: LlamaGen story-to-comic gallery visual showing the rendering step after prompt planning. Not a Claude-generated image. Quelle prüfen ↗

Diese Seite ist teilweise übersetzt. Ausführliche Beispiele, Prompts und FAQ sind noch auf Englisch; die Seite bleibt bis zur vollständigen Prüfung von der Indexierung ausgeschlossen.

Kurzantwort

Kopierbare Vorlagen für Figurenbibeln, Seitenskripte, Panel-Planung und Kontinuitätskontrollen.

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.

Wichtiger Hinweis zu den Modellfunktionen These are independent example prompts, not an official Anthropic preset or a promise that all Claude environments can generate images.

Was die Quellen belegen 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.

FieldShot
Panel 1Wide establishing shot of rainy station
Panel 2Close-up of a torn ticket
FieldAction
Panel 1C01 enters from left holding map
Panel 2C01 discovers handwritten clue
FieldDialogue
Panel 1C01: 'We have one hour.'
Panel 2C01: 'This is not my ticket.'
FieldCharacter lock
Panel 1Dark-green coat, bronze glasses
Panel 2Same coat, glasses and right-side mole
FieldArt direction
Panel 1Room for bubble at top left
Panel 2No in-image lettering

Use this as an editorial schema, not a Claude image sample. Maintain a separate visual prompt for every panel.

Schritt-für-Schritt-Anleitung

Follow the sequence using an original or authorized project. The workshop above is an editorial plan, not output falsely attributed to a model.

  1. Step 1

    Choose a production scope

    Pick a short 4-panel strip or a 2-page scene before expanding a series.

  2. Step 2

    Create the character bible once

    Include age range, face landmarks, outfit, color palette and one unique prop per recurring character.

  3. Step 3

    Generate panel-level output

    Require exactly numbered pages and panels, with action, camera angle, dialogue and scene continuity fields.

  4. Step 4

    Editorially trim balloons

    Read the dialogue aloud, cut excessive words and inspect the order of speech bubbles.

  5. Step 5

    Handoff to the comic editor

    Render or assemble visuals with a suitable tool, then QA details against the original script.

Prompts zum Kopieren

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

Probleme beim Comic-Workflow beheben

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

Mögliche Ursache Script and drawing fields were mixed.

Lösung Put exact spoken text in a dedicated lettering field.

2. Scene continuity breaks

Mögliche Ursache Prompt does not carry character IDs or props.

Lösung Reference the same bible and scene state across pages.

3. Panel count balloons uncontrollably

Mögliche Ursache Page and panel limits are omitted.

Lösung Set exact maximum page count and per-page panel count.

Vor der Veröffentlichung prüfen

Review progress: 0 of 4 checks complete

A personal QA worksheet, not an automated pass/fail evaluation of your image.

Häufige Fragen

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.

Quellen und weiterführende Links

Primary documentation and public creator discussions; not a substitute for hands-on results.