Odin Visual

Use when asked to render documentation as an interactive, navigable HTML canvas. Not for writing or restructuring docs.

Use when the user runs /embed-diagram to render a Mermaid diagram offline and embed it into a document. Not for code-derived diagrams or remote, credential, publish, deploy, or irreversible changes.

Use when a user asks for a zoomable PR map or graph-canvas orientation. Not for remote, credential, publish, deploy, or irreversible changes.

Use when asked to diagram, or a tool or --quick flag renders a structured spec to HTML. Modes: interactive, quick-render. Not for Excalidraw or documents: use visual-argument-diagram or embed-diagram.

Use when asked to visualize data movement, ETL or ELT, lineage, transformations, custody, governance, stores, sources, or consumers.

Use when asked for a call graph, class hierarchy, dependency map, containment or complexity view, or data-flow view. Not for embedding: use embed-diagram. Not for architecture: use visual-diagram.

Use when asked to render a PR review as a Cursor Canvas artifact or a standalone HTML page served on localhost (mode: html), with risky hunks foregrounded.

Use when a user asks to visualize a time-ordered interaction. Authors a typed sequence JSON spec and a self-contained interactive HTML artifact named by the user. Not for static architecture diagrams.

Use when a user requests a comparison table, data record, metric card, stepper, or mockup widget, a numeric chart, or an interactive explainer. Not for source or remote-system changes.

Use when a user asks to visualize a process, approval flow, runbook, CI/CD path, responsibility lanes, or tool calls. Not for remote, credential, publish, deploy, or irreversible changes.

Use when states, waits, retries, decisions, transitions, and terminals need a lifecycle view. Not for remote, credential, publish, deploy, or irreversible changes.

Use when the user asks for direction and a compilable 3D workflow from an interview. Not for remote, credential, publish, deploy, or irreversible changes.

Use when the user asks to visualize an architecture as a self-contained HTML artifact, or compare two architecture snapshots. Not for remote, credential, publish, deploy, or irreversible changes.

Use when asked to create a presentation, pitch deck, or slides from a topic and audience, or to format supplied source items into a 16:9 HTML slide deck. Not for PowerPoint files.

Use when the user explicitly names snipgrapher and wants code rendered to a polished PNG, SVG, or WebP at an explicit local path. Not for other renderers, publishing, or remote actions.

Use when a user wants a conceptual, workflow, or architecture diagram, a layout repair, or a PNG render of an existing .excalidraw file. Not for HTML or chat visuals: use visual-diagram or show-me.

Use when the user wants a cybernetic flow design document for an interactive system. Not for implementing or deploying the system.

Use when a user wants a looser conceptual graph for exploratory work. Not for remote, credential, publish, deploy, or irreversible changes.