
Threejs Game Director
This is the orchestration layer for building complete Three.js games through Claude. It routes you through gameplay systems, AAA graphics, UI design, debug/profiling, and QA phases while managing five sibling skills and three generator skills for 3D models, textures, and audio. The discipline here is real: it maintains ledgers for skill loading, references, asset sourcing, and phase execution, refuses to call prototype work premium without evidence, and won't let you skip the visual scorecard for AAA claims. It adapts to different runner capabilities and knows when to ask you to paste command output instead of fabricating it. If you want a polished browser game and not just a spinning cube, this is where you start.
- skills.sh installs
- 3.5K
- GitHub stars
- 2.8K
- last updated
- Aug 21, 2026
Install
$ npx -y skills add majidmanzarpour/threejs-game-skills --skill threejs-game-director --agent claude-codeInstalls into .claude/skills of the current project.
Files
Three.js Game Director
Own the end-to-end game outcome: a playable loop first, then the visual and interface depth the request actually asked for, then browser evidence that it works.
Scope
The user's own words set the bar. "Make a small arcade game" is not a request for the full premium pipeline — build the good version of what was asked and stop. "Premium", "AAA", "polished", "high-fidelity", "showcase", "release-ready", or "less basic" is that request, and at that bar a first playable slice is not done. "Less basic" specifically means the current visual level was rejected; treat it as the premium bar.
Sponsors
Details
- Repository
- github.com/majidmanzarpour/threejs-game-skills
- Categories
- Testing & QA, DevOps & CI/CD, Release Management, Debugging, Automation & Workflows, Game Development
- First seen
- Jul 14, 2026