SkillAgentSearch skills...

threejs-gameplay-systems

Build and iterate playable Three.js game systems: starter scaffold, architecture, design briefs, core loops, level and encounter design, entities, input, camera, collision and physics, scoring, objectives, and game feel.

Install / Use

npx skills add majidmanzarpour/threejs-game-skills --skill threejs-gameplay-systems

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

86/100

Category

Other

Supported Platforms

Universal

Our assessment of threejs-gameplay-systems

threejs-gameplay-systems scores 86/100 on our quality scale, 165th of 330 Other skills we index (top 50%).

Its SKILL.md is 5.4 KB long, well organised into 8 sections with 1 code example: a solid amount of guidance for an agent.

With 2,124 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
17/20
Description
15/15
Adoption
14/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so threejs-gameplay-systems is actively maintained.
  • Our last check on 2026-11-03 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-30. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

threejs-gameplay-systems compared with similar skills

All 4 of these similar skills score higher than threejs-gameplay-systems; compare them before choosing.

SkillScoreStarsUpdatedFormat
threejs-gameplay-systems (this skill)by majidmanzarpour862.1k2mo agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
rufloby ruvnet10081.9ktodayCLAUDE.md
headroomby headroomlabs-ai10079.8ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md

Frequently asked questions

How do I install threejs-gameplay-systems?
Run npx skills add majidmanzarpour/threejs-game-skills --skill threejs-gameplay-systems. The install tabs above show the steps for each supported agent.
Which AI agents does threejs-gameplay-systems work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is threejs-gameplay-systems safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is threejs-gameplay-systems still maintained?
The repository was last updated about 2 months ago, so threejs-gameplay-systems is actively maintained.

name: threejs-gameplay-systems description: "Build and iterate playable Three.js game systems: starter scaffold, architecture, design briefs, core loops, level and encounter design, entities, input, camera, collision and physics, scoring, objectives, and game feel. Use for first playable slices, new Vite/TypeScript/Three.js setups, level/arena/track/wave/hole/puzzle design, combat encounters, difficulty tuning, and juice."

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.

Design first

For broad game creation or a substantial design change, write three short artifacts or update the existing ones. A narrow mechanic fix uses the existing design and preserves unrelated systems:

Design brief. Player promise (the fantasy in one sentence) · target feeling · primary verb · secondary verbs · what the player repeats every 5–30 seconds · what changes across 1–5 minutes · how they lose, learn, and restart · what is rewarded and what creates risk · what a better player does differently · how the next decision is communicated · non-goals for this slice.

Core loop contract. Player does [verb] to achieve [objective] while [pressure] creates risk; success gives [reward], failure causes [cost/retry]. Then prove each clause in code: the verb is mapped to real input, the objective is visible in world or HUD, pressure exists inside the first playable minute, reward changes state rather than only visuals, failure teaches what happened, and restart is fast enough to invite another attempt.

Level or encounter plan. Spatial format · what the camera can and cannot see · player start, first decision, first threat, first reward · landmarks · how challenge escalates every 20–60 seconds or per wave/hole/lap · recovery beats · how hazards are telegraphed · which pieces are modular or parameterized.

"Explore a cool scene" is not a design brief. A brief needs decisions, pressure, feedback, and consequence.

Build

  1. Inspect existing structure, scripts, dependencies, loop, input, camera, entities, state, UI, diagnostics.
  2. Keep small ownership boundaries: core, game, entities, systems, assets, ui, tests.
  3. Implement in playable increments — input, state, entity, collision, feedback, HUD and audio hooks, diagnostics — so something is playable at every step. Establish one representative encounter at the intended camera scale with the actual hero and feedback before expanding content. Enemy, reward, and prop variety should serve the genre's decisions, not a universal asset quota.
  4. Tune feel: movement, acceleration, camera follow and FOV, hitstop, impact feedback, cooldowns, difficulty, restart.
  5. Keep hot paths allocation-light and update order explicit.
  6. Route all gameplay randomness through the scaffold's seeded RNG so the deterministic test hooks keep working.

For coordinated work, define input intents, entity/asset interfaces, and events before delegating independent modules. Report changed behavior and local checks to the lead, who owns the consolidated browser pass. When a user changes requirements, update the existing brief and pending tasks instead of restarting completed work.

Gameplay code emits audio events; threejs-audio-generator produces the actual assets and the runtime audio matrix.

Stack

TypeScript, Vite, Three.js modules, three/addons/... for official controls, loaders, and post-processing. lil-gui for live-tuned constants. Web Audio for runtime playback. Physics engine choice, timestep, and collider strategy follow references/physics-engine-selection.md — Rapier by default when the game needs real simulation.

What goes wrong

A static demo instead of a playable loop · mechanics bolted onto a scene that was built first · a core loop described but never proven through real input, pressure, reward, and fail/retry · a track or arena that decorates rather than shapes decisions · a mechanic that compiles but no input can trigger · camera and controls that lag or hide the next decision · state changes that never reach UI, audio, or VFX · abstractions built before any mechanic needed them.

Report

Behavior and controls, the three design artifacts for broad builds, architecture choices and tuned values, changed files, and what you saw when you played it. Note the physics engine, timestep, and collider strategy when physics is in scope.

Related Skills

View on GitHub
GitHub Stars2.1k
CategoryOther
Updated2mo ago
Forks216

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions