Skip to content
Back to search

fluxygram

MarketplaceWorks with Claude CodeGitHub

Fluxygram for Claude Code: create animated, step-by-step diagrams from JSON.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 19 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/Fluxygram/fluxygram with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/Fluxygram/fluxygram'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/fluxygram--fluxygram/badge.svg)](/listings/fluxygram--fluxygram)

HTML

<a href="/listings/fluxygram--fluxygram"><img src="/api/listings/fluxygram--fluxygram/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

npm install @fluxygram/element
import '@fluxygram/element'; // registers <fluxy-gram>

| Package | What it is | | --- | --- | | [`@fluxygram/element`](packages/element) | The `<fluxy-gram>` web component. Works in any framework, or none | | [`@fluxygram/core`](packages/core) | Format, validation, layout and motion. No DOM | | [`fluxygram`](packages/fluxygram) | Single-file build for `<script>` tags and CDNs | | [`@fluxygram/markdown`](packages/markdown) | ` ```fluxygram ` code blocks become diagrams. remark and markdown-it plugins | | [`@fluxygram/astro`](packages/astro) | Astro and Starlight integration | | [`@fluxygram/docusaurus`](packages/docusaurus) | Docusaurus plugin | | [`@fluxygram/mcp`](packages/mcp) | MCP server for AI agents (also hosted at `https://fluxygram.app/mcp`) |

Docs sites (Docusaurus, Astro, Starlight, VitePress, Next.js MDX) and Obsidian: see [integrations](https://docs.fluxygram.app/guides/integrations/).

The component picks English or Spanish from the page or browser language (the `lang` attribute wins when set).

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 16 lines
  1. {
  2. "name": "fluxygram",
  3. "description": "Fluxygram for Claude Code: create animated, step-by-step diagrams from JSON.",
  4. "owner": {
  5. "name": "Fluxygram",
  6. "url": "https://github.com/Fluxygram"
  7. },
  8. "plugins": [
  9. {
  10. "name": "fluxygram",
  11. "source": "./",
  12. "description": "Animated, step-by-step diagrams from JSON: flows, architectures, sequences, timelines and more.",
  13. "version": "0.1.0"
  14. }
  15. ]
  16. }
README.md · README · 220 lines
  1. <p align="center">
  2. <picture>
  3. <source media="(prefers-color-scheme: dark)" srcset=".github/assets/mark-on-dark.svg">
  4. <img src=".github/assets/mark-on-light.svg" alt="Fluxygram" width="72" height="72">
  5. </picture>
  6. </p>
  7. <h1 align="center">Fluxygram</h1>
  8. <p align="center">
  9. <strong>Diagrams that explain themselves.</strong><br>
  10. Describe anything in JSON; Fluxygram draws it and tells it step by step, with motion that helps people understand.
  11. </p>
  12. <p align="center">
  13. <a href="https://fluxygram.app">Website</a> ·
  14. <a href="https://fluxygram.app/play">Editor</a> ·
  15. <a href="https://docs.fluxygram.app">Docs</a> ·
  16. <a href="#for-agents">For agents</a> ·
  17. <a href="https://github.com/Fluxygram/fluxygram/discussions">Discussions</a> ·
  18. <a href="#español">Español</a>
  19. </p>
  20. <p align="center">
  21. <a href="https://www.npmjs.com/package/@fluxygram/element"><img src="https://img.shields.io/npm/v/@fluxygram/element?label=npm&color=2bff88&labelColor=16161c" alt="npm version"></a>
  22. <a href="https://github.com/Fluxygram/fluxygram/actions/workflows/ci.yml"><img src="https://github.com/Fluxygram/fluxygram/actions/workflows/ci.yml/badge.svg" alt="CI"></a>
  23. <a href="LICENSE.md"><img src="https://img.shields.io/badge/license-MIT%20%2B%20FSL-16161c" alt="License: MIT + FSL"></a>
  24. </p>
  25. <p align="center">
  26. <img src=".github/assets/demo-steps.gif" width="860" alt="A Fluxygram diagram telling, step by step, how a question becomes an animated diagram: blocks appear, a particle travels along each connection and the camera follows the story.">
  27. </p>
  28. ---
  29. ```html
  30. <script type="module" src="https://cdn.jsdelivr.net/npm/fluxygram@0.3"></script>
  31. <fluxy-gram src="order.flux.json"></fluxy-gram>
  32. ```
  33. ```json
  34. {
  35. "type": "flow",
  36. "title": "How an order gets processed",
  37. "nodes": [
  38. { "id": "start", "label": "Order received", "kind": "start", "icon": "cart" },
  39. { "id": "stock", "label": "In stock?", "kind": "decision" },
  40. { "id": "pay", "label": "Charge", "icon": "card" },
  41. { "id": "done", "label": "Delivered", "kind": "end", "accent": true }
  42. ],
  43. "edges": [
  44. { "from": "start", "to": "stock" },
  45. { "from": "stock", "to": "pay", "label": "yes" },
  46. { "from": "pay", "to": "done" }
  47. ]
  48. }
  49. ```
  50. That's a complete diagram. With no steps, it uses the default motion of its type; add `steps` to tell your own story.
  51. ## Diagram types
  52. | Type | Explains | Default motion |
  53. | --- | --- | --- |
  54. | `flow` | steps, decisions, pipelines, user journeys | the path builds column by column; a particle runs along each new edge |
  55. | `architecture` | systems, layers, services | layers appear bottom-up, then requests travel between services |
  56. | `timeline` | history, roadmaps, releases | the camera moves from milestone to milestone |
  57. | `tree` | hierarchies, org charts, categories | grows from the root, level by level |
  58. | `cycle` | loops, feedback, anything that repeats | each stage appears around the ring; at the end it all loops |
  59. | `sequence` | API calls, logins, protocols | participants appear, then each message crosses between lifelines |
  60. | `mindmap` | ideas around a topic, plans, syllabi | the central idea first, then one branch at a time |
  61. You can switch a diagram's type at any time without losing its nodes and connections.
  62. ## Telling the story
  63. Each step says what changes:
  64. | Field | What it does |
  65. | --- | --- |
  66. | `show` / `hide` | Elements that appear or disappear |
  67. | `flow` | A particle travels along these connections |
  68. | `highlight` | These nodes stand out, everything else dims |
  69. | `focus` | The camera moves in on a node or group |
  70. | `state` | `success`, `error`, `warning` or `pending` on nodes **and connections** (errors shake, pending spins) |
  71. | `caption` | The sentence under the diagram |
  72. | `duration` | Seconds this step stays on screen |
  73. | `notes` | Speaker notes, only visible to the presenter |
  74. `motion` sets the style for the whole diagram, or per block and connection: how things enter (`fade`, `scale`, `draw`, `slide`), how they travel (`particle`, `pulse`, `dash`, `packets`), the speed, and whether the camera follows the action. At the end, the camera pulls back to show the whole picture.
  75. Full documentation at **[docs.fluxygram.app](https://docs.fluxygram.app)**: every field, every type with live examples, the component API and guides. Also: [`SKILL.md`](skills/fluxygram/SKILL.md) (format and storytelling rules) and the [JSON Schema](https://fluxygram.app/schema/v1.json).
  76. ## Editor and presentation mode
  77. [fluxygram.app/play](https://fluxygram.app/play) is a canvas editor that runs entirely in your browser:
  78. - Drag blocks from the palette, drag from a block's dot to connect it, and edit everything in the side panel (or in the JSON tab, with live validation).
  79. - Build the story step by step: captions, states, timing and speaker notes.
  80. - Open or drop a `.flux.json`, download it, share a link (the diagram is compressed into the URL, no server involved) or export a single self-contained HTML file.
  81. - **Present** opens the diagram full screen for your audience. Press <kbd>N</kbd> for a second window with your notes, the next step and a timer.
  82. Dragging a block pins it (`x`, `y` in the JSON); everything else keeps its automatic layout.
  83. ## Live status (tracker mode)
  84. The same diagram can also show **where a real process is right now**: an order, a delivery, a support ticket, a job application. Your app sets the current stage; done stages turn green, the current one shows its status, and every change animates.
  85. ```html
  86. <fluxy-gram src="order.flux.json" mode="tracker" stage="shipped"></fluxy-gram>
  87. ```
  88. ```js
  89. tracker.setStage('delivered', 'success'); // status: pending | success | warning | error
  90. ```
  91. <p align="center">
  92. <img src=".github/assets/demo-live.gif" width="860" alt="Tracker mode: an order advances from Order placed to Delivered; each stage turns green as the next one becomes current.">
  93. </p>
  94. For branches that join or processes that loop back, pass `history` (the stages it went through). Try the live examples in the [gallery](https://fluxygram.app/gallery) and read the [tracker guide](https://docs.fluxygram.app/guides/tracker/): connecting it to your data, translations, ideas.
  95. ## Install
  96. ```bash
  97. npm install @fluxygram/element
  98. ```
  99. ```js
  100. import '@fluxygram/element'; // registers <fluxy-gram>
  101. ```
  102. | Package | What it is |
  103. | --- | --- |
  104. | [`@fluxygram/element`](packages/element) | The `<fluxy-gram>` web component. Works in any framework, or none |
  105. | [`@fluxygram/core`](packages/core) | Format, validation, layout and motion. No DOM |
  106. | [`fluxygram`](packages/fluxygram) | Single-file build for `<script>` tags and CDNs |
  107. | [`@fluxygram/markdown`](packages/markdown) | ` ```fluxygram ` code blocks become diagrams. remark and markdown-it plugins |
  108. | [`@fluxygram/astro`](packages/astro) | Astro and Starlight integration |
  109. | [`@fluxygram/docusaurus`](packages/docusaurus) | Docusaurus plugin |
  110. | [`@fluxygram/mcp`](packages/mcp) | MCP server for AI agents (also hosted at `https://fluxygram.app/mcp`) |
  111. Docs sites (Docusaurus, Astro, Starlight, VitePress, Next.js MDX) and Obsidian: see [integrations](https://docs.fluxygram.app/guides/integrations/).
  112. The component picks English or Spanish from the page or browser language (the `lang` attribute wins when set).
  113. ## For agents
  114. The skill in [`skills/fluxygram`](skills/fluxygram) teaches an agent the format, how to pick the diagram type and how to write good steps, plus a recipe for diagramming a whole codebase.
  115. **Claude Code**
  116. ```
  117. /plugin marketplace add Fluxygram/fluxygram
  118. /plugin install fluxygram@fluxygram
  119. ```
  120. **Cursor, Windsurf, Codex, Copilot and other coding agents**: save the skill in your project and point the agent at it.
  121. **MCP server** (Claude, Cursor, VS Code, Windsurf, any MCP client): connect `https://fluxygram.app/mcp`, or run `npx -y @fluxygram/mcp`. The agent can then validate its diagrams and give you a link to watch them. [Setup](https://docs.fluxygram.app/guides/mcp/).
  122. ```bash
  123. curl -o FLUXYGRAM.md https://fluxygram.app/skill.md
  124. ```
  125. **ChatGPT, Gemini, Claude.ai**: the [website](https://fluxygram.app/#agents) has a "Copy prompt" button for each one that includes the whole skill; paste the answer in the editor.
  126. ## Contributing
  127. Questions, ideas and diagrams go to [Discussions](https://github.com/Fluxygram/fluxygram/discussions); bugs and concrete requests to [issues](https://github.com/Fluxygram/fluxygram/issues/new/choose). Read [CONTRIBUTING.md](CONTRIBUTING.md) to set up the project and open a pull request. Contributors sign the [CLA](CLA.md) once, on their first PR. Security problems: [SECURITY.md](SECURITY.md).
  128. ```bash
  129. pnpm install
  130. pnpm dev # site, editor and presentation mode on http://localhost:5173
  131. pnpm typecheck
  132. ```
  133. | Path | What it is |
  134. | --- | --- |
  135. | `packages/core` | Format, validation, layout and motion. No framework, no DOM |
  136. | `packages/element` | `<fluxy-gram>` web component (SVG, CSS transitions, Web Animations) |
  137. | `packages/fluxygram` | Single-file build for CDNs |
  138. | `site` | Landing, editor, viewer and presentation mode (Vite), deployed on Cloudflare Workers |
  139. | `docs` | Documentation at docs.fluxygram.app (Astro Starlight), in English and Spanish |
  140. | `skills/fluxygram` | Agent skill and examples, also a Claude Code plugin (`.claude-plugin/`) |
  141. ## License
  142. - `packages/*`, `skills/fluxygram` and `docs`: **MIT**. Use, embed and ship them anywhere.
  143. - `site` (landing, editor, presentation mode): **FSL-1.1-ALv2**. Free to read, modify and self-host for your own use; not to offer as a competing commercial service. Every release becomes Apache 2.0 after two years.
  144. Details in [LICENSE.md](LICENSE.md).
  145. ---
  146. ## Español
  147. **Diagramas que se explican solos.** Describes cualquier cosa en un JSON y Fluxygram la dibuja y la cuenta paso a paso, con movimiento que ayuda a entender.
  148. - **Siete tipos de diagrama:** `flow` (procesos y decisiones), `architecture` (sistemas por capas), `timeline` (historia y roadmaps), `tree` (jerarquías), `cycle` (ciclos), `sequence` (quién le habla a quién, en orden) y `mindmap` (ideas alrededor de un tema). Cada uno se mueve a su manera, y se puede cambiar de tipo sin perder el contenido.
  149. - **Pasos opcionales:** sin ellos, el diagrama usa el movimiento de su tipo. Con ellos decides qué aparece, por dónde viaja la partícula, qué se resalta, a dónde va la cámara, los estados (éxito, error, advertencia, en progreso) en bloques y conexiones, el texto de cada paso y su duración.
  150. - **Editor visual** en [fluxygram.app/play](https://fluxygram.app/play): arrastras bloques, los conectas, armas la historia paso a paso y compartes un link, descargas el JSON o exportas un HTML. Todo pasa en tu navegador.
  151. - **Modo presentación:** el diagrama a pantalla completa para tu público y, con la tecla <kbd>N</kbd>, una segunda ventana con tus notas, el siguiente paso y un cronómetro.
  152. - **Estado en vivo (modo seguimiento):** el mismo diagrama muestra en qué etapa va un proceso real (un pedido, un domicilio, un ticket, una postulación). Tu aplicación cambia `stage` y el diagrama se anima: lo cumplido en verde, la etapa actual con su estado. Pruébalo en la [galería](https://fluxygram.app/gallery) y lee la [guía](https://docs.fluxygram.app/es/guides/tracker/).
  153. - **Para agentes:** la carpeta [`skills/fluxygram`](skills/fluxygram) le enseña a cualquier agente a escribir diagramas. En Claude Code se instala con `/plugin marketplace add Fluxygram/fluxygram` y `/plugin install fluxygram@fluxygram`; para ChatGPT, Gemini o Claude.ai, el sitio tiene un botón "Copiar prompt".
  154. - **Documentación** completa en [docs.fluxygram.app/es](https://docs.fluxygram.app/es/), con ejemplos en vivo de cada tipo.
  155. - **Paquetes en npm:** `@fluxygram/element` (el componente), `@fluxygram/core` (el formato) y `fluxygram` (un solo archivo para usar desde un CDN).
  156. - El sitio y el componente se muestran en inglés o español según el idioma del navegador.
  157. ### Contribuir
  158. Las preguntas e ideas van en [Discussions](https://github.com/Fluxygram/fluxygram/discussions) y los errores en [issues](https://github.com/Fluxygram/fluxygram/issues/new/choose), en inglés o español. La guía está en [CONTRIBUTING.md](CONTRIBUTING.md); en tu primer pull request firmas el [CLA](CLA.md) una sola vez.
  159. ### Licencia
  160. - `packages/*`, `skills/fluxygram` y `docs`: **MIT**. Se pueden usar, incrustar y distribuir en cualquier parte.
  161. - `site` (landing, editor, modo presentación): **FSL-1.1-ALv2**. Libre para leer, modificar e instalar para uso propio; no para ofrecerlo como un servicio comercial que compita. Cada versión pasa a Apache 2.0 a los dos años.
  162. Detalles en [LICENSE.md](LICENSE.md).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.