Leaderboard/Gaming/threejs-game-skills
Last commit on September 5, 2026·Created on June 14, 2026

majidmanzarpour/threejs-game-skills

A pipeline for generating game-ready 3D assets and animations for Three.js browser games.
Combined rank
#186
across all skills
In Gaming
#1
category rank
Stars
2.1k
+4.7% in last 7d
Forks
213
+4.9% in last 7d
Watchers
11
+10.0% in last 7d
Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
TL;DR

This skill enables indie developers to produce high-fidelity 3D models, characters, and environments using the Tripo API. It streamlines the transition from text or image prompts to functional GLB and FBX files, handling the technical overhead of rigging and animation retargeting.

By automating the creation of props, creatures, and terrain, it allows developers to build polished browser-based experiences with AAA-style graphics without requiring a full art team.

WHO IT'S FOR
Indie game developers
building polished browser games with AI assets
Technical artists
upgrading prototype visuals to premium browser graphics
Frontend engineers
debugging and profiling Three.js performance
Creative technologists
integrating AI-generated 3D and audio assets
Repository contents

9 skill files

Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.

Use this skill collection

Follow the documented setup, then try a first task.

I’m using

Install all skills for Codex with npx

Installs: Complete shared pack of nine Three.js game skills. · Codex

Before you start
  • A working npx command.
  1. In a terminal, install the complete pack globally for Codex.

    npx skills add majidmanzarpour/threejs-game-skills --skill '*' -a codex -g -y
README.md · Checked Sep 18, 2026skills/threejs-game-director/SKILL.md · Checked Sep 18, 2026

Give it something to do.

Suggested first task

Plan a first playable slice

Uses threejs-gameplay-systems

  • Replace <game-project-path> with the existing game project's path.
  • Replace <genre> with the intended game genre.
  • Replace <player fantasy> with the experience the player should feel.
  • Replace <target platform> with the intended desktop, mobile, or combined target.
Use threejs-gameplay-systems for the Three.js project at <game-project-path>. Based on the intended <genre>, <player fantasy>, and <target platform>, inspect the existing structure and produce a concise design brief, core-loop contract, and one representative level or encounter plan. Keep this to planning a first playable slice; identify the primary input, visible objective, early pressure, reward, failure feedback, and restart behavior, but do not implement changes yet.
Suggested first task

Review one HUD state

Uses threejs-game-ui-designer

  • Replace <HUD-state> with the gameplay, pause, settings, fail, win, loading, or touch-control state to review.
  • Replace <game-project-path> with the existing game project's path.
  • Replace <target-viewports> with the desktop and/or mobile viewport sizes that matter.
Use threejs-game-ui-designer to review the <HUD-state> in the Three.js project at <game-project-path> on <target-viewports>. Preserve the current visual style and scope. Inventory the information hierarchy, check text fit, overlap, safe areas, interaction states, and touch targets where applicable, then report the three highest-impact issues with focused recommendations. Do not redesign unrelated screens or edit files yet.
Suggested first task

Diagnose one reproducible game bug

Uses threejs-debug-profiler

  • Replace <observed-bug> with the exact visible failure and reproduction conditions.
  • Replace <game-project-path> with the existing game project's path.
  • Replace <run-command> with the project's documented local run command.
  • Replace <browser-url> with the local URL where the failure appears.
Use threejs-debug-profiler to diagnose <observed-bug> in the Three.js project at <game-project-path>. Reproduce it using <run-command> and <browser-url>, inspect console, page, and network errors, then check the relevant canvas, renderer, loop, camera, asset, timing, input, resize, or audio path. Report the root cause, supporting evidence, and the smallest appropriate fix, but do not edit files yet.