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

AI USE CASES

How to add light motion to a diagram that explains steps in order with diagram-design

Turn on optional motion so a process diagram reveals its steps one after another.

Who it is forTechnical writer or educator presenting a process (request flow, pipeline) where order matters

The problemA static diagram shows all steps at once, which makes sequences harder to follow in a talk or doc.

The outcomeAn HTML diagram with optional motion that walks a viewer through the steps in order, with a static version still available.

What you need first

  • An Agent Skills compatible host such as Claude Code, Codex, Cursor, Qoder, GitHub Copilot, Gemini CLI, Cline, Windsurf or Amp
  • Node.js for the npx install command
  • A browser to open the generated HTML file
  • Optional: a public website URL for brand onboarding

Steps

  1. Install the skill with: npx skills add cathrynlavery/diagram-design
  2. Ask your agent to draw an ordered process and request optional motion for it.
  3. Open the HTML file in a browser and check that the steps appear in the intended order.
  4. Keep the static version as the default for places where motion is not wanted.

Prompt for your agent

Use diagram-design to draw <process name> as an ordered diagram with the optional motion enabled. Confirm the step order is right and keep a static version alongside it.

Caveat. The README says static HTML is the default and motion is optional for ordered explanations only, so it will not suit every diagram type.

About diagram-design

An agent skill that draws clean diagrams as a single HTML and SVG file in your brand. Part of this week's top 10 repos: ranked #8 on Repo Radar. View cathrynlavery/diagram-design on GitHub.

More with diagram-design

See all use cases for cathrynlavery/diagram-design

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