archify

See Archify in action

https://github.com/user-attachments/assets/78570807-ba1d-4737-953f-55504a378a87

One sentence. Your repo, mapped. Watch the 35-second demo: explore the diagram, follow source links, and trace a path. Try the interactive examples ↗

Install, then describe your idea

Works with Cursor, Claude Code, Codex CLI, and OpenCode. See installation options below for additional integrations.

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

Send this to your agent:

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.

Then continue: “Add authentication”, “Highlight the cache-miss path”, or “Switch to the light theme”.

No repository is required: start with a description, or ask your agent to read a repository for a source-backed architecture diagram.

Choose your agent · Installation details and update checks · Create and check diagrams with your agent

Ask a question, get a one-page answer

Not every answer is one diagram. Ask your agent to answer as a page and Archify builds an explainer: the conclusion first, then one panel per question, with tables, steps, charts, code and validated diagrams.

• Conclusion first. The answer and its reasons lead; every panel takes one question.
• Diagrams that explain. Steps sit beside the diagram they walk through and light its parts as you read. Click any node to open the full interactive view.
• Easy to check. Claims cite numbered sources; repository excerpts are pinned to a commit and open in a source card.
• Easy to share. One HTML file with four styles and light or dark themes. Export a PNG, WebP or JPG long image, or print to PDF. Ask about any panel to get a follow-up your agent can use to revise just that panel.

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?

Live examples: First HTTPS visit · P99 latency (Chinese) · How Archify finalize keeps the last good file, read from this repository (Chinese) · First rental checklist (Chinese)

❤️ Sponsors

Archify × Kimi Work. Find Archify in the Kimi Work plugin store as Interactive Architecture Diagram. Describe your system in one sentence to create an interactive diagram. Try it in Kimi Work →

Want to sponsor Archify? Contact us by email.

Show what matters

Explain an agent workflow	Follow a cache miss	Explore service relationships
Trace everything downstream of one step.	Highlight the path from web app to database.	Focus on authored backend and database connections.

The Proof Lab contains all 11 checked-in scenarios, their JSON sources, and validation receipts.

Understand a real repository

CODE → DIAGRAM · A source-backed system map

Archify traced mco-org/mco at 9f1a1cf and produced this checked map. Open it ↗ · trace reach ↗ · typed source

Easy to extend. More ways to make it yours.

COMMUNITY STORIES · Selected examples shared by users

Keep building after the diagram is generated. Archify is open source and its output is standalone HTML. Ask your agent to adapt it, connect useful links, or add interactions for your own workflow. Community creations already span team collaboration, travel planning, legal citation checks, contract review, and incident retrospectives. These are just a few examples.

One user started with a hand-drawn multi-agent architecture, turned it into an interactive diagram, then added a Kimi execution pool through conversation. Others asked their agent to read a project and brought the resulting architecture into Feishu or DingTalk for team discussion.

Another user turned a Shanghai CityWalk guide into a four-day itinerary: switch between days, inspect a stop, and jump to Amap, Xiaohongshu, or Dianping. The author also added arrival check-ins and stop notes, turning the itinerary into a small tool to use during the trip. These extensions were added by the community author for this particular artifact.

▶ Explore the interactive Shanghai CityWalk

▶ Try the interactive version · Switch between D1–D4 and click a place to explore.

Community artifact · Shanghai CityWalk · Four days of routes and place links

Download it. Open it. Explore it.

The output is a self-contained HTML file. Download it and open it in your browser to use the node details and path exploration included in that artifact. No Archify installation is needed to view it. Send the HTML to someone else and the interactions go with it; external websites and map links need a network connection.

Explore the Shanghai CityWalk ↗ · Download HTML ↓

Try switching between D1–D4, opening a place card, or following a map link. Times and place information reflect the author's original itinerary.

Community and recognition

• #1 on GitHub Trending's weekly, all-language repository list. Ranking screenshot published by the creator on September 1, 2026, with all languages and “This week” selected.
• Featured and interviewed by QbitAI. Project feature · The developer's story.
• Shared with developer communities. midudev's post.

A selection of public coverage, community shares, and historical milestones. Follow the links for dates and sources.

Preview

Same diagram, two themes, one click to switch:

Dark	Light

The Export menu copies PNG to the clipboard and downloads static or motion formats:

After tracing a route, Export → Route Share Card downloads that authored path as a 1200×630 PNG with the full diagram retained for context.

After tracing authored Upstream or Downstream reach, Export → Reach Share Card captures that exact reading without claiming runtime impact.

Open examples/web-app.html locally to try the complete viewer.

Quick start

Current stable version: v3.2.0. See Changelog.

1. Install

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

For an explicit, non-interactive Cursor install:

npx -y skills@latest add https://archify.si --skill archify --agent cursor --global --copy --yes

To try without installing:

npx skills use tt-a1i/archify@archify --agent codex

DSH community opt-in: dsh plugin --profile web add @tt-a1i/[email protected]

The agent switcher covers cursor, codex, claude-code, and opencode.

Archify may GET the fixed stable manifest solely to show an optional reminder; it never downloads or installs updates. Successful checks wait about 24 hours (±20%); active use retries failures after 6, then 24 hours. The server sees normal HTTP metadata (IP and time), but receives no version, Agent, project data, prompts, account/device ID, or ETag. You decide whether and when to update. Set ARCHIFY_UPDATE_CHECK_DISABLED=1 to disable networking and reminder-state writes.

Stay updated

• Get release notifications: select Watch → Custom → Releases at the top of this GitHub repository. Starring the project does not subscribe you to release notifications.
• See what changed: Release notes.
• Use a feed reader: Subscribe to the release feed.

Installations with the update checker also check for newer stable releases during diagram delivery and can show a reminder. Older installations without the checker need a manual update to gain this feature. You choose whether and when to upgrade; Archify never installs updates automatically.

2. Start from a description — no repository required

Use Archify to draw: Browser -> API -> Redis cache -> PostgreSQL fallback.

For source evidence, open a repository and ask:

Analyze this repository, then use archify to create a high-level runtime architecture diagram.
Show 8–12 core components, one primary path, external dependencies, and trust boundaries.
Put supporting detail in cards instead of adding more edges.

3. Refine in chat

Continue with focused requests such as add Redis, move auth to the left, or highlight the rollback path. Archify keeps the typed source available for targeted iteration.

Choose the right diagram

Type	Best for	Include in your prompt
Architecture	Components, services, storage, boundaries	Scope, core components, primary path
Workflow	CI/CD, approvals, tool calls, runbooks	Participants, order, branches, exceptions
Sequence	API calls, cache fallback, auth, async traces	Callers, callees, returns, timing
Data Flow	Pipelines, lineage, PII, consumers	Sources, transforms, stores, boundaries
Lifecycle	States, retries, waits, terminal outcomes	States, events, retry and cancellation paths
ERD	Database schemas: tables, columns, keys, cardinality	Tables, every column with its type, primary/foreign/unique keys, relationship cardinality
Class	Classes, interfaces, selected members, type relationships	Types, key members, inheritance and implementations, composition, dependencies
Tree	Single-parent hierarchies: repositories, modules, capability breakdowns	Root, levels, what each branch contains
Timeline	When things happened: incident reviews, release histories	Timestamps with time zone, events, source lanes, whether times are observed or illustrative
Waterfall	Where the time went in one request or agent run	Spans, start times and durations, nesting, whether timings are measured or illustrative

Architecture's optional deployment-ownership profile fails closed when authored owners, region placement, private database scope, or named crossings are missing; it is never implicit and does not inspect live infrastructure. See the checked deployment proof.

For design or PR review, Architecture Delta compares validated Before / Delta / After snapshots with a machine receipt. Select an authored change or play one finite, viewer-only Review; it infers no impact, risk, or merge safety.

node archify/bin/archify.mjs compare architecture base.json head.json architecture-delta.html --json

Not sure which one fits? Use the interactive scenario guide, or ask the zero-dependency CLI:

node archify/bin/archify.mjs guide "Show an API request with Redis cache miss"
node archify/bin/archify.mjs guide "Map Kafka topics, consumer groups, replay, and DLQ" --json

Workflow keeps the happy path clear across lanes:

Sequence explains one interaction over time:

Data Flow makes movement and sensitivity boundaries explicit:

Lifecycle separates progress, waits, retries, and terminal outcomes:

New in 3.1: ERD, Class, Tree, Timeline and Waterfall.

ERD keeps tables, every column and key, and relationship cardinality together:

Class shows contracts, selected members, and which types depend on or implement them:

Tree shows single-parent containment, such as a capability breakdown:

Timeline places events on one proportional clock, with a lane per source:

Waterfall shows where the time went across nested and overlapping spans:

Explore these examples: ERD · Class · Tree · Timeline · Waterfall. The Timeline and Waterfall examples use illustrative data; treat timestamps or durations as real only when they come from logs or traces.

Architecture examples: web-app · Archify pipeline · grid placement · desktop agent

Why Archify

Understand the structure	Walk through the story
Map components, workflows, and relationships from code or a description.	Explore nodes, follow paths, and share any view as a link.
Extend it your way	Share the result
Keep an editable source and build on the open-source code or generated HTML with your own interactions and use cases.	Share a self-contained HTML file or export images, video, and share cards.

• Layout judgment over generic auto-layout — the agent chooses hierarchy, spacing, routes, and emphasis; shared automatic endpoints spread deterministically instead of piling arrows on one midpoint.
• Typed JSON IR — every renderer-backed mode has a schema and reproducible source.
• Atomic validation before delivery — schema, layout, HTML/SVG, route, and label-to-route clearance checks must all pass before a showcase artifact replaces the last known good output.
• Failures come with a repair receipt — validate --json and deliver --json return stable rule codes, the exact subject, measured evidence, and only supported repair controls instead of a Node stack or an unstructured retry guess.
• Last-good live preview — an optional desktop loop watches one JSON file, refreshes only after the latest candidate passes every gate, and keeps the previous verified diagram visible when a save is incomplete or invalid.
• Truthful interaction — focus, upstream/downstream reach, exact routes, role comparison, and stories reuse authored nodes and relationships instead of inventing topology or claiming runtime impact.
• Source evidence, only when requested — Evidence-backed Architecture nodes mark themselves SRC n and open Git-verified files and line ranges pinned to one public commit; ordinary artifacts stay source-free.
• Portable by default — the result is one HTML file; exports remain full-diagram and free of temporary viewer state.

Archify is not a general-purpose drawing editor or a Mermaid theme. It turns technical intent into a communication artifact.

How it works

Step	What happens
Generate	The agent creates typed JSON IR from your description.
Validate	Bundled validators and layout rules check the source; failures identify the exact local repair in machine-readable JSON.
Preview (optional)	A loopback-only desktop session watches one source and reloads only verified revisions; failures keep the last-good artifact.
Deliver	A same-directory candidate is rendered and checked; only a passing artifact atomically replaces the target, then optional --open launches that exact file.
Iterate	The agent updates the source while unrelated structure stays stable.

Useful repository commands:

cd archify
node bin/archify.mjs doctor
node bin/archify.mjs demo /tmp/archify-demo
node bin/archify.mjs guide "Show CI/CD checks, approval, deploy, and rollback"
node bin/archify.mjs validate workflow examples/agent-tool-call.workflow.json --quality showcase --json
node bin/archify.mjs preview workflow examples/agent-tool-call.workflow.json /tmp/workflow.html --quality showcase
node bin/archify.mjs deliver workflow examples/agent-tool-call.workflow.json /tmp/workflow.html --quality showcase --open --json

preview is an explicit loopback-only desktop mode: it watches one JSON file on a random 127.0.0.1 port, keeps the last verified output through failures, stops with Ctrl-C, and adds no generated-HTML runtime. Use --no-open for tests or manual URL opening.

deliver --open is an opt-in one-shot handoff after commit. Opener failure preserves success; JSON remains on stdout and the absolute fallback path goes to stderr.

On failure, validate --json and deliver --json emit one JSON object. Apply only each diagnostics[] subject's supportedFixes, within the Skill's two correction rounds; visual review remains separate.

Settings:

{
  "meta": {
    "locale": "en",
    "animation": "trace",
    "visual_preset": "signal-flow"
  }
}

meta.locale localizes page title, Legend, states/errors, a11y, HTML/SVG lang—never authored content. en, zh-CN, zh-TW, es, ko, and ar are bundled and need only meta.locale; meta.translations (canonical message key → translated string) overrides individual keys and keeps the rest of the language. Other languages supply their catalog there (see archify/examples/locales/), or the renderer falls back to English and discloses it. Static omits animation; classic defaults.

Explore and share the output

Action	Control
Open the factual Diagram Guide	?
Find and focus a semantic node	/
Trace upstream/downstream authored reach	Focus a node → Upstream / Downstream
Probe a directed route and inspect its journey	R or PATH
Compare one or two semantic roles	L or LENS
Open the live overview radar	M or MAP
Enter Presentation Stage	F
Choose visual style (S cycles) / toggle theme / open Export	S / T / E
Zoom or reset	+ / - / 0

Stable links can restore #focus=<id>, #focus=<id>&reach=upstream|downstream, #relation=<id>, #route=<source>~<target>, and #lens=<kind>~<kind>. Live repeats connection flow until paused; semantic previews remain bounded. Motion respects prefers-reduced-motion and never enters canonical exports.

The complete generation and viewer contract lives in archify/SKILL.md.

Installation options

Surface	Install location or method	Capability
Claude Code	~/.claude/skills/ or .claude/skills/	Full renderer + validation workflow
Codex CLI	~/.agents/skills/ or .agents/skills/	Full renderer + validation workflow
opencode	~/.config/opencode/skills/, .opencode/skills/, or .agents/skills/	Full renderer + validation workflow
Claude.ai	Upload archify.zip under Settings → Capabilities → Skills	Depends on Node.js access in the sandbox
Project Knowledge	Upload archify.zip to the project	Prompt-driven architecture fallback
Hermes Agent	Opt-in: hermes skills install skills-sh/tt-a1i/archify/archify -y	Community Skill-only integration; Node >=18; not a Nous official product. No telemetry. It is not a switcher target. Details.
DeepSeek Harness	Opt-in: dsh plugin --profile web add @tt-a1i/[email protected]. Invoke: Use the archify skill to map this repository's runtime architecture. Remove: dsh plugin --profile web remove @tt-a1i/archify-dsh.	Community integration for developer-preview @deepseek-ai/[email protected]; Node ^22.19.0 || >=24.0.0; not an official DeepSeek product. No telemetry. Shell files need exact workspace paths, not Web Produced Files. Details.

Reference and scope

• Schema reference · Skill · Examples · Agent cookbook
• Changelog
• Roadmap
• Generated Proof Lab

Automatic Mermaid parsing, general-purpose auto-layout, hosted sharing, and WYSIWYG editing are intentionally outside the current scope.

Community

👋 Welcome to the Archify Community!

Connect with other users and developers, share ideas, request features, report bugs, discuss development, and help make Archify better together.

• Discord
• WeChat: scan the QR code below. WeChat group codes expire periodically; if this one has expired, ask for the current code through Discord or QQ.
• QQ group: 1121948602

Official channels and third-party services

• Open-source project: Current source and packages built from it are available under the Apache License 2.0; previously published releases retain their original licenses.
• Official website: archify.si currently provides project information, examples, and installation guidance.
• Third-party services: Pricing, data handling, and support are determined by the respective provider. A similar name or domain does not establish an official affiliation.

License

Apache-2.0 — free to use, modify, and distribute.

Historical MIT grants remain in effect; see NOTICE and LICENSE-MIT. Third-party components retain their own licenses. The software license does not change ownership of your authored content or grant general permission to use Archify trademarks.

Contributing

Building a standalone package on Archify? Submit it to the community catalog; the guide includes a collapsible example and complete Chinese steps.

Issues, pull requests, and real-world diagrams are welcome. Start with the contribution guide, use the reproducible bug form for failures, or submit a validated diagram through the community showcase form. · LINUX DO

Support Archify

If Archify has been useful to you, you can support its continued development. Thank you for helping keep the project going ❤️

Scan the QR code below with WeChat, or save it and open it in WeChat to scan.

Scan the QR code below with Alipay, or save it and open it in Alipay to scan.

Using Archify, sharing it, reporting bugs, and contributing improvements are also ways to help.

Contributors

Thanks to everyone who helped build Archify. Go follow them. ❤️

Star History