Archify
Technical diagrams from plain English, validated before they render
About Archify
Archify is an agent skill that turns a codebase or a plain-English description of a system into a polished, explorable diagram, delivered as a single self-contained HTML file with no dependencies and no server. It covers five diagram types - architecture, workflow, sequence, data flow and lifecycle - and picks the right visual language for what you described. The reason it is worth separating from the wider pile of agent-skill repositories is that it is not a prompt. The model produces a typed JSON intermediate representation, that IR is validated, and only then is it compiled deterministically into HTML and SVG, so the diagram you get is a checked artifact rather than whatever the model felt like drawing.
That distinction matters in practice because diagram output is exactly where a language model quietly invents an edge that does not exist. Archify's own gallery publishes live artifacts with their validation results attached, and the project positions itself openly as a Mermaid alternative in its repository topics. The output is built to survive contact with the places engineers actually put diagrams: a dual-theme SVG that carries both variable sets plus a prefers-color-scheme rule, so one file dropped in a GitHub README follows the reader's theme; PNG, JPEG and WebP rasterised natively at up to 4x for slides and print; WebM for motion; and a clipboard button that puts a PNG straight into Slack, Notion or Figma. It is MIT licensed with nothing to buy. Two things to keep in mind: the public build is labelled a development version, and it is a single-maintainer project, though a very actively developed one.
You install it as a skill into whichever agent you already use - the documented paths cover Claude Code, Cursor, Codex CLI and OpenCode - with a single command. From then on you describe the system in chat, either by pointing the agent at a codebase or by explaining the architecture in prose, and ask for the diagram you want. The agent produces the typed IR, Archify validates it, and the compiler emits a self-contained HTML file. Refinement happens in the same conversation rather than in a diagram editor: asking for a component to be added, a box moved, or a colour changed regenerates the artifact. The rendered diagram is explorable rather than static, with progressive levels of detail, a semantic camera, and route playback that follows an authored path through the system one stop at a time so you can pin or share an exact moment. Exporting is a button, and the resulting file can be attached to an email or a pull request comment and opened in any browser.
- •Five Diagram Types - Architecture, workflow, sequence, data flow and lifecycle, each with its own semantic vocabulary rather than one generic box-and-arrow style
- •Validated Before It Renders - A typed JSON intermediate representation is checked first, so the diagram is a verified artifact instead of an unreviewed model output
- •Self-Contained HTML Output - One file, zero dependencies, no server or runtime, openable in any browser and attachable to a pull request
- •Export That Survives Real Use - PNG, JPEG and WebP rasterised natively at up to 4x, WebM for motion, and a dual-theme SVG that follows prefers-color-scheme in a README
- •Iterate By Chat - Refine with instructions like adding a cache or moving a service, with no diagram editor to learn
- •Four Presets and Coordinated Themes - Classic, Signal Flow, Blueprint and Editorial share one geometry contract, each with matched dark and light themes
Engineers who need an architecture diagram for a design document, an onboarding page or a pull request and do not want to spend an afternoon in a drawing tool, and teams whose diagrams go stale because updating them is manual. The validation step is the reason to prefer it over asking an agent for Mermaid directly, and the dual-theme SVG is the reason to prefer it over a screenshot of a whiteboard. It suits anyone already running a coding agent, since that is the delivery mechanism. It is not for you if you do not use an agent at all, because there is no standalone application, and it is not for teams who need pixel-level control over layout, since you are steering a compiler through prose rather than positioning nodes. The public build being labelled a development version is worth weighing if you need stability.
Pricing
No pricing page found
Free and MIT licensed. Installs as an agent skill with npx skills add, with documented paths for Claude Code, Cursor, Codex CLI and OpenCode. There is no paid tier and nothing on the site is for sale.
From the vendor pricing page, 2026-10-08
