DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to build a figure with a WebGL fire or water effect with Anatomy

Make an isometric explainer where a shader shows fire, water or light inside the drawing.

  • Content
  • Advanced
  • 45 minutes
  • From the README
  • Claude Code
  • Codex

Who it is forA science educator or lab content author who needs a figure where flame, water or light is part of the explanation.

The problemStatic SVG cannot show fire, water or caustics convincingly, so the physical effect gets lost.

The outcomeA figure where a WebGL shader renders the effect in the same isometric camera as the SVG parts.

What you need first

  • Node.js (the README says version 1.7.1 of the skills CLI asks for 22.20 or later)
  • Claude Code, Codex, or another supported agent with the skill installed
  • Headless Chrome, which the skill uses to check its own figures
  • No API keys and no npm install are needed, since the kit uses only Node's built-in modules

Steps

  1. Run npx skills add wheresryan22/anatomy -g -a claude-code to install the skill.
  2. Run /anatomy and describe the apparatus, naming the effect that needs a shader, such as a flame or water.
  3. Open the built HTML file and confirm the shader layer sits between the back and front SVG.
  4. Run node scripts/capture.mjs page.html --out shots/page.png to save a preview.

Prompt for your agent

Using the skill in wheresryan22/anatomy, build a figure of <apparatus> with a WebGL shader for <effect>. Expected output: an HTML file where the shader is inside the isometric camera. Verify that the SVG still renders with WebGL turned off.

Caveat. The README marks the 3D mode as beta, so stick to the SVG and WebGL tiers for production figures.

Share: X LinkedIn Hacker News Email Copy link

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