agentleFS
Bbeierle12Bbeierle12/Skill-MCP-Claude/skills/particles-router/SKILL.md

particles-router

Skill9 starsChanged 6 months agoMITView on GitHub

Decision framework for particle system projects. Routes to specialized particle skills (gpu, physics, lifecycle) based on task requirements. Use when building particle effects or needing guidance on which particle techniques to combine.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When multiple signals present, resolve by priority:

    line 31

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Particles Router

Routes to 3 specialized particle system skills based on task requirements.

Routing Protocol

  1. Classify — Identify particle effect type and scale
  2. Match — Find skill(s) with highest signal match
  3. Combine — Most particle systems need 2-3 skills together
  4. Load — Read matched SKILL.md files before implementation

Quick Route

Tier 1: Core (Always Consider)

Task TypeSkillPrimary Signal Words
Renderingparticles-gpupoints, instanced, buffer, shader, thousands, performance
Motionparticles-physicsgravity, wind, attract, force, velocity, turbulence, collision
Spawningparticles-lifecycleemit, spawn, fade, trail, pool, birth, death, age

Signal Matching Rules

Priority Order

When multiple signals present, resolve by priority:

  1. Performance concern — "millions of particles" → particles-gpu first
  2. Motion type — "swirling", "attracted to" → particles-physics
  3. Emission pattern — "burst", "continuous", "trails" → particles-lifecycle
  4. Default — All three skills usually needed together

Confidence Scoring

  • High (3+ signals) — Route immediately
  • Medium (1-2 signals) — Include all three skills (typical)
  • Low (0 signals) — Ask: "Describe the particle effect you want"

Common Combinations

Basic Particle System (All 3 skills)

particles-gpu       → Buffer setup, shader rendering
particles-physics   → Gravity, basic motion
particles-lifecycle → Emission, fade out

Wiring: GPU provides rendering foundation, lifecycle handles spawning/death, physics adds motion.

Snow/Rain Effect (3 skills)

particles-gpu       → Points with texture
particles-physics   → Gravity, wind, turbulence
particles-lifecycle → Continuous emission, recycling

Wiring: Lifecycle emits continuously, physics handles falling + drift, GPU renders efficiently.

Explosion (3 skills)

particles-gpu       → Instanced or points rendering
particles-physics   → Radial velocity, drag
particles-lifecycle → Burst emission, fade + shrink

Wiring: Lifecycle bursts particles, physics applies outward force + slowdown, GPU handles scale.

Fire/Smoke (3 skills)

particles-gpu       → Custom shader with noise
particles-physics   → Upward force, turbulence
particles-lifecycle → Continuous emit, color gradient, size over life

Wiring: Lifecycle manages color/size curves, physics adds flicker motion, GPU renders with blend modes.

Swarm/Flock (2-3 skills)

particles-gpu       → Instanced mesh (if 3D shapes)
particles-physics   → Attractors, flow fields, separation
particles-lifecycle → (Optional) Population management

Wiring: Physics dominates with behavioral forces, GPU handles rendering.

Magic Trail (3 skills)

particles-gpu       → Points with glow shader
particles-physics   → Follow path, slight randomness
particles-lifecycle → Trail history, fade along length

Wiring: Lifecycle stores position history, GPU renders with alpha gradient.

Confetti (3 skills)

particles-gpu       → Instanced flat planes
particles-physics   → Gravity, tumbling rotation, air resistance
particles-lifecycle → Burst emission, ground collision death

Wiring: Physics handles realistic falling, lifecycle manages burst and cleanup.

Decision Table

Effect TypeGPU FocusPhysics FocusLifecycle Focus
Stars/sparklePoints, staticMinimalTwinkle (alpha)
Snow/rainPoints, textureGravity, windContinuous, recycle
FireShader, blendUpward, turbulenceColor/size curves
ExplosionHigh countRadial, dragBurst, fade
SmokeSoft shaderRise, curlSlow fade, grow
SwarmInstancedAttractors, fieldsSpawn/death
TrailLine or pointsPath followingPosition history
DustSmall pointsBrownianRandom spawn

Particle Count Guidelines

CountApproachSkills Priority
< 100Simple, any approachlifecycle > physics > gpu
100 - 1,000Points or instancedAll equal
1,000 - 10,000GPU-focusedgpu > physics > lifecycle
10,000 - 100,000GPU essentialgpu >> physics (shader) > lifecycle
> 100,000Full GPU/computegpu only, physics in shader

Skill Dependencies

particles-gpu (rendering foundation)
├── particles-physics (motion layer)
└── particles-lifecycle (management layer)
  • particles-gpu is always needed for rendering
  • particles-physics and particles-lifecycle are independent but complementary
  • For simple effects, you might skip physics OR lifecycle, rarely both

Fallback Behavior

  • Unknown effect → Start with all three skills
  • Performance issues → Focus on particles-gpu optimization
  • Motion problems → Deep-dive particles-physics
  • Spawning/timing issues → Focus on particles-lifecycle

Quick Decision Flowchart

User Request
     │
     ▼
┌─────────────────────────┐
│ Rendering particles?    │──Yes──▶ particles-gpu (always)
└─────────────────────────┘
     │
     ▼
┌─────────────────────────┐
│ Movement/forces needed? │──Yes──▶ + particles-physics
└─────────────────────────┘
     │
     ▼
┌─────────────────────────┐
│ Birth/death/emission?   │──Yes──▶ + particles-lifecycle
└─────────────────────────┘
     │
     ▼
Most effects need all 3 skills

Effect Recipes

Quick Start Templates

EffectStart With
Ambient dustgpu (points) + lifecycle (continuous)
Button sparklegpu (points) + lifecycle (burst, fade)
Character trailgpu + lifecycle (trail)
WeatherAll three
Magic spellAll three
Data visualizationgpu + lifecycle

Integration with Other Domains

Combined WithUse Case
shader-noiseTurbulent motion, organic shapes
shader-effectsGlow, chromatic aberration on particles
r3f-performanceOptimization, culling, LOD
gsap-fundamentalsScripted particle animations
audio-reactiveMusic-driven particle effects

Reference

See individual skill files for detailed patterns:

  • /mnt/skills/user/particles-gpu/SKILL.md
  • /mnt/skills/user/particles-physics/SKILL.md
  • /mnt/skills/user/particles-lifecycle/SKILL.md

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.