What problem does it solve? Hand-editing a Decentraland scene's main.composite file is error-prone: entities can fall outside parcel bounds, inspector bookkeeping can desync, and the Creator Hub autosave can silently discard edits. 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 for core::Transform, GltfContainer, MeshRenderer, Material, AudioSource, and more. - Bounds and GLB Validation: Mandatory Step 0 computes scene bounds from scene.json parcels and measures GLB bounding boxes so models never render outside the scene. - Edit-Mode Safety Gates: Detects whether a composite is fresh or Creator Hub-managed, enforces inspector::Nodes synchronization, and prefers the Creator Hub MCP over risky file edits. - Use Case: When adding a tree model to an existing Decentraland scene without the Creator Hub MCP, follow the workflow to compute parcel bounds, measure the GLB extent, register the entity in inspector::Nodes, and verify with an SDK build. ## Quick Start Ask the assistant to add a new entity to the scene's main.composite file and validate it with the SDK build.