full-stack-skills/threejs-skills

threejs-materials

Classic three.js materials (non-Node): MeshStandardMaterial, MeshPhysicalMaterial, Phong/Lambert/Toon/Basic, Line/Points/Sprite materials, MeshMatcapMaterial, MeshNormalMaterial, depth/distance materials, ShaderMaterial and RawShaderMaterial.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/full-stack-skills/threejs-skills --skill threejs-materials

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

When to use this skill

ALWAYS use this skill when the user mentions:

  • Choosing among built-in mesh materials, map slots (albedo, normal, roughness, metalness, ao, emissive), envMap
  • Transparency sorting issues, alphaTest, depthWrite, blending modes, side/double-sided rendering
  • ShaderMaterial / RawShaderMaterial uniforms, includes, and compatibility with lights pipeline
  • Line, points, sprite materials for vector overlays and particles

IMPORTANT: classic materials vs node-tsl

NeedSkill
Standard PBR with maps, physical clearcoat/sheenthreejs-materials
TSL nodes, NodeMaterial, WebGPU-first shading, compute-style graphthreejs-node-tsl
Migrating ShaderMaterial → TSLthreejs-node-tsl (conceptual), keep ShaderMaterial here until cutover

Trigger phrases include:

  • "MeshStandardMaterial", "MeshPhysicalMaterial", "ShaderMaterial", "transparent", "alphaTest"
  • "PBR", "物理材质", "透明", "自定义着色器"

How to use this skill

  1. Select class by lighting model: MeshBasic (unlit), Lambert/Phong (legacy lit), Standard/Physical (PBR).
  2. Assign maps and ensure color space correctness for albedo vs data maps (link threejs-textures).
  3. Environment: set envMap from cube or equirect; align metalness/roughness; consider MeshPhysicalMaterial for transmission/IOR when needed.
  4. Transparency: order objects or use alphaTest/depthWrite trade-offs; mention sorting limitations.
  5. ShaderMaterial: minimize re-lit work unless intentional; document required lights and lights: true flag behavior per version docs.
  6. Performance: share materials across meshes; avoid cloning per frame.
  7. Skinning/morph: set skinning/morphTargets where applicable—mesh side in threejs-objects.

See examples/workflow-pbr-transparent.md.

Doc map (official)

Docs sectionRepresentative links
Materials (core)https://threejs.org/docs/Material.html
PBRhttps://threejs.org/docs/MeshStandardMaterial.html
Physicalhttps://threejs.org/docs/MeshPhysicalMaterial.html
Custom GLSLhttps://threejs.org/docs/ShaderMaterial.html

Scope

  • In scope: Non-Node materials listed under Core Materials in docs (except *NodeMaterial).
  • Out of scope: Full Nodes catalog (threejs-node-tsl); post pass materials inside composer (threejs-postprocessing).

Common pitfalls and best practices

  • Wrong normal map normalMapType or tangent space breaks lighting; verify geometry has tangents or use appropriate mode.
  • Premultiplied alpha vs straight alpha mismatches cause fringe halos on foliage.
  • MeshPhysicalMaterial transmission needs thickness and good env—combine with threejs-textures / PMREM.
  • Too many unique materials hurts sorting and batching—merge where possible.

Documentation and version

PBR and ShaderMaterial behavior track the Materials section in three.js docs. Color management and default envMap handling changed in modern releases—always pair material answers with renderer/output settings from threejs-renderers when colors look wrong.

Agent response checklist

When answering under this skill, prefer responses that:

  1. Link MeshStandardMaterial, MeshPhysicalMaterial, or ShaderMaterial pages as appropriate.
  2. Force a clear choice vs threejs-node-tsl when the user asks for “shaders” or “nodes”.
  3. Separate map roles (albedo vs roughness vs normal) and colorSpace expectations with threejs-textures.
  4. Call out transparency and depthWrite trade-offs for sorted rendering.
  5. Note that *NodeMaterial types belong to the node skill, not this one.

References

  • https://threejs.org/docs/#Materials
  • https://threejs.org/docs/MeshStandardMaterial.html
  • https://threejs.org/docs/MeshPhysicalMaterial.html
  • https://threejs.org/docs/ShaderMaterial.html

Keywords

English: meshstandardmaterial, meshphysicalmaterial, shadermaterial, pbr, transparency, envmap, materials, three.js

中文: 材质、PBR、MeshStandardMaterial、物理材质、透明、环境贴图、ShaderMaterial、three.js

同じリポジトリから

関連する Skills

すべての Skills
full-stack-skills
コミュニティ

threejs-audio

three.js audio spatialization: AudioListener attached to camera rig, Audio and PositionalAudio sources, AudioAnalyser for FFT/time-domain data, and integration with Web Audio API contexts; AudioLoader is referenced from threejs-loaders for file decoding. Use when placing 3D sound, configuring panner parameters, or visualization; not a replacement for full game audio middleware.

1時間の導入数
3
GitHub Stars
14
更新日
10月3日
full-stack-skills
コミュニティ

threejs-camera

three.js cameras: Camera base, PerspectiveCamera, OrthographicCamera, CubeCamera, ArrayCamera, StereoCamera; projection matrices, aspect, FOV, orthographic frustum sizes, near/far planes, and dynamic environment maps with CubeCamera. Use when placing views, rendering reflections, or multi-view splits; for XR projections and eye matrices use threejs-webxr; for post pass camera tricks use threejs-postprocessing alongside threejs-renderers.

1時間の導入数
3
GitHub Stars
14
更新日
10月3日
full-stack-skills
コミュニティ

threejs-controls

Addon camera and object manipulation controls: OrbitControls, MapControls, FlyControls, FirstPersonControls, TrackballControls, ArcballControls, DragControls, PointerLockControls, TransformControls; damping, target focal point, and integration with the animation loop. Use for editor-style navigation and gizmos—not a full game character controller stack; pair with Raycaster selection patterns in threejs-objects when transforming selections.

1時間の導入数
3
GitHub Stars
14
更新日
10月3日
full-stack-skills
コミュニティ

threejs-dev-setup

Bootstrap and toolchain guidance for three.js applications using npm, Vite/Webpack/Rollup, bare ESM import maps, and TypeScript. Covers canonical import paths for three core versus three/addons/ (examples/jsm re-exports), version alignment with https://threejs.org/docs/, and fixing "module not found" for loaders and controls. Use when scaffolding a new 3D project, migrating bundler, or debugging resolution of addons—do not use for rendering API details (see threejs-renderers) or asset loading lo

1時間の導入数
3
GitHub Stars
14
更新日
10月3日