composites

Author and validate Decentraland main.composite JSON files defining initial scene entities.

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/ansonj-dev/neon-reverse --skill composites-ansonj-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: composites
Source: https://github.com/ansonj-dev/neon-reverse/tree/main/agent/skills/composites
Command: npx skills add https://github.com/ansonj-dev/neon-reverse --skill composites-ansonj-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about composites

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add an entity to a Decentraland main.composite file?

Allocate the next entity ID starting from 512, add core::Transform and core-schema::Name entries, then add feature components like GltfContainer. If the composite already contains inspector::Nodes, also register the new entity there or it will be invisible in the Creator Hub entity tree.

Should I edit main.composite by hand or use the Creator Hub MCP?

Prefer the Creator Hub MCP whenever its tools are available, since it updates the live scene and autosaves consistently. Hand-editing is the fallback for CLI-only projects, and the scene must be closed in the Creator Hub or autosave will silently overwrite your changes.

Why does my entity render but not appear in the Creator Hub entity tree?

The entity was added to core::Transform but not registered in inspector::Nodes. Append its ID to the parent entry's children array and add a matching top-level entry with its own children array in the Nodes value list.

Why is my GLB model rendering outside the scene bounds?

A model's Transform position is its local origin, not its visual extent, and many GLBs extend several meters beyond it. Parse the GLB binary to compute the real bounding box including node scale, then clamp the origin within the parcel bounds computed from scene.json.

What components must never be included when authoring a composite from scratch?

Never include inspector::Nodes, inspector::SceneMetadata, inspector::Selection, inspector::TransformConfig, composite::root, or asset-packs::ActionTypes in a fresh composite. The Creator Hub auto-generates them on first save, and including them causes build errors or a broken entity tree.