← ClaudeAtlas

diagram-animatorlisted

Animate the arrows of a static diagram — a pulse travels along each connector in the direction the data flows, and nothing else in the image moves. Use this whenever someone wants to animate an architecture diagram, flowchart, system design, pipeline, or any "how it works" explainer image, including phrasings like "make this diagram move", "animate the arrows", "animate this schema for LinkedIn", "add motion to this architecture picture", or "turn this PNG into a GIF". Also use it when someone asks how to animate a diagram at all, even before they upload one. Do NOT use it for generating diagrams from scratch, for video editing, or for animating photographs.
nazboyko/claude-skills · ★ 1 · Data & Documents · score 69
Install: claude install-skill nazboyko/claude-skills
# Diagram Animator Takes a finished diagram image and animates it **without redrawing it**. Every effect is a brightness operation on pixels that are already in the image, so text stays crisp, icons stay unwarped, and the layout stays pixel-identical. That constraint is the entire point — generative image-to-video models melt small text, which is exactly what a technical diagram is made of. **Animate the arrows first, and by default only the arrows.** A diagram contains many true relationships but only a few matter to the story; motion is the strongest signal available, and spending it on glowing boxes dilutes the one thing the animation is for — showing where the data goes. Keeping every other pixel perfectly still is also what makes the movement readable at feed size. The one exception is **node icons**, and only in a step-through: revealing a node's pictogram as its step is reached says "this is happening now" using the same primitive as the arrows and adding nothing to the picture. See [Icons](#icons). Everything else — box halos, glowing panels, flashing headings — stays off. Output is a seamless loop as GIF and MP4. ## Workflow Four steps. The first happens before any code runs, and it is the one that decides whether the result is any good. ### 1. Look at the image and say what will move Open the image with the Read tool. Then tell the user, in a few sentences: - **are there arrows at all?** If the image has no connectors — a pure text infographic, a screensh