particles-router

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 Type	Skill	Primary Signal Words
Rendering	particles-gpu	points, instanced, buffer, shader, thousands, performance
Motion	particles-physics	gravity, wind, attract, force, velocity, turbulence, collision
Spawning	particles-lifecycle	emit, 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