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

How to draw a flowchart or architecture diagram as lint-clean SVG with SVG Diagram

Have your agent hand-place an SVG diagram in the house style and confirm it with svg-lint.

  • Top pick
  • Software and DevOps
  • Intermediate
  • 30 minutes
  • From the README
  • Claude Code
  • Codex
  • Cursor
  • Gemini CLI

Who it is forA developer writing a README or docs page who needs a diagram that matches a consistent style and renders on GitHub.

The problemAuto-layout tools choose positions you did not pick, and hand-written SVG drifts in spacing, fonts and arrowheads.

The outcomeA plain SVG file with every coordinate chosen and annotated, reported by svg-lint as 0 errors and 0 warnings.

What you need first

  • Node.js, since svg-lint is plain Node with no packages
  • A coding agent that loads skills, such as Claude Code, Codex, Cursor or Gemini CLI
  • npx, to run the skills install command

Steps

  1. Run npx skills add bybit-exchange/svg-diagram -g to install the skill for your agents.
  2. Start a new session and ask your agent for a diagram of your system, confirming it announces it is using SVG Diagram.
  3. Run node ~/.claude/skills/svg-diagram/tools/svg-lint/bin/svg-lint.mjs diagram.svg (this path applies to a Claude Code install).
  4. Fix each finding using its repair line, then rerun the linter until the output shows 0 errors, 0 warnings.

Prompt for your agent

Using the svg-diagram skill from bybit-exchange/svg-diagram, draw an architecture diagram of <system> as diagram.svg. Run node tools/svg-lint/bin/svg-lint.mjs diagram.svg and fix every finding until it reports 0 errors and 0 warnings.

Caveat. The linter is a maintainer tool that nothing runs for you, so you must invoke it yourself before handing a diagram over.

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