asset-spec

You can generate per-asset visual specifications and AI prompts directly from design documents like GDDs, level docs, or character profiles. The skill automates this by outputting structured specification files and updating the main asset manifest to track production progress.

An asset manifest tracks all visual specifications and naming rules before production starts. You need it after art bible and design approvals to ensure asset creation aligns with visual language, asset standards, and engine constraints.

Creating AI prompts from a level document involves deriving per-asset visual specs that match the art bible. The skill automates this by encoding rules and preferences to generate structured prompts and update the asset manifest before production.

Yes, an approved art bible and design documents are required before generating asset specifications. Running the specification process after these approvals ensures all derived asset specs and AI prompts align with the established visual language and engineering constraints.

Yes, asset specification generation applies to multiple target types, including level documents, character profiles, and general GDDs. It derives structured visual specs and AI prompts for each specific target and updates the central asset manifest accordingly.

The best way to align asset creation with engine constraints is by encoding rules and preferences into the specification process. This generates structured visual specs and naming rules from design documents before production starts, ensuring full compliance.