character-consistency

# character-consistency > Lock a character's visual identity into > `agents/reference/ai-video/<project>/characters/<id>.json` so every scene > reuses the **exact same tokens** verbatim. Downstream skills > ([`video-director`](../video-director/SKILL.md), > [`pixar-storyteller`](../pixar-storyteller/SKILL.md), > [`motion-choreographer`](../motion-choreographer/SKILL.md)) read > this file and never paraphrase. Verified by visual regression > (pixel similarity ≥ 95%, Phase 6 Step 3). ## When to use - A multi-scene run names the same character on screen more than once — Character Lock is mandatory before the second scene drafts. - A character drift bug landed (face / outfit / prop changed between scenes) — re-lock and rerun the affected scenes. - A series, episode, or recurring ad uses the same on-screen identity. Do NOT use when: - One-shot scene with no recurring character — overhead is wasted. - The "character" is an environment or set (a place, not an entity) — use a `style.json` lock pattern in the project's notes instead. Recurring creatures, vehicles, and hero objects DO get a real lock — pick the matching `subject_class` below. ## Procedure ### Step 0: Inspect 1. Check `agents/reference/ai-video/<project>/characters/` — if a lock already exists for this id, **read it, do not redraft**. Edits require an explicit revision note (Phase 6 visual regression must rerun). 2. Confirm the character will appear in ≥ 2 scenes; one-shot → skip. ### Step 1: Dr...