Agent skill
threejs-postprocessing
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. Use when building composer chains for bloom, SSAO, or other screen-space effects; not for basic renderer tone mapping alone (threejs-renderers).
Install this agent skill to your Project
npx add-skill https://github.com/partme-ai/full-stack-skills/tree/main/skills/threejs-skills/threejs-postprocessing
SKILL.md
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
ShaderPasswith 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.setSizealongside 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.infoto check draw calls and triangles. - Validate output — render a simple test scene through the composer first to verify passes work before adding complexity.
- 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
PostProcessingclass separately to avoid name collision confusion.
Example: EffectComposer with bloom and debugging
import * as THREE from 'three';
import { EffectComposer } from 'three/addons/postprocessing/EffectComposer.js';
import { RenderPass } from 'three/addons/postprocessing/RenderPass.js';
import { UnrealBloomPass } from 'three/addons/postprocessing/UnrealBloomPass.js';
const composer = new EffectComposer(renderer);
composer.addPass(new RenderPass(scene, camera));
const bloomPass = new UnrealBloomPass(
new THREE.Vector2(window.innerWidth, window.innerHeight),
1.5, // strength
0.4, // radius
0.85 // threshold
);
composer.addPass(bloomPass);
// Resize handler — must match renderer size
window.addEventListener('resize', () => {
renderer.setSize(window.innerWidth, window.innerHeight);
composer.setSize(window.innerWidth, window.innerHeight);
});
// Render loop: use composer.render() instead of renderer.render()
function animate() {
composer.render();
}
renderer.setAnimationLoop(animate);
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
setSizeon 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
- https://threejs.org/docs/#Postprocessing
- https://threejs.org/docs/EffectComposer.html
- https://threejs.org/docs/RenderPass.html
Keywords
English: effectcomposer, renderpass, bloom, ssao, ssr, outline, postprocessing, three.js
中文: 后期、EffectComposer、泛光、SSAO、SSR、屏幕空间、three.js
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
ocrmypdf-batch
OCRmyPDF batch processing skill — process multiple PDFs, Docker automation, shell scripting, and CI/CD integration. Use when the user needs to OCR many PDFs, set up automated OCR pipelines, or integrate OCR into workflows.
ocrmypdf-optimize
OCRmyPDF optimization skill — compress PDFs, configure PDF/A output, JBIG2 encoding, and lossless optimization. Use when the user needs to reduce PDF file size, create archival PDF/A files, or optimize OCR output.
ocrmypdf-image
OCRmyPDF image processing skill — deskew, rotate, clean, despeckle, remove border from scanned documents. Use when the user needs to improve scanned PDF quality, fix skewed pages, remove noise, or clean up scanned documents before OCR.
ocrmypdf-api
OCRmyPDF Python API and plugin skill — use OCRmyPDF programmatically from Python, integrate with applications, and extend with plugins (EasyOCR, PaddleOCR, AppleOCR). Use when the user needs to call OCRmyPDF from Python code, build OCR pipelines, or use alternative OCR engines.
ocrmypdf
OCRmyPDF core skill — add searchable OCR text layer to scanned PDFs, convert images to searchable PDFs, support 100+ languages via Tesseract. Use when the user needs to OCR a PDF, make a scanned PDF searchable, or extract text from scanned documents.
svelte
Guides Svelte and SvelteKit development including reactive components, stores, transitions, lifecycle hooks, SSR, file-based routing, and deployment. Use when the user needs to build Svelte components, create SvelteKit applications, implement reactivity patterns, or configure Svelte with Vite.
Didn't find tool you were looking for?