A Claude Code skillkit for scaffolding, developing, and maintaining Babylon.js apps and games, covering both the full engine (v9) and Babylon Lite, for apps and games alike.
Ten focused, flag-driven skills (bjs-*, Unix-style: each does one job, each prints full usage with no arguments) plus a shared, verified reference library, nested inside the bjs-reference skill and read by every other skill, instead of re-stating.
From idea to shipped build in three steps: sketch a throwaway single-file prototype straight in the browser, scaffold a real TypeScript project once the idea earns it, then develop it feature by feature, with the same skills guiding architecture, performance, and review the whole way.
Requires Claude Code installed. Install the skillkit once:
git clone https://github.com/<you>/bjs-skillkit.git ~/src/bjs-skillkit # replace <you>, or use your own fork
cp -r ~/src/bjs-skillkit/skills/. ~/.claude/skills/Then, as a message inside your Claude Code chat — not a shell command — type:
bjs-sketch --idea "a lazy orbiting camera around a shiny sphere for a product page"
Claude writes one self-contained HTML file; open it in a browser and you're looking at your idea, no npm install needed. See Skills and Quick start below for the full picture, including turning an idea into a real project.
| Skill | Kind | Purpose |
|---|---|---|
bjs |
orchestrator | Lifecycle guide: recommends which skill(s) to run for a described goal, runs freshness checks |
bjs-sketch |
operative | Zero-build, single-HTML-file Babylon.js prototype: before there's a project at all |
bjs-scaffold |
operative | Create a new Babylon.js app or game project |
bjs-feature |
operative | Add a scene/system/mechanic/UI-panel/shader/service to an existing project |
bjs-architecture-doc |
operative | Generate/sync docs/ARCHITECTURE.md |
bjs-performance-audit |
operative | Profile-driven rendering/runtime performance review |
bjs-mobile-check |
operative | Mobile web / desktop web readiness checklist |
bjs-lite-port |
operative | Migration helper: full Babylon.js → Babylon Lite |
bjs-review |
operative | Babylon.js-specific code review lens (complements generic code review) |
bjs-reference |
read-only | On-demand Babylon.js / Babylon Lite API and pattern lookup |
Every operative skill shares two cross-cutting flags, resolved once at scaffold time and read back by every other skill via a project's .bjs/config.json:
--engine full|lite: Babylon.js full engine or Babylon Lite. Never silently defaulted; seeskills/bjs-reference/reference/babylonjs-lite/feature-comparison.md.--profile quality|performance|balanced: concrete rendering/quality parameters, seeskills/bjs-reference/reference/performance/profiles.md.--backend none|express: optional companion Node/Express server (client+server dev workflow vianpm run dev:full), scaffolded from the start or retrofitted later viabjs-feature --kind backend. Defaultnone; seeskills/bjs-reference/reference/project-structure/server-structure.md.
This is a plain repo, not (yet) a packaged Claude Code plugin. Install all ten skills together, as a set, since several depend on bjs-reference's bundled reference/ subfolder for shared lookups, so skipping it or copying only some skills will break the others.
git clone https://github.com/<you>/bjs-skillkit.git ~/src/bjs-skillkit # replace <you>, or use your own fork
# global:
cp -r ~/src/bjs-skillkit/skills/. ~/.claude/skills/
# or, for a single project:
cp -r ~/src/bjs-skillkit/skills/. <project>/.claude/skills/Plain copy works because every skill is fully self-contained: bjs-reference/ bundles the shared reference/ library, bjs-scaffold/ bundles its own templates/. ln -s instead of cp -r works the same way if you'd rather track upstream updates than pin a snapshot.
All of the following are typed as messages in your Claude Code chat, not shell commands — Claude Code recognizes them as skill invocations.
Not sure the idea is even worth a project yet? Sketch it first - one zero-build HTML file, open it in a browser, no npm involved:
bjs-sketch --idea "a lazy orbiting camera around a shiny sphere for a product page"
Ready to commit to a real project? Describe the idea and let it infer the flags:
bjs-scaffold --idea "a small physics puzzle game, mobile-first, needs to load fast"
Inferred flags (engine, profile, type, starter-scene --template, ...) are shown with a one-line rationale each and confirmed with you before anything is written. See skills/bjs-reference/reference/project-structure/idea-to-flags.md. Any flag you also pass explicitly wins over what's inferred.
Or skip inference and pass flags directly:
bjs-scaffold --name my-solar-system --type app --engine full --profile quality
bjs-scaffold --name idle-miner --type game --engine lite --profile performance
Want a recommendation without committing to scaffolding yet?
bjs --suggest "small physics puzzle game, mobile-first, needs to load fast"
- Two kinds of guidance, applied differently. Architectural trade-offs (ECS threshold, layering, config-externalization, ...) are contextual, so skills ask and advise, never dictate. Code-level baseline (TypeScript conventions, structured logging, Babylon.js correctness) has no real trade-off and applies unconditionally to every operative skill's generated code. See
skills/bjs-reference/reference/README.md. - One shared reference library. All fact-based content (API patterns, gotchas, performance tables, project-structure templates) lives once, inside
skills/bjs-reference/reference/, not duplicated per skill; every other skill reaches it via a relative path, on the explicit premise that the whole kit is always installed together (see Install above). docs/ARCHITECTURE.mdas a toolbox, not a checklist. Only Project Identity + Repository Structure (with explicit dependency rules) is mandatory; everything else is added as a project actually grows into needing it. Seeskills/bjs-reference/reference/project-structure/architecture-doc-template.md.- Freshness is a first-class concern.
bjs --check-freshnessverifies the reference material's claims against the live Babylon.js / Babylon Lite repos rather than letting them silently rot. Seeskills/bjs-reference/reference/freshness/version-matrix.md. - Idea → tested → developed further, with no forced ceremony floor.
bjs-sketch(zero-build single file) →bjs-scaffold(real project, starter scene picked via--template, Inspector/FPS overlay on by default and gated out of production builds) →bjs-feature(grow it) is a ladder, not a single door. Seeskills/bjs-reference/reference/project-structure/scene-templates.mdandskills/bjs-reference/reference/babylonjs-full/debug-tooling.md.
This project is licensed unter MIT license. BJS Skillkit is an independent, community-built project. It is not affiliated with, endorsed by, or sponsored by BabylonJS.