Plan around reusable assets

Watch the commercial once as a viewer. On the second pass, ignore the story and count what must survive from shot to shot: the red car, the driver in two looks, the traveler, the consultant, the key, and every recurring location.

Build the dependency list first

Create one row for every visual that returns. Give it a stable name, record the reference you approved, and note the scenes that depend on it. The source saves the product as @car_sheet, tells Claude the same name, and repeats that handoff for every asset in the film.

Asset class	What you lock	What it protects later
Product	Shape, paint, badges, cabin details	Exterior, interior, and beauty-shot continuity
Character	Face, wardrobe, role-specific variants	Identity and story continuity across cuts
Prop	The key, disguise pieces, newspaper	Actions that must remain readable in motion
Location	Palette, geometry, and a clean plate	Geography and stable backgrounds

The folder structure is not decoration. One main folder per scene, asset-type folders inside it, and a fresh subfolder for each iteration make the winning generation recoverable after hundreds of attempts.

Before generating a scene, check that every returning visual has one approved reference and one stable name. If you cannot point to both, the scene is not ready to inherit continuity.