Turn anything you want to understand, plan, or share into an interactive visual.
Start with an idea, a question, or a plan. Describe it to your AI agent, and Archify turns it into an interactive HTML you can explore, customize, and share. From travel itineraries and learning maps to complex systems—make it your own.
See what the community is creating—and imagine what you could make next.
Live demos · Get started · Scenario guide · Community · 简体中文 · 日本語
❤️ Partners & sponsors: Kimi Work · Supercode · OpenLux
See Archify in action
archify-launch-en-v4.mp4
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.
npx skills add tt-a1i/archify -gSend 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
❤️ 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 →
 supercode.sh |
Supercode sponsors Archify and enhances Codex and Cursor with token optimization, curated Skills, and spec-driven development. Archify is featured as a Supercode Editor’s Choice skill. |
 OpenLux |
Thank you to OpenLux for sponsoring this project! OpenLux is an all-in-one AI platform for businesses, bringing together leading AI models from major providers worldwide. With fast, reliable service and responsive technical support, OpenLux offers base pricing for Claude, OpenAI, and Gemini models as low as 8.82%, 4%, and 8% of official rates, respectively. Exclusive offer for Archify users: Sign up through our referral link and enjoy up to 7.5% off credit top-ups! Get started with OpenLux → |
 EverMind · Raven | EverMind sponsors Archify and builds memory infrastructure for agents. Its Raven harness supports Archify as a Skill for verified, interactive system maps. |
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
Themes, exports, and share cards
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.0.1. See Changelog.
1. Install
npx skills add tt-a1i/archify -gMore installation options and update-check details
For an explicit, non-interactive Cursor install:
npx -y skills add tt-a1i/archify --skill archify --agent cursor --global --copy --yesTo try without installing:
npx skills use tt-a1i/archify@archify --agent codexDSH 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.
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
Five diagram types, architecture comparisons, and examples
| 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 |
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" --jsonWorkflow 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:
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. |
The engineering behind the experience
- 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 --jsonanddeliver --jsonreturn 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 nand 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
Generation, validation, preview, and delivery details
| 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 --jsonpreview 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 are built in; other languages, including Spanish (es), need meta.translations (canonical message key → translated string; see examples/locales/es.json), 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>. Reader-driven motion is finite, 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
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
 WeChat |
 QQ |
License
MIT — free to use, modify, and distribute.
Contributing
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 ❤️
Support via WeChat Pay
Scan the QR code below with WeChat, or save it and open it in WeChat to scan.
Support via Alipay
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.
Star History
