Documentation
Engine-ready UI
Understand each engine handoff’s contents and limits.
Engine JSON
Unity, Unreal, Godot, and Phaser JSON mappings describe supported hierarchy, frames, and properties. Inspect warnings for unsupported features, interactions, and unresolved asset bindings. JSON handoff alone is not a complete native runtime.
Packages
Unity JSON + assets contains metadata and sprites rather than generated prefabs. Unreal packages include a scoped raster UMG consumer and native manifest; the dialog reports structural preflight support and blockers. Rive handoff contains layout data and assets rather than a compiled .riv file.
Validation
Runtime-ready export can block unsupported content; warning-oriented handoff can retain warnings for downstream work. Resolve missing assets and native blockers, then test a representative export in your engine for sizing, nine-slice behavior, and interactions.

