agentleFS
svenkatreddysvenkatreddy/universal-video-skills/skills/character-consistency/SKILL.md

character-consistency

Skill8 starsChanged 28 days agoMITView on GitHub

Keep faces, products, and props identical across AI-generated shots with an asset registry, reference sheets, and verbatim descriptions. Use when a character or product appears in more than one shot, or when faces keep drifting between generations.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Register everything that repeats: Every character, product, and key prop gets an asset ID before the first generation …

    line 15
  2. Very specific:

    Verify across shots: Check identity at every join (../video-qa/references/continuity.md).

    line 27
  3. Distinctive:

    Fewer recurring assets, better continuity: Every additional recurring character multiplies the drift surface.

    line 43

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Character Consistency

The single most visible failure in AI video: the same person looks like three different people across four shots. Models don't remember your character from shot to shot. Every generation starts from zero, so continuity has to be engineered with words, pictures, and IDs that don't change.

The workflow

  1. Register everything that repeats. Every character, product, and key prop gets an asset ID before the first generation (references/asset-registry.md). The registry is the single source of truth.
  2. Write the reference sheet. One canonical description per asset: physical, specific, frozen (references/reference-sheets.md). This text gets pasted verbatim into every prompt. Verbatim. Not "in your own words."
  3. Attach reference images where the model allows. Image inputs lock identity far better than text. The adapters note per-model support.
  4. Cite, don't describe. In every shot-brief, write the asset ID and paste the frozen description. Never paraphrase, never summarize, never "improve" it mid-project.
  5. Verify across shots. Check identity at every join (../video-qa/references/continuity.md). Drift caught at the join is a reshoot; drift caught at delivery is a disaster.

Rules that don't bend

  • One description, frozen. The moment two shots describe the same face differently, you have two faces. Copy-paste is a feature.
  • IDs are contracts. mara-01 means the registry entry, not "a woman kind of like Mara." When the description needs to change, change the registry and bump the version. Don't silently edit prompts.
  • Describe what's stable, not what's momentary. The reference sheet holds face, build, hair, wardrobe staples. Not expressions, not poses, not lighting. Momentary things live in the shot-brief.
  • Products are characters too. A bottle, a car, a logo: same discipline. Geometry, colors, label placement: frozen and cited.
  • Fewer recurring assets, better continuity. Every additional recurring character multiplies the drift surface. Design casts you can actually hold together.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.