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/project-stack.md
View on GitHub# Project Stack Notes
Historical example from the Lab029s application, not a required stack or a path assumed to exist on this machine. Inspect the current project's dependencies and layout first:
- Frontend: Vite, React 19, TypeScript, Tailwind 4.
- 3D deps: `three@0.183`, `@react-three/fiber`, `@react-three/drei`, `cannon-es`, Babylon core/loaders.
- Common 3D folders: `services/frontend/src/components/simulations/*`, `features/game/*/scene`, `components/atoms`.
- Existing simulation pattern: React component owns state; `setup<Name>Scene.ts` owns imperative Three.js lifecycle; control panel and shared chatbot/report/question components sit above the scene.
- Existing QA scripts: `npm --prefix services/frontend run build`, `npm --prefix services/frontend run lint`.
For that application only, these were the local surfaces (verify before reuse):
- New KHTN8 lesson: `components/simulations/khtn8`.
- New full experiment: sibling folder under `components/simulations/<topic>`.
- Shared 3D lab room/robot ideas: inspect `components/simulations/shared/labEnvironment.ts` and `robotAssistant.ts`.
- Agent-connected flow: inspect `DensityLab.tsx` and `ElectricityCoulombsLaw.tsx`.
- Physics/Babylon flow: inspect `features/game/mars-mission/scene/physicsSetup.ts`.
Do not add a second scene framework inside one lab. If the lab starts in Three.js, keep the feature in Three.js unless there is a strong reason to move a whole surface.
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: 471k | 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 |