generate-assets

Batch asset design generation is automated by reading pending assets from project.json, distributing prompts to the Gemini API, and queuing tasks to ensure consistent visuals across characters, scenes, and props. This enforces validation by requiring asset descriptions and reports outcomes with versioning.

Maintaining visual consistency requires queuing batch generation tasks through a unified API like Gemini. The system processes asset descriptions from project.json sequentially, applying versioning and validation to ensure character and scene designs match throughout the video project.

project.json tracks pending assets by identifying missing *_sheet entries for characters, scenes, and props. The generation system validates these descriptions, queues the missing assets for design generation, and updates the file with versioned outcomes after processing.

Yes, asset descriptions in project.json are required to generate design sheets. The system enforces validation by checking for these descriptions before queuing tasks and distributing prompts to the Gemini API for batch processing and versioning.

Yes, you can generate a single asset design by name instead of batch processing all pending assets. The system queues individual tasks or full batches from project.json, distributing prompts to the Gemini API and reporting versioned outcomes for each asset.

Validation of project.json descriptions is required to ensure accurate prompt distribution to the Gemini API. Enforcing validation prevents missing or incomplete asset data from breaking the batch generation queue and ensures versioned outcomes for characters, scenes, and props.