Case studies/Case study 02

AI CONTENT SYSTEM · BUILT + IN USE

A visual world that
doesn’t drift.

Turning style rules, character references, scene generation, animation, and finishing into one reusable creative pipeline—without automating away taste.

For
A series that should feel made by one hand
Industry
Creative production
System
Ruby CLI + image and video models
Deliverables
Stills, motion clips + captions

01 / THE FRICTION

One good image is easy.
A coherent series is not.

Generative tools could make an attractive frame, but every new scene created another chance for the world to wander. Characters changed shape. Environments lost their texture. Color drifted. Settings repeated. The rules lived in one person’s memory and had to be reconstructed inside every prompt.

The real problem was not generation. It was continuity: making dozens of independent model calls feel like parts of the same body of work.

The system needed to remember the world so the person could concentrate on the story.

02 / BEFORE THE BUILD

The checklist worked.
It also revealed the system.

The first version was deliberately manual: a style bible, character sheets, a scene template, a motion template, and a ten-step checklist. Running it exposed exactly what software needed to hold.

01

Style by memory

The same visual rules had to be restated and interpreted for every scene.

02

Character drift

Descriptions alone were not enough to keep recurring characters recognizable.

03

Repeated ideas

Nothing remembered which settings, palettes, and compositions the series had already used.

04

Split strengths

One video model produced better sound; another held the camera where it belonged.

03 / THE SYSTEM

One small command line.
A whole production method.

The finished workflow stores style, characters, palettes, quotes, prior settings, and every selected result in files it can read again. It generates options at each creative fork and waits for a person to choose.

  1. 01Define

    Load the locked world, characters, palette, quote, and rules for the series.

  2. 02Brainstorm

    Generate different scene concepts while avoiding settings already used.

  3. 03Generate

    Build reviewable still variations from pinned references and structured prompts.

  4. 04Select

    A person chooses the scene and image worth moving forward.

  5. 05Finish

    Animate, combine the strongest picture and audio, and prepare the caption.

THE OUTPUT

A frame from the system—not a one-off prompt.

EMBER + MOON · 8 SECONDS

The same pinned style and character references travel through every scene. The clip is an output of the production system; the system is the actual project.

04 / THE GUARDRAILS

Consistency became a set of refusals.

01

No scene-specific style anchors. Every image starts from the same canonical visual source.

02

No inferred characters. Recurring characters come from pinned solo references and structured definitions.

03

No recycled setting by accident. The brainstormer sees what the series has already used.

04

No words burned into the art. Quotes and captions remain editable, accessible, and separate from the image.

05

No automatic publishing. The system creates candidates. Selection remains a human act.

05 / WHAT CHANGED

From remembering every rule
to directing the work.

BEFORE

Rebuild the prompt by hand

Re-describe every character

Remember the style constraints

Track previous scenes mentally

Move files between tools manually

NOW

Load the same source of truth

Generate genuinely different concepts

Review three visible candidates

Choose the version with the right feeling

Finish picture, sound, and caption together

THE PRINCIPLE

The system holds the style. The person holds the taste.

06 / THE HUMAN PART

Every command produces candidates.
None produces a post.

The system can enforce continuity, remember prior decisions, assemble prompts, call the models, and combine outputs. It cannot decide which scene says something, which imperfection feels alive, or whether the result belongs in the series. Those are the decisions the workflow is designed to protect.

This demonstration uses original fictional characters and contains no client or employer material.

YOUR WORKFLOW DOESN’T HAVE TO BE CREATIVE

What does your team
keep in its head?

Show me the process

If quality depends on somebody remembering the same rules every time, there may be a useful system hiding inside the work.