agentleFS
Sign inStart free
MRCalderon3DMRCalderon3D/everything-game-dev-code/skills/art-audio-content/vfx-pipeline/SKILL.md

vfx-pipeline

Skill105 starsChanged 8 months agoMITView on GitHub

Create VFX authoring and integration rules that preserve readability, style fit, and performance.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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:

    Create VFX authoring and integration rules that preserve readability, style fit, and performance.

    line 11
  2. Distinctive:

    create review checkpoints for style and readability

    line 28
  3. Distinctive:

    test effects under combat or stress conditions

    line 29
  4. Distinctive:

    Keep this skill aligned with the relevant rules layer and current project documentation.

    line 58
  5. Distinctive:

    If engine-specific constraints materially change the workflow, hand off to the matching engine skill or engine-specific reviewer.

    line 59

≈ “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

VFX Pipeline

Purpose

Create VFX authoring and integration rules that preserve readability, style fit, and performance.

Use When

  • combat or interaction effects are being built
  • VFX cost is escalating
  • readability is poor

Inputs

  • art bible
  • combat readability needs
  • engine constraints
  • performance budget

Process

  1. define effect categories and quality bars
  2. separate gameplay-critical clarity from decorative layers
  3. set cost expectations for particles, materials, lights, and post-process
  4. create review checkpoints for style and readability
  5. test effects under combat or stress conditions

Outputs

  • VFX guide
  • cost tiers
  • readability checklist
  • integration notes

Quality Bar

  • is usable by content creators without tribal knowledge
  • respects quality bars and runtime constraints together
  • defines validation and ownership for content flow

Common Failure Modes

  • style consistency that ignores gameplay readability
  • manual pipeline steps that create drift
  • content that cannot be validated before release

Related Agents

  • technical-artist
  • combat-designer
  • performance-reviewer

Related Commands

  • combat-design
  • verify
  • perf-budget

Notes

  • Keep this skill aligned with the relevant rules layer and current project documentation.
  • If engine-specific constraints materially change the workflow, hand off to the matching engine skill or engine-specific reviewer.

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.

Check your setup, free