Three.js Fundamentals
Three.js scene setup, cameras, renderer, Object3D hierarchy, coordinate systems. Use when setting up 3D scenes, creating cameras, configuring renderers, managing object hierarchies, or working with transforms.
When to Use
- You need to set up the core structure of a Three.js scene.
- The task involves scenes, cameras, renderers, transforms, resize handling, or object hierarchy basics.
- You want foundational Three.js guidance before working on specialized topics like shaders or post-processing.
Core Workflow
- Confirm the request matches this skill's trigger, scope, and risk profile.
- Use the topic map to identify the relevant pattern, checklist, or example before writing detailed guidance or code.
- Load
references/full-guidance.md when implementation details, examples, anti-patterns, validation checks, or edge cases are needed.
- Apply only the relevant guidance instead of loading or repeating the entire reference by default.
- Verify the result against any validation checks, limitations, security notes, or platform constraints in the reference.
Topic Map
- Quick Start
- Core Classes
- Scene
- Cameras
- WebGLRenderer
- Object3D
- Group
- Mesh
- Coordinate System
- Math Utilities
- Vector3
- Matrix4
- Quaternion
- Euler
- Color
- MathUtils
- Common Patterns
- Proper Cleanup
Reference Map
references/full-guidance.md preserves the complete original guidance, including examples and detailed edge cases.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Progressive Loading
Keep this SKILL.md as the compact routing and workflow entrypoint. Load the reference file only when the user task requires the deeper implementation material.
1---2name: threejs-fundamentals3description: Three.js scene setup, cameras, renderer, Object3D hierarchy, coordinate systems. Use when setting up 3D scenes, creating cameras, configuring renderers, managing object hierarchies, or working with transforms.4license: MIT5---67# Three.js Fundamentals89Three.js scene setup, cameras, renderer, Object3D hierarchy, coordinate systems. Use when setting up 3D scenes, creating cameras, configuring renderers, managing object hierarchies, or working with transforms.1011## When to Use12- You need to set up the core structure of a Three.js scene.13- The task involves scenes, cameras, renderers, transforms, resize handling, or object hierarchy basics.14- You want foundational Three.js guidance before working on specialized topics like shaders or post-processing.1516## Core Workflow171. Confirm the request matches this skill's trigger, scope, and risk profile.182. Use the topic map to identify the relevant pattern, checklist, or example before writing detailed guidance or code.193. Load `references/full-guidance.md` when implementation details, examples, anti-patterns, validation checks, or edge cases are needed.204. Apply only the relevant guidance instead of loading or repeating the entire reference by default.215. Verify the result against any validation checks, limitations, security notes, or platform constraints in the reference.2223## Topic Map24- Quick Start25- Core Classes26- Scene27- Cameras28- WebGLRenderer29- Object3D30- Group31- Mesh32- Coordinate System33- Math Utilities34- Vector335- Matrix436- Quaternion37- Euler38- Color39- MathUtils40- Common Patterns41- Proper Cleanup4243## Reference Map44- `references/full-guidance.md` preserves the complete original guidance, including examples and detailed edge cases.4546## Limitations47- Use this skill only when the task clearly matches the scope described above.48- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.49- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.5051## Progressive Loading52Keep this `SKILL.md` as the compact routing and workflow entrypoint. Load the reference file only when the user task requires the deeper implementation material.