The Problem

Claude Code and similar AI coding assistants have general programming knowledge but lack the specific Three.js API details needed to generate correct 3D code. Without curated reference material, they produce code with outdated constructor signatures, incorrect import paths, and missing performance patterns. This repo solves that by providing a set of skill files that give the assistant accurate, versioned API knowledge on demand.

What This Does

threejs-skills is a collection of 10 Markdown skill files under skills/, each covering one Three.js subsystem: threejs-fundamentals, threejs-geometry, threejs-materials, threejs-lighting, threejs-textures, threejs-animation, threejs-loaders, threejs-shaders, threejs-postprocessing, and threejs-interaction. Each file follows a consistent template with Quick Start, Core Concepts, Common Patterns, and Performance Tips sections.

The README states these are audited against Three.js r160+ documentation. The intended consumer is Claude Code, which loads skill files from .claude/skills when they match the request context.

How It Is Wired

The wiring has not been mapped for this repository yet. There is no code to trace — the repo contains only Markdown documentation. There is no execution path, no entry point, no function call graph, and nothing touches the network, filesystem, or a database at runtime.

Each file is self-contained. The only structural relationship is the naming convention: skills/<topic>/SKILL.md. The README's table maps each skill to its activation scenario (e.g., "Load a GLTF model" → threejs-loaders), but that mapping lives in the README, not in code. There is no dependency graph, no hub module, and no cycle to worry about.

How To Use It

Setup: The README documents two installation methods, both via git. Note the clone URLs in the README point to pinkforest/threejs-playground, not this repo — use the actual clone URL:

git clone https://github.com/moses-y/threejs-skills

Or add as a submodule:

git submodule add https://github.com/moses-y/threejs-skills

Configuration: No configuration files, environment variables, or build steps exist. The skill files are consumed by Claude Code from .claude/skills — the README implies you should copy or symlink the skills/ directory there, but it does not document the exact command.

Running it: There is no executable. The "run" is asking Claude Code to generate Three.js code; the skill files get loaded automatically based on context.

Real-World Use

A developer building a product configurator asks Claude Code: "Load a GLTF model with Draco compression and play its animations." Claude Code pulls threejs-loaders and threejs-animation from these skill files and generates code with correct DRACOLoader setup, AnimationMixer wiring, and error handling — instead of hallucinating an outdated API surface.

Code Health & Issues

Deep analysis has not run for this repo yet — it is 11 Markdown files with no code. Based on the structure:

  • Med - No LICENSE file - root. Usage and redistribution rights are unclear despite the repo being forked from a 3k-star project.
  • Med - No tests - repository-wide. No test files exist, though the README claims the skills were "audited against the official Three.js documentation." That audit is not reproducible from the repo.
  • Med - No CI/CD - no .github/ or CI config. Nothing validates the Markdown structure or the API claims in the skill files.

The README's clone URLs point to a different repository (pinkforest/threejs-playground), which will confuse anyone following the documented install path.

The Bottom Line

This is a content repo, not a codebase — there is nothing to build, test, or deploy. Its value is the curated Three.js reference material for AI assistants, which is genuinely useful if you work with Claude Code on 3D projects. The lack of a license and the stale clone URLs are the main practical concerns. Fork it, fix the URLs, and treat it as a reference library rather than a dependency.