agentleFS
wrg32786wrg32786/aigent-design-system/skills/threejs-web-scene/SKILL.md

threejs-web-scene

Skill4 starsChanged 3 months agoMITView on GitHub

Build a production Three.js or React Three Fiber scene for a cinematic website when live geometry, shaders, lighting, or interaction are genuinely required.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Do not start here. Confirm model-viewer, Spline, video, or a sequence cannot satisfy the requirement.

    line 8
  2. Distinctive:

    Use React Three Fiber only inside an existing React product.

    line 44
  3. Very specific:

    Use GSAP or Theatre.js only when the scene has coordinated approved beats.

    line 48
  4. Distinctive:

    Test low-power mobile, reduced motion, WebGL failure, lost context, slow network, high-DPI screens, tab backgrounding, and page navigation.

    line 52

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Three.js Web Scene

Do not start here. Confirm model-viewer, Spline, video, or a sequence cannot satisfy the requirement.

Read

  • integrations/threejs/README.md
  • creative-production/pipelines/web-3d-assets.md
  • skills/web-3d-asset-pipeline/SKILL.md

Scene contract

Define:

  • user interaction
  • camera states
  • object states
  • lighting
  • scroll relationship
  • loading state
  • error state
  • reduced motion
  • mobile fallback
  • cleanup lifecycle

Minimum implementation

  • explicit renderer size
  • bounded device pixel ratio
  • color management
  • asset loading progress
  • resize handling
  • pause when offscreen
  • dispose geometry, materials, textures, and renderer
  • semantic content outside the canvas
  • keyboard-safe controls
  • poster fallback

Use React Three Fiber only inside an existing React product. Do not add React to a static page solely for the renderer.

Choreography

Use GSAP or Theatre.js only when the scene has coordinated approved beats. One system owns camera state.

Verify

Test low-power mobile, reduced motion, WebGL failure, lost context, slow network, high-DPI screens, tab backgrounding, and page navigation.

A beautiful scene that makes the page unusable is a failed implementation.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.