agentleFS
Sign inStart free
381487190381487190/opengod/skills/seedance/seedance-vfx/SKILL.md

seedance-vfx

Skill0 starsChanged 3 months agoMITView on GitHub

This skill should be used when the user asks for VFX, particles, energy, destruction, transformation, weather effects, magical effects, explosions, smoke, fire, water, or physically plausible effects in Seedance 2.0.

2 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

Create a free account to mount
Files
SKILL.md

seedance-vfx

VFX prompts need material behavior, source, timing, and consequence. Treat every effect as physical: it starts somewhere, interacts with light and objects, changes over time, and ends in a visible state. Avoid generic words such as magical, explosive, or cinematic unless they are translated into particles, fluids, smoke, light, debris, deformation, or energy behavior.

Intent

The user wants wonder, and wonder dies the moment it stops obeying physics. This skill's purpose is magic with a budget of cause and effect: every effect has a source, a journey, and an ending, so the impossible reads as witnessed rather than rendered.

Effects Contract

State: effect source, material, motion path, interaction with light, interaction with objects, dissipation, and endpoint.

EffectPrompt-ready phraseStability note
Product particlesgold dust particles spiral from behind the logo, catch the backlight, then settle on the tableKeep logo and bottle rigid.
Energythin blue electrical arcs crawl along the cable, briefly illuminating fingerprints on the plugKeep arcs attached to source.
Smokecold white vapor rolls over the rim, sinks down the glass, and thins near the tabletopDescribe density and direction.
Transformationpaper edge chars inward from the corner, flakes curl and fall, final logo remains untouchedProtect identity anchor.
Weatherwind pushes rain diagonally across the frame, puddles ripple outward from each stepTie weather to surfaces.

VFX Integration Rules

Use one hero effect per clip. Anchor the source to a clear object or body part. Make the effect respect gravity, wind, collision, reflection, and occlusion. For VFX near faces, hands, logos, or text, keep the core identity stable and place the effect around it rather than through it.

Timing and Dissipation

Effects need an endpoint: settle, fade, evaporate, freeze, collapse, glow out, or leave residue. If the effect is complex, use a three-step timing phrase: forms -> travels -> dissipates. Avoid perpetual effects with no consequence because they often become noisy overlays.

Output Contract

Return the VFX contract, stability constraints, and a compact prompt-ready phrase.

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