threejs-postprocessing

Original：🇺🇸 English

Translated

Addon screen-space post-processing for three.js using EffectComposer, Pass base class, RenderPass, and stock passes such as UnrealBloomPass, SSAOPass, SSRPass, BokehPass, OutlinePass, FXAAPass/SMAAPass, TAARenderPass, and ShaderPass; references the Shaders addon group for underlying shader modules; contrasts with core PostProcessing class used in node/WebGPU stacks (see threejs-node-tsl and threejs-renderers). Use when building composer chains—not for basic renderer tone mapping alone (threejs-renderers).

6installs

Sourcefull-stack-skills/threejs-skills

Added on2026-09-06

NPX Install

npx skill4agent add full-stack-skills/threejs-skills threejs-postprocessing

SKILL.md Content

View Translation Comparison →

When to use this skill

ALWAYS use this skill when the user mentions:

```
EffectComposer
```
,
```
RenderPass
```
, stacking passes, resize of composer
Bloom, SSAO, SSR, DOF, outline, glitch, film grain, TAA—addon pass names
```
ShaderPass
```
with shader modules from Addons Shaders group

IMPORTANT: postprocessing vs renderers vs node-tsl

Pipeline	Skill
Classic composer + passes	threejs-postprocessing
Renderer output color/tone only	threejs-renderers
Node/TSL post nodes	threejs-node-tsl

Trigger phrases include:

"EffectComposer", "RenderPass", "UnrealBloomPass", "SSAOPass", "后期"
"泛光", "环境光遮蔽", "描边"

How to use this skill

Chain:
```
RenderPass
```
→ effect passes → output; ensure size matches renderer and DPR changes.
Resize: call
```
composer.setSize
```
alongside renderer resize workflows.
Half-float: many passes expect appropriate render target types—cite docs for your version.
Performance: each pass has cost—profile with
```
renderer.info
```
sparingly.
Shader modules: link Addons Shaders list instead of inlining huge GLSL in SKILL.
Output: final pass should align color management with renderer (threejs-renderers).
Contrast: mention core
```
PostProcessing
```
class separately to avoid name collision confusion.

See examples/workflow-composer-bloom.md.

Doc map (official)

Docs section	Representative links
Postprocessing	https://threejs.org/docs/EffectComposer.html
Postprocessing	https://threejs.org/docs/RenderPass.html
Postprocessing	https://threejs.org/docs/UnrealBloomPass.html
Shaders (addon modules)	https://threejs.org/docs/module-CopyShader.html

Scope

In scope: Addon postprocessing passes and composer wiring; pointers to shader modules.
Out of scope: Custom full-screen pipeline design outside three docs; engine-level frame graphs.

Common pitfalls and best practices

Forgetting composer resize produces smeared or low-res effects.
Pass order matters—bloom often after main scene pass, outline may need masks.
Some passes need depth—ensure depth buffer availability per pass docs.

Documentation and version

Addon passes live under Postprocessing and Shaders modules in three.js docs. Pass constructors and required buffers change across versions—link the specific pass page (e.g.

UnrealBloomPass

) rather than guessing uniform names.

Agent response checklist

When answering under this skill, prefer responses that:

Link
```
EffectComposer
```
,
```
RenderPass
```
, or the named pass (
```
SSAOPass
```
, …).
Contrast addon composer stack with core
```
PostProcessing
```
+ threejs-node-tsl when users mix terms.
Require
```
setSize
```
on composer when threejs-renderers resizes.
Point to Shaders group for raw shader modules used by
```
ShaderPass
```
.
Warn about VR frame-time when stacking heavy passes (threejs-webxr).

References

Keywords

English: effectcomposer, renderpass, bloom, ssao, ssr, outline, postprocessing, three.js

中文： 后期、EffectComposer、泛光、SSAO、SSR、屏幕空间、three.js

能力边界

✅ 适用场景

当你需要使用此技能对应的技术栈时
当项目需要遵循最佳实践时
当需要快速上手或深入理解核心概念时

⚠️ 需要注意

复杂业务逻辑需要结合具体场景调整
性能优化需要根据实际数据量评估

❌ 不适用场景

不相关的技术栈或框架
需要完全自定义的特殊场景

常见陷阱 (Gotchas)

版本兼容性：注意框架版本与依赖库的兼容性，不同版本 API 可能有差异
配置文件格式：配置文件格式错误是最常见的问题，建议使用编辑器的语法检查
环境变量：确保所有必要的环境变量已正确设置，敏感信息不要硬编码
依赖冲突：多版本共存时注意依赖冲突，使用 lock 文件锁定版本
性能陷阱：大数据量场景下注意性能优化，避免 N+1 查询等常见问题

使用流程

Step 1: 环境准备

确保开发环境已安装必要的依赖和工具。

Step 2: 配置初始化

根据项目需求进行基础配置。

Step 3: 核心功能使用

按照示例代码实现核心功能。

Step 4: 测试验证

运行测试确保功能正常。

Step 5: 部署上线

完成开发后进行部署和监控。