What problem does it solve? Hand-editing a Decentraland scene's main.composite file is error-prone: entities can fall outside parcel bounds and never render, missing inspector::Nodes entries make entities invisible in the Creator Hub entity tree, and incorrect jsonSchema usage causes SDK build failures. This Skill provides the format reference and mandatory validation workflow to author or edit composites correctly. ## Core Features & Use Cases - Composite Format Reference: Full specification of the main.composite JSON structure, entity ID allocation, and per-component catalogs (core::Transform, core::GltfContainer, core::MeshCollider, core::Animator, and more). - Bounds and Bounding-Box Validation: Mandatory Step 0 computes scene bounds from scene.json parcels and measures GLB bounding boxes so models are never placed outside the renderable area. - Edit-Mode vs Authoring-Mode Rules: Distinct checklists for fresh composites versus scenes already saved by the Creator Hub, including inspector::Nodes synchronization and the Creator Hub MCP gate. - Use Case: When adding a new 3D model entity to an existing Decentraland scene without the Creator Hub MCP, follow the edit-mode checklist to register the entity in inspector::Nodes, add core-schema::Name, and verify with an SDK build. ## Quick Start Ask the AI to add a new GLB model entity to the scene's main.composite file while keeping it inside the parcel bounds and visible in the Creator Hub entity tree.