RandallLiuXin/GodotMaker / skills/reviewer/particles
particles-review
VerifiedReviews Godot Particles implementation for known pitfalls. Triggers AFTER implementation, when code involves GPUParticles2D, GPUParticles3D, CPUParticles2D, CPUParticles3D, ParticleProcessMaterial, trail_enabled, sub-emitters, GPUParticlesCollision, or particle amount/emission control. Do NOT use this skill for planning or teaching — only for post-implementation review.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.4 KB |
| checklist.md | markdown | 2.1 KB |
| gotchas.md | markdown | 4.4 KB |
SKILL.md
View on GitHub---
name: particles-review
description: |
Reviews Godot Particles implementation for known pitfalls.
Triggers AFTER implementation, when code involves GPUParticles2D, GPUParticles3D,
CPUParticles2D, CPUParticles3D, ParticleProcessMaterial, trail_enabled,
sub-emitters, GPUParticlesCollision, or particle amount/emission control.
Do NOT use this skill for planning or teaching — only for post-implementation review.
---
# Particles Review
Post-implementation reviewer for Godot particle code. Checks against known gotchas that LLMs consistently get wrong.
## When to trigger
After particle-related code is written or modified. Look for:
- Particle nodes (GPUParticles2D, GPUParticles3D, CPUParticles2D, CPUParticles3D)
- ParticleProcessMaterial or `shader_type particles`
- Trail configuration (`trail_enabled`, `use_particle_trails`)
- Sub-emitter setup (`sub_emitter_mode`, `sub_emitter_*`)
- Collision nodes (GPUParticlesCollisionBox3D, GPUParticlesCollisionSphere3D, etc.)
- Runtime particle property changes (`.amount`, `.emitting`)
## Review process
1. Read `gotchas.md`
2. Scan the implemented code against each gotcha
3. For each hit:
- Cite the gotcha ID (e.g. G1)
- Show the offending code
- Provide the fix
4. If no hits, report clean
5. Optionally run `checklist.md` static checks for automated verification
When you need specific API details, delegate to the **godot-api** skill.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |