The class diagram below shows the video-production portion of the
toolkit and the relationships between the skills and supporting
artefacts. scene-inventory-extractor-v2 produces the scene pack,
continuity inventory, prompt keyword library, recurring visual element
definitions, and reference images. shot-specifier consumes that
package, uses nanobanana for storyboard frames, consults the Seedance
or Kling deep-dive skill when a shot is routed to that model, and emits
prompt files plus the manifest. video-generator consumes that handoff
and submits jobs through the Higgsfield MCP. The phoneticize skill is
part of the repository but is independent of this visual generation
pipeline.
All nanobanana image calls in this pipeline must request
model: gemini-3-pro-image-preview. If that model is unavailable or cannot accept the
reference images or character-consistency images required by the current operation, the
image-generation workflow stops instead of selecting a fallback model.
Figure 2 — Video skill and artefact relationships. Solid arrows show
runtime dependency or handoff direction: the extractor creates
continuity and recurring-element constraints, shot-specifier turns
them into per-shot prompt and reference requirements, and
video-generator submits only after validating those requirements
against the live Higgsfield MCP. The dashed arrow records provenance:
the prompt keyword library is produced by extractor Phase 2.4 and then
reused downstream for style consistency.