Skip to content

arjun988/blender-skills / .claude/skills/vfx-fx

vfx-fx

Verified

Cinematic and game VFX in Blender including smoke, fire, particles, trails, and Geometry Nodes FX setups via MCP.

VFX / FX

Readable effects. Controlled simulation domains. Game sprites vs cinematic volumes.

When to Use

  • Smoke, fire, dust, sparks, debris
  • Magic / sci-fi energy FX
  • Muzzle flashes, trails, impacts
  • Geometry Nodes driven particle systems

Path Decision

Game real-time → Meshes/cards/ribbons + emissive mats (+ GN)
Cinematic     → Mantaflow / particles / GN → render → comp
Hybrid        → Sim in Blender → bake flipbooks/meshes for engine

Workflow

Brief (silhouette + timing) → Proxy emitter → Sim/GN prototype
  → Art-direct motion → Materials/lights → Cache → Render/comp or export

Effect Types

TypeBlender Approach
Smoke/fireMantaflow domain + flow; keep domain tight
SparksParticle Newtonian + collision + trail
DebrisRigid body shards (physics-sim)
Magic ribbonsCurves / GN extrude + emissive
Dust hitShort particle burst + soft sprites

Domain Rules (Volume)

  • Domain only as large as needed
  • Resolution from low → high after motion approved
  • Open borders intentionally; avoid wasted empty voxels
  • Collection: COL_FX_[Shot]

Naming

  • Emitters: FX_Emit_[Name]
  • Domains: FX_Domain_[Name]
  • Caches: document frame range in brief

Game Export Notes

  • Prefer mesh cards / GN instances over volume export
  • Atlas flipbooks when baking fire/smoke for engines
  • Keep pivot at logical spawn point

Constraints

MUST DO

  • Approve motion at low res before high-res sim
  • Light FX intentionally (emissive + key)
  • Cache before final render

MUST NOT DO

  • Huge empty domains
  • Unbounded particle counts
  • Skip timing brief (start/peak/end frames)

Reference Guide

TopicReferenceLoad When
Fx Timing Briefreferences/fx-timing-brief.mdWhen needed
Volume Domain Rulesreferences/volume-domain-rules.mdWhen needed
Game Fx Exportreferences/game-fx-export.mdWhen needed
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: 471kUpdated Claude CodeCodexVerifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 322kUpdated Claude CodeCodexVerifiedInstall