with one click
babylon-help
// Look up Babylon.js APIs, import paths, examples, loaders, Vite integration, and browser runtime behavior. Use for Babylon-specific API lookup, feature design, rendering setup, asset loading, and capture issues.
// Look up Babylon.js APIs, import paths, examples, loaders, Vite integration, and browser runtime behavior. Use for Babylon-specific API lookup, feature design, rendering setup, asset loading, and capture issues.
Generate or update a complete Babylon.js browser game from a natural-language description. Use when the user wants ${AGENT_NAME} to make, rebuild, or substantially extend a Babylon.js project end to end.
Look up current Bevy engine APIs, crates, examples, and patterns. Use for any Bevy-related question, including API lookup, feature design, architecture, and implementation patterns.
Generate or update a complete Bevy game from a natural-language description. Use when the user wants ${AGENT_NAME} to make, rebuild, or substantially extend a Bevy project end to end.
Generate or update a complete Godot game from a natural-language description. Use when the user wants ${AGENT_NAME} to make, rebuild, or substantially extend a Godot project end to end.
Look up Godot engine class APIs, methods, properties, signals, enums, or C# Godot syntax. Use when you need a targeted Godot API answer or a specific engine-class recommendation.
| name | babylon-help |
| display_name | Babylon Help |
| short_description | Babylon.js APIs, loaders, Vite patterns, and browser runtime help |
| default_prompt | Use ${BABYLON_HELP_COMMAND} for Babylon.js, Vite, WebGL, loader, or browser-capture questions. |
| allow_implicit_invocation | false |
| description | Look up Babylon.js APIs, import paths, examples, loaders, Vite integration, and browser runtime behavior. Use for Babylon-specific API lookup, feature design, rendering setup, asset loading, and capture issues. |
Use this skill for Babylon.js API questions, exact import paths, loader behavior, rendering setup, Vite/HMR integration, WebGL/browser runtime questions, and browser capture problems.
Single-version policy:
package.json and package-lock.json.Primary local sources after npm install:
node_modules/@babylonjs/core/
node_modules/@babylonjs/loaders/
node_modules/vite/
Lookup order:
package.json and lockfile for exact versions.node_modules/@babylonjs/core and node_modules/@babylonjs/loaders source/types.node_modules/vite docs/types for Vite-specific behavior.https://doc.babylonjs.com/.If node_modules/ is missing in a scaffolded project, run npm install before lookup. If the project is not scaffolded yet, use official docs and say which package version you are targeting.
Useful searches:
rg "class ArcRotateCamera" node_modules/@babylonjs/core
rg "ImportMeshAsync" node_modules/@babylonjs/core node_modules/@babylonjs/loaders
rg "handleHotUpdate" node_modules/vite
When answering:
Mandatory action after every successful lookup:
./.babylon-help.log.requested: what the caller asked forcomment: short resolution noteresult_files: concrete local files or official URLs usedKeep the log compact. Do not paste full docs or large code blocks into it.