LumosLab-Innovation/3D-lab-skills / plugins/threejs-lab/skills/learning-lab-3d-creator
learning-lab-3d-creator
VerifiedBuild complete production-grade 3D educational labs and simulations. Use when creating or refactoring science/physics labs, KHTN8 lessons, experiment scenes, Three.js/Babylon scenes, agent-connected simulation flows, control panels, reports, quizzes, tutorial phases, or reusable lab architecture.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.4 KB |
| agents/openai.yaml | config | 194 B |
| references/engine-decision.md | markdown | 2.2 KB |
| references/lab-contract.md | markdown | 717 B |
| references/project-stack.md | markdown | 1.4 KB |
references/engine-decision.md
View on GitHub# Engine Decision
Recommendation: default new school-lab simulations to imperative Three.js, but do not migrate every existing 3D surface blindly.
## Default Choices
- New curriculum/science lab: Three.js scene controller.
- Existing imperative Three.js lab: keep Three.js and improve lifecycle/performance.
- Existing Babylon game or world simulation: keep Babylon unless the task is already a planned rewrite.
- R3F/drei: use when a scene is naturally React-componentized or already written in R3F; avoid driving high-frequency physics through React state.
- Physics: formula/custom solver first, `cannon-es` for rigid-body/collision, Babylon physics only in Babylon scenes.
## Why
- The target app already has many Three.js simulation files, shared lab helpers, CSS2D labels, GLTF loading, and imperative setup/dispose patterns.
- The `CloudAI-X/threejs-skills` repo is valuable because it splits Three.js knowledge into focused areas: fundamentals, geometry, materials, lighting, textures, loaders, animation, shaders, postprocessing, and interaction.
- Three.js is enough for most school labs because the product needs controlled apparatus, labels, units, formulas, and visual clarity more than a full game engine.
- Babylon remains useful for game-like scenes, built-in physics integration, inspectors/tools, and existing Babylon surfaces.
## Migration Rule
Convert to Three.js only when at least one is true:
- The surface is a new lab.
- The current implementation is small and already isolated.
- The existing engine is the blocker for load time, maintainability, or visual consistency.
- The lab needs DOM/React UI integration more than engine-level game features.
Do not convert when:
- The Babylon scene already owns physics/game architecture.
- The rewrite would touch unrelated routing, UI, or agent flow.
- The user asked for one lab/bug and migration would delay delivery.
## Three.js Lab Standard
For new learning labs:
1. React component owns UI state and agent events.
2. `setup<Name>Scene.ts` owns Three.js scene lifecycle.
3. Scene state is plain data with units.
4. The solver is independent from meshes.
5. Visual sync mutates meshes from state.
6. QA includes build/lint plus browser canvas check.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |