Skip to content
Skills Library
Programming · Building & coding

add-effects

/add-effects

Use when adding visual effects to a PlayCanvas app, to choose between particle systems, shader chunks, runtime meshes, and post-processing.

Repository
skills ↗
Licence
MIT
Last repository change
21.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 21.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when adding visual effects to a PlayCanvas app, to choose between particle systems, shader chunks, runtime meshes, and post-processing.

Original author description

Use when adding visual effects to a PlayCanvas app, to choose between particle systems, shader chunks, runtime meshes, and post-processing.

How it works

  1. Engine gotchas
Original SKILL.md headings · 27 lines, 178 words
SKILL.md preview
---
name: add-effects
description: Use when adding visual effects to a PlayCanvas app, to choose between particle systems, shader chunks, runtime meshes, and post-processing.
---

# Effects

Pick the Engine building block first, then adapt its closest official example with
`find-examples`:

- Particle systems: the `particlesystem` component (`graphics/particles-*` examples).
- Custom shading on existing surfaces: `StandardMaterial` chunk overrides
  (`override-shader-chunks`), or a `ShaderMaterial` when the effect needs its own shader pair.
- Procedural or per-frame geometry: a runtime-updated `Mesh` on a `render` component
  (`graphics/mesh-*` examples), or `WideLineRenderer` for lines with width.
- Full-screen effects: `CameraFrame` (`light-scene`).
- Gaussian splat effects: the shipped gsplat scripts (`reuse-scripts`).

## Engine gotchas

- `CurveSet` takes one key array per channel. A flattened array type-checks, then fails at texture
  upload.
- Create emitters and meshes at load and reuse them. Fire an emitter with `reset()` then `play()`;
  one-shots use `loop: false`.
- The first use of a shader stalls a frame. Render each effect once behind a loading screen.
- Animate values with `setParameter`, not a per-frame `material.update()`.
- A lit material on a custom mesh needs normals; otherwise use an unlit material.

Trigger each effect through the app's real inputs, and confirm repeated triggers keep entity counts
stable.

Versions

The database has no other skills named add-effects.

Database snapshot: 13.11.2026 · package version 7a4f822b2cd7 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 86override-shader-chunks
    Use when a PlayCanvas StandardMaterial needs custom shading its properties cannot express, such as stylized looks or vertex displacement, before writing a ShaderMaterial.
  • 90inspect-runtime
    Use when reading state from a running PlayCanvas app, to reach its live Application through the Engine devtools hook without changing app code.
  • 100shaders
    Write shaders in Godot using the shader language or Visual Shaders. Use this skill when creating visual effects, custom materials, post-processing, dissolve effects, outlines, water effects, particle shaders, or any GPU-based rendering customization.
  • 100shader-basics
    Use when implementing shaders — Godot shader language, visual shaders, common visual recipes, and post-processing effects
  • 100shader-effects-qa
    Use to validate visual shader effects, screenshots, color correctness, regressions and GPU budgets; not write base GLSL pipelines.
  • 100shader-basics
    Use when implementing shaders — Godot shader language, visual shaders, common visual recipes, and post-processing effects

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.