← Creator Dry Run Hub

ARTICLE 2 · WITH YOUR BRAND

Designing characters that can survive AI generation

A recurring character is not consistent because you gave it a name. Consistency comes from deciding its role, what must remain fixed, what can flex, and what visual information the model needs every time.

Start with role before appearance

Bee Righteous and Match were not designed as two interchangeable mascots. Their relationship and jobs inside the story had to be readable before any animation happened. Appearance followed role.

The relationship is part of the character system

Character consistency is not only anatomy. The relationship needs a repeatable emotional rule.

Bee Righteous + Match should read as magnetic, affectionate and creatively connected without being explicitly romantic. That gives the series room to express recognition, curiosity, encouragement, tension, discovery and creative momentum without locking every episode into one narrow interpretation.

For recurring IP, define not only who each character is, but how they are allowed to relate.

Build a character lock

For each recurring character, record a compact list of non-negotiables:

• relative height and body proportions
• base body colors and contrast
• eye color and eyebrow shape
• antennae count and shape
• wing count and general silhouette
• clothing that must remain
• signature marking or symbol
• personality and movement energy
• expression range
• features that must never transfer to the other character

The important rule is that the two character locks must also describe their difference from each other. A model can preserve two individually good characters and still blur their identities together.

Differentiation is a control system

Do not stop at “keep Character A consistent.” Also define “keep Character A clearly different from Character B.”

The first reference-image mistake

Our early character bible was useful for human thinking but overloaded for video reference. It contained multiple poses, expressions, labels, diagrams, repeated versions and broader world-building information.

The production reference fix

We simplified the production input to one clean square image containing only Bee Righteous and Match:

• both characters only
• full body
• three-quarter front view
• same baseline for scale comparison
• plain warm neutral background
• neutral readable expressions
• no props
• no alternate poses
• no environment
• no readable text
• no extra logos
• only Match’s restrained chest glow as an identity cue

Reference-image prompt practice

When creating a canonical character reference, organize the brief in this order:

ROLE → PROPORTIONS → BODY/COLOR → FACE/EYES → CLOTHING → IDENTITY MARKERS → MOVEMENT/PERSONALITY → RELATIVE SCALE → POSE → BACKGROUND → EXCLUSIONS

That structure is reusable for human characters, mascots, objects, creatures or branded visual IP. Do not ask one image to demonstrate every possible pose, scene and future use.

Character-system QA

1. Can I identify each character instantly in silhouette?
2. Is their size relationship obvious?
3. Does each character have one or two strong identity anchors?
4. Could the model accidentally swap their clothing, markings or proportions?
5. Is the reference image showing one canonical version?
6. Are there unnecessary visual elements competing with the characters?
7. Does the styling match the intended audience rather than drifting younger, cuter or more realistic than intended?

What we deliberately removed

During the production-reference pass, we removed unnecessary logos and extra symbolic elements. That was not because brand meaning is unimportant. It was because identity should be introduced intentionally rather than asking one reference image to carry every future brand cue at once.

The paid-control lesson

The free lesson is simple: define a character lock, define the difference between characters, and use a clean canonical reference. The advanced problem is preserving that identity across scenes, tools, aspect ratios, episodes and new poses without creating drift. That is where reference architecture, continuity records, version control and reusable production prompts become CONTROL / Creator Pro practices.