Build and revise procedural 3D assets with your coding agent. Local MCP server, CLI and TypeScript engine with rendered review, editable source and GLB export.
Asset examples
For recent work, browse the gallery and interactive scenes. Download Runtime assets for an application or Editable assets to retain the authored sources and revisions.
| Collection | Sources and examples |
|---|---|
| Troy | Horse, ships, characters, buildings and props |
| Farm | Buildings, animals, crops and equipment |
| Vehicles | Six road vehicles and saved revisions |
| Golden Gate Bridge | Standalone bridge sources |
| Foundry Floor | Factory asset sources |
Follow the asset source guide to restore a collection into a separate workspace. Saved material dependencies and the recorded engine version matter when rebuilding an existing asset. Scene interaction code is separate from the models.
For small examples of current APIs, use kiln_discover or kiln discover. Its
helper examples and recipes come from the maintained engine catalog, not the
repository's historical examples/ folder. Neither that folder nor the asset
packs are bundled into the npm package or automatically supplied to an agent.
Historical collection
The old standalone examples are preserved in the website archive and Git history. They are historical showcases, not recommended implementations or quality baselines.
They are no longer part of the active source tree. Contributors building the archive gallery or running the full regression corpus can restore the exact programs, credits and image records into an ignored cache:
node scripts/example-archive.mjs --fetch
Run this from an engine checkout. It does not add files to a user's asset workspace or change the npm installation. No teaching collection or asset-discovery index is added. Small engine-specific regression fixtures remain under tests.