Archify turns an agent prompt into a single interactive HTML diagram, and the agent does all the work

Installation is one sentence that sends your agent to llms.txt

Archify has no installer you run yourself in the quick start. You paste a single instruction into a supported agent, and the agent reads the project's llms.txt and sets the skill up:

Install Archify for me by reading https://raw.githubusercontent.com/tt-a1i/archify/main/llms.txt

The supported agents named up front are Cursor, Claude Code, Codex CLI and OpenCode, with more integrations under the installation options section and an integrations/ folder in the repository. Archify is also listed on skills.sh, and Kimi Work carries it in its plugin store under the name Interactive Architecture Diagram. The consequence of this design is that the install is only as reliable as your agent's ability to follow written instructions from a URL. If your agent cannot fetch remote files, this path does not work for you.

Diagrams are built and revised by conversation, not by editing a file

After install you describe the system in plain language. The project's own starter prompt is a cache-miss request path:

Use Archify to diagram a web request: Browser calls the API,
the API checks Redis, and a cache miss queries PostgreSQL and fills the cache.

From there you keep talking to it with follow-ups such as Add authentication, Highlight the cache-miss path, or Switch to the light theme. No repository is required; a description is enough. When you do point the agent at a repository, it can produce a source-backed architecture diagram, and the 35-second launch demo shows following source links and tracing a path through a mapped repo. The diagram types in the project description are architecture, workflow, sequence, data-flow and lifecycle, and the examples folder adds class, ERD, timeline, tree and waterfall renderings.

Explainer pages lead with the conclusion and pin repository excerpts to a commit

Not every question fits one diagram, so Archify can answer as a page it calls an explainer. The conclusion and its reasons come first, then one panel per question, using tables, steps, charts, code and validated diagrams. Steps sit beside the diagram they walk through and light up its parts as you read, and clicking a node opens the full interactive view.

Use Archify to answer as one page: our API's P99 went from 80 ms to 600 ms
while the mean barely moved. What is the likely cause, and how should we investigate?

Claims cite numbered sources, and repository excerpts are pinned to a commit and open in a source card. That makes checking possible, not automatic. The page tells you where a claim came from; it is still on you to open the source and confirm the agent read it correctly. You can ask about any single panel and get a follow-up prompt the agent uses to revise only that panel.

Output is one HTML file, and the exports are images or a printed PDF

Every result is a single self-contained HTML file with four styles and light or dark themes. Sharing means sending that file or hosting it. For people who will not open HTML, the export options are a PNG, WebP or JPG long image, or printing the page to PDF from the browser.

That list has a practical consequence. None of those outputs is an editable diagram source for another tool, so if your team keeps diagrams in a separate editor, Archify gives you a picture to paste, not a file to keep editing there. The motion and click-through behavior also only exist in the HTML; a PNG or a printed PDF loses the interactive view, the source cards and the per-panel follow-ups. Treat the HTML as the real artifact and the images as snapshots.

Only archify.si and the GitHub repository speak for the project

Archify is free and open source under Apache-2.0. Its official channels are archify.si and github.com/tt-a1i/archify, and the project states that third-party online services and paid plans are operated by their own providers and do not represent Archify. The README also carries a sponsor block for Kimi Work, Supercode, OpenLux and PackyCode, which are separate businesses.

For a reader this matters in two ways. A website charging for Archify under a similar name is not the project, and whatever it does with your prompts or repository is outside Archify's control. Second, sponsor offers such as discounted model credits are commercial arrangements between you and that sponsor. The repository root also includes LICENSE-MIT, NOTICE and THIRD_PARTY_NOTICES.md next to the Apache-2.0 LICENSE, so check those files if you plan to redistribute parts of it.

Without a capable agent, Archify does nothing on its own

Archify is a skill, so every step depends on the agent running it. The agent reads the install instructions, reads your repository when you ask for a source-backed diagram, writes the HTML, and applies your revisions. If the agent misreads a file or skips part of the codebase, the diagram will reflect that, and the polish of the output can make a wrong map look authoritative.

The practical response is the one the project builds in: source links on diagrams, numbered citations and commit-pinned excerpts on explainers. Use them. For a description-only diagram, such as the Redis and PostgreSQL example, there is no source to check against, so the diagram is exactly as accurate as the sentence you typed. Archify also provides a guide for creating and checking diagrams with your agent at archify.si/agent-diagrams.

Examples ship as JSON specs beside rendered HTML, checked by a Node 18 test suite

The examples folder pairs specification files with output, for instance rag-pipeline.architecture.json next to rag-pipeline.html, and checkout-platform-delta.html comes with a checkout-platform-delta.receipt.json. That pairing shows what the skill generates from, which helps if you want to inspect or hand-edit a spec before re-rendering.

For contributors, the root package.json is a private package named archify-repository that requires Node 18 or newer. The default test script runs the core smoke tests; separate scripts cover browser tests, WebM artifacts, generated-output checks for the viewer, brand marks, validators and release identity, plus golden-file comparison. The project is moving quickly: v3.1.0 landed on 2026-10-13, v3.2.0 on 2026-10-19, a separately versioned Archify DSH 1.0.0 on 2026-10-04, and the last push to main was 2026-11-02.

Editorial conclusion

Archify fits people who already work inside Claude Code, Cursor, Codex CLI or OpenCode and want a shareable, clickable diagram or explainer page without opening a drawing tool. It is a poor fit if you have no agent, or if you need an editable diagram source for another program, since the exports are raster images or a printed PDF. Before using it, install only from the GitHub llms.txt URL or archify.si, and open the cited sources on any explainer before you trust its conclusion.

Frequently asked questions

Official sources

1. Official documentation
2. Official README
3. Project repository
4. Release notes