OpenViSTAI · Agents · Blockchain · Crypto
Menu
Agent Frameworks

Archify

Archify is a JavaScript-based, MIT-licensed agent skill that enables compatible AI agents to create interactive HTML diagrams from a user’s idea, plan or codebase. The resulting visual can be explored, customized and shared.

Independent OpenViST project profile, based on linked sources.

Archify — OpenViST project profile in Agent Frameworks.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use Archify when you want a compatible AI agent to turn a written description, plan or codebase into an interactive HTML visual, especially when a repository-backed architecture map or iterative prompt-based refinement is useful.

Who it is for

  • Developers who want an AI agent to map a repository’s runtime architecture.
  • People turning a described system or workflow into an interactive visual.
  • Learners and planners who want maps of topics, study plans or itineraries.

Documented uses

  • Create an interactive architecture diagram from a system description or codebase.
  • Turn a plan or topic into a navigable visual map.
  • Refine a generated diagram through follow-up requests, such as emphasizing a path or changing its theme.
Before you choose

Requirements & limits

The project describes itself as free and open source. Third-party online services and paid plans mentioned by the project are operated by their respective providers.

  • Archify is an agent skill, so the workflow depends on using a compatible AI-agent environment rather than a standalone editor.
  • Documented agent contexts include Claude Code, Codex CLI, Cursor and OpenCode; installation steps vary by surface.
  • Claude.ai support depends on Node.js access in its sandbox; Project Knowledge is described as a prompt-driven architecture fallback.
  • Automatic Mermaid parsing, general-purpose auto-layout, hosted sharing and WYSIWYG editing are outside the documented scope.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Install Archify and request a diagram from a description

Install the Archify skill for a compatible AI agent and ask it to create an interactive diagram from a plain-language description.

Before you start

  • A compatible agent such as Claude Code, Codex, Cursor, or OpenCode.
  • Access to run the documented npx installation command.

Steps

  1. Install Archify globally with the command below.

    Documented command
    npx skills add tt-a1i/archify -g
  2. In your agent, describe the subject you want diagrammed and ask it to use Archify; for example, describe a browser-to-API request that checks Redis and falls back to PostgreSQL.

  3. Review the generated diagram and ask the agent for supported changes, such as highlighting a path or switching the theme.

Expected outcome

The agent produces an interactive HTML diagram that can be explored, customized, and shared.

Guide limitations

  • A repository is not required for a diagram based on a description; source-backed diagrams require asking the agent to inspect a repository.
  • Archify does not automatically install updates; you choose whether and when to update.
Source-based practical guide

Start a diagram from a bounded system overview

Use Archify to create a high-level architecture diagram from a plain-language system description without providing a repository.

Before you start

  • An agent that can use the Archify skill.
  • A system description covering users, core components, the primary path, external dependencies, and boundaries.

Steps

  1. Install the Archify skill using the global installation command: the command below.

    Documented command
    npx -y skills add tt-a1i/archify --skill archify --agent codex --global --copy --yes
  2. Ask Archify to turn the description into a high-level architecture diagram, keeping one primary path across 8–12 core components.

  3. Ask for clarification on missing facts that would materially change the diagram, and have remaining unknowns marked rather than invented.

Expected outcome

A high-level architecture diagram organized around one primary path, with external dependencies and boundaries represented.

Guide limitations

  • This recipe describes a diagram from a plain-language description; use a repository when source evidence matters.
  • The recommended scope is 8–12 core components and one primary path.
Evidence and transparency

Sources & review

Source record details
Source availability
Active
Sources checked
13 October 2026
Original website title
tt-a1i/archify · Official homepage title · retained in its source language