Archify

Archify is an agent skill that compiles a typed JSON IR into architecture, workflow, sequence, data-flow, and lifecycle diagrams as one HTML file. The repo tt-a1i/archify is JavaScript, MIT, created 2026-04-15. On 2026-09-18 GitHub listed 65,850 stars and 4,399 forks. The project page is tt-a1i.github.io/archify. 65,850 stars is a heat signal, not traffic. README that day named development version v2.17.0-dev.1.

Agents write JSON. Archify validates schema, layout, routes, and label clearance, then atomically replaces the last good HTML. It is not a Mermaid theme and not a drawing editor. Compare Mermaid Visualizer if you wanted Markdown diagrams, or Excalidraw Diagram if you wanted a sketch. Hosts include Claude Code, Codex CLI, Cursor, and OpenCode.

Install: npx skills add tt-a1i/archify -g. No repository is required; you can describe a system in chat.

Key Features

• Five diagram types: architecture, workflow, sequence, data flow, lifecycle. Optional architecture deployment-ownership fails closed when owners or regions are missing.
• Deterministic HTML/SVG: four visual presets, dark/light, finite motion that respects prefers-reduced-motion. Export PNG, SVG, WebM, and 1200x630 share cards.
• Architecture Delta: compare two validated snapshots as Before / Delta / After with added, removed, changed, moved, and rerouted facts. node archify/bin/archify.mjs compare ...
• Grounded viewer: search nodes, trace authored upstream/downstream reach and exact routes, compare roles, play named stories. It does not invent topology or claim runtime impact.
• Source evidence on request: architecture nodes can open Git-verified files and line ranges pinned to one public commit. Ordinary artifacts stay source-free.
• Last-good preview: optional loopback desktop watch reloads only after every gate passes.

Limitation: automatic Mermaid parsing, general auto-layout, hosted sharing, and WYSIWYG editing are out of scope. Claude.ai upload depends on Node in the sandbox. An optional update check may GET a stable manifest (IP and time only, per README); set ARCHIFY_UPDATE_CHECK_DISABLED=1 to disable it.

Use Cases

• Explain a runtime path from a repo: 8-12 components, one primary path, trust boundaries.
• PR architecture review: Delta before merge, without claiming merge safety.
• Cache-miss or auth sequence that has to stay faithful to authored calls.

Skip it if you only need a quick Mermaid flowchart in a Markdown file.

Pricing

Getting Started

1. npx skills add tt-a1i/archify -g
2. In chat: Use Archify to draw: Browser -> API -> Redis cache -> PostgreSQL fallback.
3. Refine: add Redis, highlight the rollback path.
4. For a repo: ask for 8-12 core components and one primary path, detail in cards not extra edges.

First-party start: the project page, SKILL.md, and Proof Lab.

Frequently Asked Questions

Is this Mermaid?

No. Typed JSON IR plus a renderer. Mermaid parsing is intentionally out of scope.

Does the viewer invent extra edges?

The README says focus, reach, routes, lenses, and stories reuse authored nodes and relationships.

Can I run it without an agent?

Yes. node archify/bin/archify.mjs validate|preview|deliver ... after cloning. Node ^22.19.0 || >=24.0.0 is listed for the DeepSeek Harness plugin; confirm current README for the core CLI.

Alternatives

• Mermaid Visualizer: text to Mermaid, Obsidian/GitHub friendly.
• Excalidraw Diagram: hand-drawn boards, not validated IR.
• Claude Code: a host that can load Archify.
• OpenCode: another host listed in the agent switcher.

Tips

1. Put supporting detail in cards. Extra edges make the layout worse.
2. Use validate --json / deliver --json and only apply supportedFixes.
3. Disable the update check if you do not want the reminder GET.

Conclusion

Archify is for diagrams you can present and still trust: typed source, gates before replace, one HTML file. Use it when a Mermaid sketch is not enough. Stay on Mermaid if you only need a flowchart in a README.