Archify: Architecture Diagrams Your Agent Can Verify

Archify is an agent skill that has your AI agent draw architecture, workflow, sequence, data-flow, and lifecycle diagrams as a single interactive HTML file — and check the diagram before calling it done. Instead of an agent improvising SVG coordinates, it writes a small typed description of the system, and Archify's renderer turns that into the picture.

What it does

Ask most AI tools for an architecture diagram and you get one of two things: a flat Mermaid sketch, or hand-placed shapes with arrows running through boxes. Archify is built to avoid both.

It routes to one of five diagram types. Architecture for components, services, and security boundaries. Workflow for processes, approval gates, and CI/CD. Sequence for API call chains and async traces. Data flow for pipelines and lineage. Lifecycle for states, retries, and terminal outcomes. The agent picks the type from your question.

Structure first, pixels second. The agent writes a typed JSON specification — nodes, relationships, labels — and the renderer deterministically compiles it into HTML and SVG. The same specification always produces the same diagram.

It validates the result. Archify's checks reject the classic failures: an edge crossing an unrelated box, two routes sharing an ambiguous corridor, a label covering another line. Its authoring rules push toward diagrams people can actually read — one obvious main path, short side branches, and no invented subtitles restating the title.

The output is a working viewer. The HTML file comes with dark and light themes, pan and zoom, search, focus, and tracing a relationship through the system. Upstream, the viewer also exports images and animations for slides and docs.

It can start from Mermaid. Give it a Mermaid flowchart, sequence diagram, or state diagram, and it reads the meaning and topology, then authors a fresh Archify diagram rather than copying Mermaid's styling.

How the Taku version differs

The original Archify is a Node.js rendering and validation system. Pointed at an open repository, it can analyse the code and map it; it can also start a local preview and check online for updates.

The Taku version is a least-privilege adaptation. It validates structure and composition and renders the same kind of self-contained interactive HTML — but it doesn't start servers, open programs, inspect repositories, or fetch remote assets. You describe the system in words, which the original's own README points out is enough: no repository is required.

The trade-off is real. If you want Archify to read a codebase and map it from source, that workflow belongs to the original.

When to reach for it

• A design doc needs an architecture diagram, not a photo of a whiteboard
• You're explaining a request path with a cache miss and a fallback, as a sequence diagram
• You want to document a CI/CD pipeline or an approval workflow
• A data pipeline review needs sources, transforms, and consumers on one page
• You have a rough Mermaid diagram and want a cleaner, explorable version

It's the wrong tool for freeform illustration. Archify draws structured system diagrams, and its rules are there to keep them structured.

What's actually inside

One skill. No connectors, no API keys. The original folder is substantial: SKILL.md plus schemas, examples, the renderer, an HTML template, and command-line tools for validating, delivering, and previewing diagrams. It's MIT-licensed and credits Cocoon-AI's architecture diagram generator as its starting point.

Setting it up

The GitHub route. The original installs with npx skills add tt-a1i/archify -g, which needs Node.js on your machine. The project page has agent-specific install commands for Cursor, Codex, Claude Code, and OpenCode, and the skill ships a doctor command to confirm everything works. Then you ask in chat — something like Use Archify to draw: Browser -> API -> Redis cache -> PostgreSQL fallback — and refine with follow-ups such as "move auth to the left".

The Taku route. Open Archify in Taku and describe the system you want drawn.

Either way, the diagram is only as accurate as the description. Archify checks that a diagram is well-formed; it can't know whether your system really works the way you described it.

Who made it

Archify is an open-source project by tt-a1i on GitHub, released under the MIT license. tt-a1i also published it to the Taku marketplace, as a Community adaptation with reduced permissions.

If you've never installed a skill before

You don't need to understand GitHub, Codex, or Claude Code to draw a diagram with this skill. The original routes assume Node.js, a package command, and knowing which agent directory the skill should land in.

Taku is a desktop workspace built for skipping that: find something someone already built, mirror it into your own workspace, and run it. Browse the free app library for more developer skills, or see Claude Code use cases for where tools like this earn their place. For the written half of repository context, the AGENTS.md Generator documents build commands and boundaries for coding agents.

Download Taku and turn your next system description into a diagram. Taku is in Beta, and the Mac app is available now; there's also an experimental, unsigned Windows build for Windows 10 and 11.

FAQ

What is Archify?

An agent skill that turns a system description into a validated, interactive HTML diagram — architecture, workflow, sequence, data flow, or lifecycle — by compiling a typed JSON specification rather than hand-placing shapes.

What diagram types does it support?

Five: architecture, workflow, sequence, data flow, and lifecycle. The agent chooses based on what you're trying to show.

Does it need access to my code?

No. You can describe the system in words. The original can also analyse an open repository; the Taku version doesn't inspect repositories.

How is the Taku version different from the original?

It renders and validates the same kind of self-contained HTML diagram, but it doesn't start servers, open programs, inspect repositories, or fetch remote assets.

Is it free?

The skill is free and open source. You need an AI agent to run it. For what Taku costs, see pricing.

Key points

• Draws five kinds of system diagram as a single interactive HTML file.
• The agent writes a typed specification; the renderer compiles it deterministically.
• Built-in checks reject crossing edges, ambiguous routes, and covered labels.
• Taku's version is least-privilege: no servers, no repository access, no remote assets.
• Accurate structure, not accurate facts — the diagram reflects your description.