LlamaGen Logo

Copy-ready prompt pack · Guide indépendant pour créateurs

Prompts Claude pour BD, scénario et storyboard

Réutilisez des modèles de fiches personnages, de mise en pages et de vérification de continuité avant de générer les visuels.

Guide pédagogique indépendant. GPT-6 et Astra appartiennent à OpenAI, Claude à Anthropic, Gemini et Nano Banana à Google. Ces sociétés ne cautionnent pas cette page. Mis à jour le 15 octobre 2026

Original story adapted into sequential illustrated comic frames, supporting a story-script-to-panel workflow
Origine de l’image: LlamaGen story-to-comic gallery visual showing the rendering step after prompt planning. Not a Claude-generated image. Vérifier la source ↗

Cette page est partiellement traduite. Les exemples détaillés, prompts et FAQ restent en anglais ; elle ne sera pas indexée avant une traduction entièrement vérifiée.

Réponse rapide

Réutilisez des modèles de fiches personnages, de mise en pages et de vérification de continuité avant de générer les visuels.

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.

Note importante sur les capacités du modèle These are independent example prompts, not an official Anthropic preset or a promise that all Claude environments can generate images.

Ce que confirment les sources 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.

Guide étape par étape

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 à copier

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

Résoudre les problèmes de création de BD

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

Cause probable Script and drawing fields were mixed.

Que faire Put exact spoken text in a dedicated lettering field.

2. Scene continuity breaks

Cause probable Prompt does not carry character IDs or props.

Que faire Reference the same bible and scene state across pages.

3. Panel count balloons uncontrollably

Cause probable Page and panel limits are omitted.

Que faire Set exact maximum page count and per-page panel count.

Points à vérifier avant publication

Review progress: 0 of 4 checks complete

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

Questions fréquentes

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 et ressources

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