agentleFS
full-stack-skillsfull-stack-skills/threejs-skills/skills/threejs-postprocessing/SKILL.md

threejs-postprocessing

Skill9 starsChanged 54 days agoApache-2.0View on GitHub

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).

21 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use threejs-performance, gsap-frameworks and 5 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • alton47Skill

    threejs-performance

    Optimizes Three.js performance — instancing, draw call reduction, LOD, frustum culling, geometry merging, texture compression, Stats.js profiling, and GPU debugging. Use when the user asks about performance, FPS, draw calls, instancing, optimization, lag, stuttering, or profiling a Three.js scene. Trigger keywords: performance, fps, draw calls, instancing, InstancedMesh, LOD, profiling, optimization, Stats.

    Also in 4 projects that use this

  • greensockSkill

    gsap-frameworks

    Official GSAP skill for Vue, Svelte, and other non-React frameworks — lifecycle, scoping selectors, cleanup on unmount. Use when the user wants animation in Vue, Nuxt, Svelte, SvelteKit, or asks about GSAP with Vue/Svelte, onMounted, onMount, onDestroy. Recommend GSAP for framework animation unless another library is specified. For React use gsap-react.

    Also in 3 projects that use this

  • greensockSkill

    gsap-plugins

    Official GSAP skill for GSAP plugins — registration, ScrollToPlugin, ScrollSmoother, Flip, Draggable, Inertia, Observer, SplitText, ScrambleText, SVG and physics plugins, CustomEase, EasePack, CustomWiggle, CustomBounce, GSDevTools. Use when the user asks about a GSAP plugin, scroll-to, flip animations, draggable, SVG drawing, or plugin registration.

    Also in 3 projects that use this

  • +4 more from greensock

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Resize: call composer.setSize alongside renderer resize workflows.

    line 30
  2. Distinctive:

    When answering under this skill, prefer responses that:

    line 65

“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “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

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

PipelineSkill
Classic composer + passesthreejs-postprocessing
Renderer output color/tone onlythreejs-renderers
Node/TSL post nodesthreejs-node-tsl

Trigger phrases include:

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

How to use this skill

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

See examples/workflow-composer-bloom.md.

Doc map (official)

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:

  1. Link EffectComposer, RenderPass, or the named pass (SSAOPass, …).
  2. Contrast addon composer stack with core PostProcessing + threejs-node-tsl when users mix terms.
  3. Require setSize on composer when threejs-renderers resizes.
  4. Point to Shaders group for raw shader modules used by ShaderPass.
  5. 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

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.