cg-generation-pipeline

name: cg-generation-pipeline description: Plan and run a reusable CG generation workflow for story-driven projects. Use when Codex needs to turn scripts, beat sheets, scene lists, asset-gap notes, or existing prompt folders into production-ready backgrounds, event CG, cut-ins, epilogue images, and character reference anchors; write or revise structured prompt files; preserve character continuity and visual hierarchy across batches; execute generation through project-native scripts or image APIs; validate framing, aspect ratio, and output utility; and hand off a clean updated asset set.

CG Generation Pipeline

Overview

Use this skill to turn narrative requirements into reusable CG asset batches without improvising a new pipeline every time.

Prefer small, coherent batches. Keep planning, prompt authoring, generation, validation, and handoff tightly coupled.

Read the reference files as needed:

• Read references/workflow.md for the end-to-end production sequence.
• Read references/prompt-patterns.md before writing or revising prompt files.
• Read references/continuity.md before generating recurring characters or style-sensitive CG.
• Read references/execution-and-qa.md before running generators, validating outputs, or packaging deliverables.

Quick Routing

• For asset-gap planning, start from the story input, existing asset inventory, and current prompt tree.
• For new prompt batches, use the structured prompt-file pattern instead of ad-hoc notes.
• For recurring cast or route-line CG, treat identity continuity as a hard requirement.
• For generation runs, prefer the target project's native scripts and folder conventions over one-off helpers.
• For handoff, report created files, updated counts, and the next best batch to tackle.

Workflow

1. Inspect the current state.

   • Read the source material that drives the batch: script, CSV, storyboard, beat sheet, or user list.
   • Inspect the current prompt folders and generated asset inventory.
   • Identify the smallest useful missing batch.

2. Define the asset contract.

   • Decide the asset category for each item: reference anchor, background, event CG, cut-in, or variant.
   • Decide target framing, reuse expectations, and output naming.
   • Keep the batch cohesive enough to validate in one pass.

3. Author prompts and metadata together.

   • Write prompt files with explicit target outputs and sizing.
   • Update any scene maps, script maps, manifests, or inventory docs used by the project.
   • Keep counts and index documents synchronized.

4. Enforce continuity and readability.

   • Lock recurring characters to stable visual anchors.
   • Preserve foreground/background hierarchy.
   • Keep dialogue-safe layout when an asset is intended to sit behind UI.

5. Execute generation.

   • Use existing project scripts if they exist.
   • If the project lacks scripts, keep commands deterministic and grouped by asset category.
   • Generate only the requested batch.

6. Validate and hand off.

   • Confirm files landed in the expected output locations.
   • Check dimensions, aspect ratio, naming, and scene usability.
   • Summarize the batch and recommend the next most valuable follow-up.

Guardrails

• Prefer incremental expansion over massive regeneration.
• Keep filenames, prompt slugs, and output slugs aligned.
• Keep reusable backgrounds readable and uncluttered.
• Keep event CG emotionally focused; do not let props or crowd noise bury the main subject.
• Translate style inspiration into non-infringing qualities such as brightness, readability, polish, or warmth.
• Update project tracking files whenever the project depends on them for runtime selection or manual assembly.