Lvl 2: Wardrobe / Styling Change¶

Like Lvl 1, but with wardrobe or styling tweaks layered on top of the dialogue rewrite. Still auto-approved. Still decimal-bumped.

When you'd do this¶

You're refreshing a winning workflow for a new season (lighter wardrobe in summer, layered in winter)
The avatar needs a styling update — different hair, new accessories, different mood
A specific account's archetype shifted and you want the wardrobe to match
You want to A/B test wardrobes — same script, two looks

If the change involves the environment, camera angle, lighting, or anything structural — it's Lvl 3 or higher, not Lvl 2.

What you do¶

make a Lvl 2 variant of XYZS1-V1 — keep the dialogue but change the wardrobe to "white linen shirt, casual" for Account A and "soft pink cashmere sweater" for Account B.

Applying Lvl 2 wardrobe variant. Two tabs to update.

Confirm wardrobe per account: Account A: white linen shirt, casual Account B: soft pink cashmere sweater

Proceed?

The Manager confirms wardrobe per avatar before touching anything. Wardrobe is per-account customization (different avatars have different archetypes); you don't apply one wardrobe globally.

After you confirm:

Updating image prompts on both tabs: Account A — wardrobe in scenes 01-08 updated to "white linen shirt" Account B — wardrobe in scenes 01-08 updated to "soft pink cashmere sweater"

Image prompts in Dynamic Prompt nodes touched. Avatar reference sheets, composition specs, camera angles, lighting — all unchanged.

Saved as XYZS1-V1-2.nbflow in approved/. Version registry updated.

Ready to run.

What changes in the `.nbflow`¶

Wardrobe lives in the per-scene image specifics — typically in plain Prompt nodes or in Dynamic Prompt rows that carry per-scene composition details.

flowchart LR
    subgraph "Lvl 2 changes"
        D1[Dialogue dynamic<br/>maybe rewritten]
        IS[Image scene specs<br/>wardrobe lines updated]
    end
    subgraph "Unchanged"
        SF[Setting / environment]
        CR[Camera / framing]
        LT[Lighting]
        REF[Avatar reference]
    end

    D1 --> Veo
    IS --> NB
    SF --> NB
    CR --> NB
    LT --> NB
    REF --> NB

If the dialogue is also being rewritten as part of the variant (the typical case), that follows the same logic as Lvl 1 — the dialogue rows in the Dynamic Prompt get the new lines.

Wardrobe per archetype¶

When you're proposing wardrobe, propose it per avatar archetype. Different accounts have different personas — what works on one doesn't always work on another.

Quick example:

Archetype	Wardrobe vibe
Naturopath / wellness practitioner	Soft neutrals, linen, cardigan, scarf
Confessional / relatable mom	T-shirt, pajama tank, no jewelry
Authoritative / clinical	Crisp blouse, blazer, fitted
Casual / aspirational	Trendy fitted basics, statement earrings

Match the wardrobe to the archetype, not to your own taste. The archetype is what makes that account's avatar feel like a coherent person across many videos.

Detailed in Chapter 8 — Avatar Archetypes.

Version naming¶

Same as Lvl 1 — decimal-suffix bump on the current major:

V1   → V1-1     could be either Lvl 1 OR Lvl 2 variant
V1-1 → V1-2     next variant (any combination of Lvl 1 + Lvl 2 changes)

Auto-approved. Lands in approved/.

You don't need separate version naming for Lvl 1 vs Lvl 2 — they share the same decimal bump pattern. The history note in the version registry records what changed.

Example session¶

refresh XYZS1-V2 for the summer season. Lighter wardrobe per account, keep all dialogue.

Lvl 2 wardrobe-only variant. Proposing per account:

Account A: white linen popover, neutral wash Account B: pastel pink sundress Account C: gray cropped tank, denim button-up over shoulders Account D: minimalist white tee, gold layered necklaces Account E: muted lavender knit top

All keeping the workflow's existing setting, camera, lighting.

Confirm proceed?

Account D should be more athleisure — change to "athletic gray tank, hair pulled back". Others fine.

Updated. Account D = "athletic gray tank, hair pulled back".

Patching the 5 image scene specs per tab now.

Saved as XYZS1-V2-1.nbflow in approved/.

When you're ready¶

→ Next: Driving variants from a Google Sheet. Once you're producing multiple Lvl ½ variants of the same workflow, editing a Sheet is dramatically faster than asking Claude to patch the .nbflow each time.