Threejs Gameplay Systems

This is a full-stack workflow for building playable Three.js prototypes with actual design thinking baked in. It ships with a Vite+TypeScript scaffold, forces you to write a design brief and core loop contract before you code, and loads reference guides for physics engine selection, game feel tuning, and level design when the context demands it. Use it when you're starting a new browser game or when your prototype has mechanics but no pressure, reward, or fail state. The workflow is opinionated about deterministic update order, allocation-light hot paths, and proving behavior through real input rather than describing it. It catches the common trap of building a static Three.js demo and calling it gameplay. The included checklists and reference ledger keep you honest about whether something is actually playable or just pretty.

skills.sh installs: 3.8K
GitHub stars: 2.8K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add majidmanzarpour/threejs-game-skills --skill threejs-gameplay-systems --agent claude-code

Installs into .claude/skills of the current project.

Files

Three.js Gameplay Systems

Create or evolve a playable browser game loop with clear ownership, responsive controls, deterministic update order, and a space that shapes player decisions.

Resolve <this-skill-dir> and local references from the actual loaded skill file; resolve sibling skills beside it before using runner-discovered alternatives.

References

File	Read it when
`references/game-feel.md`	tuning feel, juice, impact, hitstop, screenshake, or claiming polished gameplay
`references/genre-design.md`	designing levels, arenas, tracks, waves, holes, puzzles, encounters, or difficulty curves
`references/physics-engine-selection.md`	adding or changing physics, collision-heavy gameplay, vehicles, rolling balls, character controllers, sensors, moving platforms

Start here

python3 <this-skill-dir>/scripts/create_threejs_game.py ./my-game

Copies assets/threejs-vite-game/, rewrites the project name, and gives the game its own visual test and canvas inspector. --force copies into a non-empty directory, overwriting files that collide with the scaffold and leaving everything else in place.