Babylon.js Engine skill
Build real-time scenes with Babylon.js cameras, PBR, physics and loaders.
Community · freshtechbro| Author | freshtechbro |
|---|---|
| Licence | MIT |
| Source | freshtechbro/claudedesignskills · SKILL.md on GitHub |
| Works in | Claude Code · Codex, Gemini CLI, Cursor, Copilot |
| Read from the source on |
babylonjs-engine: Build real-time scenes with Babylon.js cameras, PBR, physics and loaders.
Its examples span engine lifecycle, PBR, model loading, physics integration and performance diagnostics.
From the skill's SKILL.md: # Babylon.js Engine Skill
What it does
- Configure an engine and scene, then integrate rendering and input.
What you get
- Scene code, loader setup and debugging guidance.
When to use it
- Create browser-based 3D applications or games.
When not to use it
- Treating reference snippets as tested production code for every release.
What it needs
- JavaScript/TypeScript project, Babylon.js packages and a compatible browser. Physics may require separate plugins.
Files in the skill
| File or folder | What it is for |
|---|---|
SKILL.md | Entry-point instructions and workflow boundaries. |
Licence as found in the repository on 2026-11-16: MIT.
Example prompts
Type one of these after installing; naming the skill makes sure it is used.
- Build a Babylon.js scene.
- Configure a PBR material.
- Load a model and inspect performance.
How to install babylonjs-engine
Prepare the workflow
Copy the skill folder and install project dependencies separately. Match examples to the Babylon.js release and renderer used by your app.
A skill is a folder with a SKILL.md file. You install it once; the agent reads its short description at the start of each session and loads the full instructions only when a request matches. Pick the place you use:
Claude Code: copy the folder into your skills folder
Put the skill's folder in ~/.claude/skills/ to use it in every project on this computer, or in .claude/skills/ inside a repository to share it with everyone who works there (commit it).
git clone --depth 1 https://github.com/freshtechbro/claudedesignskills.git
mkdir -p ~/.claude/skills
cp -R claudedesignskills/.claude/skills/babylonjs-engine ~/.claude/skills/Claude Code notices new or changed skills in these folders during the session. If the skills folder did not exist when the session started, run /reload-skills once. Then type /babylonjs-engine or just describe the task.
On Windows, run the commands in Git Bash or WSL, or copy the folder into the same place with File Explorer.
Codex, Gemini CLI, Cursor and GitHub Copilot
These agents read the same SKILL.md folders. The one folder all four accept inside a project is .agents/skills/, so this copies the skill there:
git clone --depth 1 https://github.com/freshtechbro/claudedesignskills.git
mkdir -p .agents/skills
cp -R claudedesignskills/.claude/skills/babylonjs-engine .agents/skills/| Agent | Project folder | Your user folder | Notes |
|---|---|---|---|
| OpenAI Codex | .agents/skills/ | ~/.agents/skills/ | Type $ or run /skills to pick a skill; Codex also chooses one when your task matches. |
| Gemini CLI | .agents/skills/.gemini/skills/ | ~/.agents/skills/~/.gemini/skills/ | Or install from Git with gemini skills install <git URL> --path <folder> --consent. Google replaced Gemini CLI with Antigravity CLI for free-tier and Google One users on 18 June 2026; Antigravity uses .agents/skills/ in a project and ~/.gemini/config/skills/ for you. |
| Cursor | .agents/skills/.cursor/skills/ | ~/.agents/skills/~/.cursor/skills/ | Type / in Agent chat to pick a skill. Cursor also reads Claude Code's .claude/skills/ folders. |
| GitHub Copilot | .github/skills/.agents/skills/.claude/skills/ | ~/.copilot/skills/~/.agents/skills/ | Works in Copilot CLI, the cloud agent, and agent mode in VS Code, Visual Studio and JetBrains (IDE support depends on the version). Or run gh skill install OWNER/REPOSITORY SKILL (public preview, GitHub CLI 2.90.0 or later). |
Sources for these steps
Checked against each vendor's documentation on 2026-11-14:
Engine and scene lifecycle
Rendering, camera controls and resize handlers need consistent ownership. Dispose scenes and engines when removed.
Check integrations
Model loading, shadows, physics and material APIs vary by configuration. Verify behavior on the target browser and package release.
Questions about babylonjs-engine
Does it install the engine?
No. Add Babylon.js packages to your own project.
Does it cover physics?
It includes integration patterns; plugin setup remains separate.
Is this official Babylon.js material?
No. It is a community skill.
Can I ignore resize and cleanup?
No. Engine lifecycle and resources still need ownership.
More AI skills
Related skills
Three.js Asset Pipeline skill
Community · CloudAI-XglTF inspection, optimization, compression and React model output.Three.js Fundamentals skill
Community · CloudAI-XScenes, cameras, renderer setup, transforms and cleanup.Three.js Geometry skill
Community · CloudAI-XBuilt-in shapes, BufferGeometry, instancing, batching and point clouds.Three.js Materials skill
Community · CloudAI-XUnlit, shaded, PBR, transparent and node-based materials.Three.js Lighting skill
Community · CloudAI-XPhysical light units, shadows, HDR environments and light probes.Three.js Textures skill
Community · CloudAI-XColour spaces, UV channels, image maps, KTX2 and render targets.