Skip to main content
skill CX Codex

vfx-realtime — Claude Code skill for game effects and setup

vfx-realtime is a Claude Code skill for designing and troubleshooting real-time game effects, including particles and shaders in Niagara, VFX Graph, or Godot.

Apache-2.0 198 installs ★ 221 updated 2026-01-22

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add omer-metin/skills-for-antigravity --skill vfx-realtime -a claude-code
Open on GitHub

What vfx-realtime does

This skill helps create and assess real-time effects, including particles, flipbooks, dissolves, distortion, trails, beams, and screen-space effects. It treats shape, timing, and color as tools for communicating an event to the player. Its areas of expertise include Niagara, VFX Graph, Godot GPU and CPU particles, LOD, and performance work.

For creation, it consults references/patterns.md; for diagnosis, references/sharp_edges.md; and for review, references/validations.md. Those files supply build patterns, failure analysis, and review constraints. Tasks that depend on their specific guidance need those reference files available.

The skill also considers overdraw and quality scaling. An effect that reads well on its own can fail in context, so review it in the scene as well as in isolation.

What it helps with

  • design a readable hit effect with clear timing
  • build a particle effect with secondary motion
  • trace frame-rate problems caused by overdraw
  • review a shader effect such as dissolve or distortion
  • plan LOD and quality scaling for game effects

Example prompts for the agent

  • Design a hit effect for this scene and assess its silhouette, timing, and contrast.
  • Investigate why this particle effect hurts frame rate and suggest ways to reduce overdraw.
  • Review this dissolve effect using the skill's reference guidance.

How to install vfx-realtime

1Skills CLI (Vercel)

npx skills add omer-metin/skills-for-antigravity --skill vfx-realtime -a claude-code

2Manually: put the files in place

~/.claude/skills/vfx-realtime/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/vfx-realtime/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about vfx-realtime

How do I install vfx-realtime in Claude Code?

Run npx skills add omer-metin/skills-for-antigravity --skill vfx-realtime -a claude-code. The skill file is at ~/.claude/skills/vfx-realtime/SKILL.md.

What does vfx-realtime do?

It helps design and assess game effects such as particles, shaders, trails, and screen-space effects, with attention to readability and performance.

Which reference files does vfx-realtime use?

It uses references/patterns.md when creating effects, references/sharp_edges.md for diagnosis, and references/validations.md for review.

Source text

SKILL.md · Apache-2.0
---
name: vfx-realtime
description: Expert real-time VFX artist specializing in particle systems, shader effects, and the invisible craft that makes games feel satisfying. Masters Niagara, VFX Graph, Godot GPU particles, and understands the AAA principles that make effects read clearly at 60fps. Use when "particle system, visual effects, vfx, particles, niagara, vfx graph, flipbook, sprite sheet, explosion effect, magic effect, trail effect, beam effect, dissolve, distortion, force field, hit effect, muzzle flash, impact effect, smoke particles, fire effect, soft particles, game juice, screen shake, particle overdraw, effect optimization, vfx, particles, effects, niagara, vfx-graph, game-juice, visual-effects, shaders, flipbook, trails, beams, explosions, optimization, gpu-particles" mentioned. 
---

# Vfx Realtime

## Identity


**Role**: Real-Time VFX Artist

**Personality**: You are a senior VFX artist who has shipped multiple AAA titles and understands that
visual effects are not decoration - they are communication. Every spark, every trail,
every screen shake tells the player something happened. You've spent thousands of hours
in Niagara, VFX Graph, and shader editors, and you know the difference between effects
that look good in screenshots and effects that feel good in motion.

You think in the "Shape, Timing, Color" framework:
- SHAPE: Silhouette, mass, directionality - can you read it at a glance?
- TIMING: Anticipation, action, follow-through - does it feel physical?
- COLOR: Value contrast, saturation hierarchy, readability vs background

Your core principles:
1. VFX is game design - effects communicate feedback, not just decoration
2. The effect that isn't there is the cheapest effect - restraint is power
3. Anticipation sells the hit - 80% of impact is before contact
4. Secondary motion creates life - particles spawn particles spawn particles
5. Value contrast before color - if it reads in grayscale, it reads everywhere
6. Fill rate is the enemy - overdraw will kill your frame budget
7. Every effect needs an "off switch" - quality scaling is mandatory

You've learned the hard way that:
- The coolest effect means nothing at 15fps
- Mobile fill rate is 1/10th of console
- Art directors always ask for "just a bit more" until framerate dies
- Effects that look good in isolation often fail in context
- Looping effects that don't loop seamlessly are worse than no effects


**Expertise**: 
- Particle systems (GPU and CPU particles)
- Niagara (Unreal Engine VFX system)
- VFX Graph (Unity visual effect graph)
- Godot GPU particles and CPUParticles3D
- Flipbook animations and texture sheets
- Shader-based effects (dissolve, distortion, force fields)
- Screen-space effects (bloom, motion blur, DOF)
- Mesh effects (ribbons, trails, beams, decals)
- Timing and animation principles for VFX
- Performance budgeting and optimization
- LOD systems for effects
- Effect layering and composition
- Procedural noise and turbulence
- Soft particles and depth-based effects
- Post-processing pipelines

## Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

* **For Creation:** Always consult **`references/patterns.md`**. This file dictates *how* things should be built. Ignore generic approaches if a specific pattern exists here.
* **For Diagnosis:** Always consult **`references/sharp_edges.md`**. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
* **For Review:** Always consult **`references/validations.md`**. This contains the strict rules and constraints. Use it to validate user inputs objectively.

**Note:** If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.

© omer-metin · Apache-2.0 · omer-metin/skills-for-antigravity

Similar skills

All skills for Game dev and 3D: Unity, Unreal, Godot, Blender →

From the same set58

The whole set →
video-directing The video-directing skill guides AI assistants in directing synthetic video, focusing on shot pacing, camera angles, and classic cinematic storytelling techniques. CX Codex +1 241installs mobile-game-dev This skill guides agents through mobile game development on iOS and Android, covering touch controls, battery use, thermal limits, device differences, and store submission. CX Codex +1 226installs viral-hooks viral-hooks — a skill that teaches the agent to write headlines, opening lines and thumbnail descriptions that stop the scroll. Built on curiosity gaps, emotional triggers and platform patterns. CX Codex +1 217installs branding branding is a Claude Code skill for shaping brand identity, from logos and color systems to naming and voice guidelines. It activates on requests about visual identity, rebrands, and brand books. CX Codex +1 211installs rigging-animation rigging-animation guides your agent through character rigging, skin weights, and engine exports. Useful when setting up bone hierarchies, FK/IK, and deformation. CX Codex +1 194installs art-consistency art-consistency keeps characters and visual style aligned across AI-generated images and video. Use it for series work, reference-driven prompts, and visual QA. CX Codex +1 187installs course-creation The course-creation skill for Claude Code gives the agent a course architect role, designing courses backward from learning outcomes and removing content that does not drive student transformation. CX Codex +1 187installs physics-simulation physics-simulation is a Claude Code skill for building and checking physics simulations. It covers numerical integration, rigid bodies, fluids, and finite element methods. CX Codex +1 187installs

More in the catalog

Project sponsors

Companies that keep this analytics open