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

How to redraw existing Mermaid or draw.io diagrams in See Code style with See Code

Convert old diagram files into See Code diagrams, one per file, with an index page to browse them.

Who it is forA developer or architect who keeps diagrams as Mermaid, draw.io or similar source files and needs them consistent for a review or a deck.

The problemDiagrams created in different tools look inconsistent, and a document with many diagrams is hard to review.

The outcomeA folder of See Code diagrams named after their headings or pages, plus an index.html, and a short report of what was merged or dropped.

What you need first

  • A coding agent that supports Agent Skills, such as Claude Code, Cursor, Codex or OpenCode
  • Node.js, needed for the command-line SVG export
  • Chrome or Edge, needed only for command-line PNG, GIF or MP4 export

Steps

  1. Install See Code in your agent with npx skills add Aryanutkarsh/seecode -g or the Claude Code plugin commands
  2. Ask your agent to redraw the source file, for example docs/architecture.mmd, simplified for your audience
  3. Ask for a folder output if the file contains several diagrams, such as a design doc with multiple Mermaid blocks
  4. Open index.html in the output folder and check each diagram against the source
  5. Read the report of merged or dropped content before sharing the result

Prompt for your agent

Use the SeeCode skill from the Aryanutkarsh/SeeCode repo to redraw every diagram in <path to source file> as SeeCode diagrams in a folder. Expected output: one HTML file per diagram plus index.html. Verify that the count of diagrams matches the count of diagram blocks in the source and that the report lists anything dropped.

Caveat. See Code redraws the content with its own layout and style and does not carry over source colours, fonts or coordinates, so review each redrawn diagram against the original.

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