find-exampleslisted

# Official examples Use official examples as version-matched recipes. Engine and Web Components examples are standalone applications to adapt, not modules to import. Use the `reuse-scripts` skill instead when the installed Engine ships a production script for the required behavior. ## Find the matching example When `node_modules/playcanvas` is a local source checkout or linked build — a symlink, a workspace, or a path dependency — its `examples/src/examples/**` are already on disk. Read them directly and skip the GitHub fetch below. A linked engine can sit ahead of any published tag, and a pre-release version (`-alpha`, `-beta`) may have no matching public tree, so the on-disk source is the ground truth. Fall back to GitHub only when the examples are absent locally; the published npm package omits `examples/`. ```sh ls node_modules/playcanvas/examples/src/examples 2>/dev/null && echo "linked engine: read local examples, skip the fetch" ``` Search the active surface's own catalog first, then the Engine catalog. Engine examples are the largest set and port to every surface; the per-surface catalogs are smaller but need no translation. | Surface | Repository | Package | Ref | Example paths | | --- | --- | --- | --- | --- | | direct Engine | `playcanvas/engine` | `playcanvas` | `v<version>` | `examples/src/examples/<category>/<name>.example.mjs` | | Web Components | `playcanvas/web-components` | `@playcanvas/web-components` | `v<version>` | `examples/<name>.html` | | React