Examples and ingested games

Every example is a real, standalone project under the vgai monorepo’s examples/<id>/ — its own vgai.project.json, package.json, and vite.config.ts, not bundled inside a scaffolded project. Get one’s source to read or build on: npx @vgai/cli@latest create <name> --example <id> makes a correctly-rewritten standalone copy. Each declares adapter-owned roots in its manifest and can be opened and played in the editor; projects may use a setup adapter, a manifest-native PixiJS/React root, or another supported adapter shape.

Examples run with the real engine in play mode (third-person-action shown).

The live catalog

Use the Examples & templates catalog for the complete list. Its cards are generated from each example’s vgai.project.json#learn block plus the shared template registry, so titles, difficulty, features, thumbnails, editor links, copy links, and lesson links cannot drift into a second hand-maintained table. The catalog includes all 29 shipped example projects and all curated templates.

Ingested (unmodified) — real upstream games, zero source diff

Real, third-party games are vendored byte-for-byte from upstream (verified against their pinned commits on every PR) and brought to the editor through the ingest seam: the game’s own modules are served in-realm on the editor’s own renderer instance, so capture, authoring, and every editor capability operate on the live game directly — a game the editor cannot fully reach does not mount. See Loading Existing Games and Ingest a game for the mechanism and the manifest shape.

See also

• Build a Game (Capstones) — the guided builds.
• Loading Existing Games — how to run existing third-party games on vgai, unmodified.