DEDUPED We read 1,000+ AI sources. You read one email. Subscribe free

AI USE CASES

How to add live fire, water or light effects to a figure with anatomy

Ask for a figure that needs exhaust, ripples or glow and get WebGL effects inside the isometric drawing.

Who it is forEducator or designer making a physics or engineering explainer that needs motion effects

The problemFlat vector drawings cannot show fire, fluid or light in motion.

The outcomeA figure whose WebGL layer draws the effect in the same isometric camera as the SVG parts, like the README's engine plume and ripple tank.

What you need first

  • An agent that supports Agent Skills: Claude Code, Antigravity, OpenCode, Codex or MiniMax Code
  • Node.js 20.10 or later (the skills CLI itself may need a newer Node, 22.20 or later for version 1.7.1)
  • Model usage costs from your agent account; the kit has no extra API keys or npm dependencies
  • A browser to open the finished HTML pages (WebGL for the effects layer)

Steps

  1. Install the skill: npx skills add wheresryan22/anatomy -g
  2. Describe a machine that needs an effect, for example a rocket engine firing.
  3. Open the page and trigger the effect; check it sits inside the drawing.
  4. Test in a browser with WebGL enabled, since the SVG alone shows no effect.

Prompt for your agent

Use wheresryan22/anatomy to build a figure of <machine with fire, water or light> with a WebGL effect layer. Verify the effect lines up with the SVG parts and the figure still reads without WebGL.

Caveat. Shader effects need a browser with WebGL and can be slower on weak hardware.

About anatomy

An agent skill that builds interactive illustrations of machines and complex systems to explain an idea. Part of this week's top 10 repos: ranked #4 on Repo Radar. View wheresryan22/anatomy on GitHub.

More with anatomy

See all use cases for wheresryan22/anatomy

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page