File reference

A project is a folder of plain text files. The CLI, the web IDE, and the sync service all read and write the same layout, so anything you see in one place exists as a file you can open in another.

my-project/
├── project.json
├── skills/
│   └── <skill_id>/
│       ├── metadata.yaml
│       └── robotic_code.py
├── workflows/
│   └── <workflow_id>.json
├── worlds/
│   └── <world_id>/
│       └── world_state.json
├── objects/
│   └── <object_name>/
│       ├── <object_name>.urdf
│       └── <object_name>.object_model.yaml
└── canvas/
    └── <workflow_id>_screen.tsx

Item names are lowercase, start with a letter or underscore, and may contain letters, digits, underscores, and hyphens, up to 64 characters.

File	What it holds	Reference
`project.json`	Project manifest and the active workflow and world pointers	Project.json
`skills/<id>/metadata.yaml`	Skill id, parameters, preconditions, postconditions	Skill metadata.yaml
`workflows/<id>.json`	The workflow graph: nodes, edges, inputs	Workflow JSON
`worlds/<id>/world_state.json`	Scene contents and simulation config	World state JSON
`objects/<name>/<name>.object_model.yaml`	Parts, articulations, and anchors for one object	Object model YAML

📝
These pages describe files the tools write for you. Creating items through the CLI or the IDE produces valid files, and the editors keep them valid as you work. Read these pages to understand a file you are looking at, to review a change before you sync, or to fix something a tool cannot express. Hand editing is the exception, not the normal path.

Skills also carry Python that runs on the robot. For how that code is structured, see Authoring a skill.