Skip to main content
Archify: An agent skill for turning ideas and code repositories into interactive diagrams
AI WorkflowProjectSource project · deployment required

Archify: An agent skill for turning ideas and code repositories into interactive diagrams

Archify is an agent skill for tools such as Claude Code, Codex CLI, Cursor, and OpenCode. It generates interactive diagrams and one-page explainers from descriptions or code repositories, delivering standalone HTML files for browser viewing.

Delivery

Upstream repository and source ZIP; deployment required

Project language

JavaScript

This is an upstream source snapshot at a fixed commit, separate from any ENHE package.

No verified installer is provided. Check the upstream repository for setup and deployment requirements.

Project details

This workflow comes from a GitHub repository. Review the delivery and verification status below before using it.

Application area

Programming & development

Project type

Skill pack

License

Apache-2.0

Delivery

Upstream repository and source ZIP; deployment required

GitHub stars

92,392 · 11/2/2026

Package verification

No ENHE package available

Link-only reason: This item is available as an upstream repository link only.

Project Overview

Project Overview

Review core features, use cases, and delivery details.

Project overview

Archify is an agent skill project written primarily in JavaScript. It lets an AI agent generate interactive diagrams from ideas, plans, questions, or code repositories. It can also organize an answer into a one-page explainer containing text, tables, steps, and diagrams. The project supports architecture, workflow, sequence, data flow, lifecycle, entity-relationship, class, tree, timeline, and waterfall diagrams. Its output is a standalone HTML file, and viewing that output does not require installing Archify.

Use cases

Use it to map a repository's core components, explain API requests and cache fallback, document approval or deployment workflows, or present database relationships, event timelines, and request timings. Without a repository, you can start from a description to visualize learning material or plans. When a complex question needs a one-page explanation, you can ask the agent to lead with the conclusion and then explain the reasons and steps in separate panels.

What it does and problems it solves

Archify organizes scattered text, components, and relationships into explorable diagrams. Readers can inspect node details and trace authored upstream or downstream relationships and specific paths. Creators can refine the result through conversation while retaining structured JSON source for editing. The project provides generation, validation, and delivery workflows. However, diagram relationships do not establish actual runtime impact or guarantee system safety or merge readiness. Automatic Mermaid parsing, general-purpose automatic layout, hosted sharing, and WYSIWYG editing are outside the current scope.

How to use

1. In an agent with the skill configured, enter a concrete description, such as: “Use Archify to diagram a browser calling an API, the API checking Redis, and a cache miss querying PostgreSQL and filling the cache.” No repository is required. 2. To analyze code, open the target repository in your agent, then ask it to analyze the repository and create a high-level runtime architecture diagram showing core components, the primary path, external dependencies, and trust boundaries. 3. Continue with focused requests such as “Add authentication,” “Highlight the cache-miss path,” or “Switch to the light theme.” 4. Open the generated HTML file in a browser to inspect node details and paths. Press `?` for the Diagram Guide, `/` to find a node, or `E` to open Export. Available interactions depend on what the file contains. 5. Share the HTML file with others; recipients do not need Archify installed. External websites and map destinations within the file require a network connection.

Installation

1. Open the original repository through the entry below this page and read Quick start and Installation options. Select the method for your agent. Obtain complete installation commands containing web addresses and any download entries from the original repository. 2. To try it temporarily with Codex without installing, the README provides: `npx skills use tt-a1i/archify@archify --agent codex`. This is a trial method, not a persistent installation. 3. For Claude.ai, obtain `archify.zip` through the entry provided in the original repository, then upload it under Settings → Capabilities → Skills. The README states that capabilities in this setup depend on Node.js access in the sandbox. 4. The README also lists skill directories for Claude Code, Codex CLI, and OpenCode. However, the supplied material does not fully describe manual copying or consistently specify runtime version requirements for every installation method. Consult the original repository's relevant installation instructions before using these methods; the trial command is not a complete environment setup. This page lists only the repository link. Runnable packages and core workflows have not been verified.

Source and usage notes

- Original repository: https://github.com/tt-a1i/archify - Source revision: a4065941f12be7967436261d9934784e381d423c This listing links to the upstream repository. It does not provide a verified download package, and the complete workflow has not been independently validated. This description was organized and translated with AI from public upstream material. Refer to the original repository for capabilities, setup requirements, costs, and license terms.

Changelog

0 records

Important version notes will be added when availability, delivery details, or usage guidance changes. Review the current page information before purchase or use.

Share This Page

Scan the QR code to view this page, or copy its link to share.

User comments

Log in to comment.

FAQ

How can I access this project?

Choose View Original Project to open the upstream GitHub repository. Follow its setup instructions to deploy the source.

What should I check before using it?

Check the upstream setup instructions, runtime requirements, version, and the verification status shown on this page. A repository link does not mean ENHE has verified the complete workflow.

Does access include third-party services and permissions?

Check the upstream license and each service provider's terms. Model APIs, accounts, hosting, and other dependencies may have separate requirements or charges; follow the stated delivery scope.