一句话定位

把 Archify 技术图 Skill 挂到 DeepSeek Harness 上，让 dsh 在聊天里读取代码、产出五种带校验的交互式系统地图（架构/工作流/时序/数据流/生命周期），最终生成可分享的自包含 HTML 文件。

核心能力

• 注入 Archify 文件系统 Skill，让 dsh 加载现成的架构图技能包
• 读仓库生成五种交互式系统地图（架构、序列、工作流、数据流、生命周期）
• 输出的图全部带 typed JSON 校验，确保结构自洽后再渲染
• 导出可分享的单文件 HTML，支持搜索节点、上下游追溯、暗/亮主题切换
• 提供 Before/Delta/After 差异视图，便于评审架构改动
• 通过 shell 写出 JSON 与 HTML 产物到工作区，无需启动额外服务

技术实现

• 语言: JavaScript (ESM)
• 关键依赖: 无运行时依赖；仅依赖 Node 内置模块 node:module、node:path
• 架构模式: DSH bundle patch（cordis.patch.yml）——通过 insert 指令向宿主注入一个名为 archify-plugin 的文件系统 Skill Provider，由 @deepseek-ai/dsh-skill-filesystem 实现
• 入口文件: integrations/deepseek-harness/lib/index.js（仅导出 resolveArchifySkillRoot 纯函数，把安装包内的 skills/ 目录解析到 DSH profile）

适用场景

想在 dsh 里直接和 agent 对话，让它把一个仓库画成可分享的架构图，而不必自己装额外桌面工具、复制 prompt 或手动跑 CLI 的用户。适配器适合那些已经把 dsh 当日常 Agent 工作台、又需要给同事或 PR 评审方提供"看一眼就懂"的系统全景的人。

前置依赖与兼容性

安装方式

dsh plugin --profile web add github:tt-a1i/archify/integrations/deepseek-harness

配置项

适配器自身不暴露用户级配置入口；以上三栏由 cordis.patch.yml 注入到宿主，无需在安装后手动调整。

常见问题

Q: 这个插件是 DeepSeek 官方出品的吗？

A: 不是。仓库首页和插件 README 都明确标注 "Community integration" 和 "not an official DeepSeek product"，仅在开发者预览版 dsh 上验证可用，不代表跨版本稳定承诺。

Q: 安装之后我怎么调用它？

A: 在 dsh 对话里直接说 "Use the archify skill to map this repository's runtime architecture" 或其中文表述，agent 就会加载 Archify Skill，按 typed JSON 生成校验过的图。Skill 内部命令需要 shell 权限（validate / deliver / preview）。

Q: 生成的图为什么不出现在 dsh Web 的 Produced Files 列表里？

A: 因为 Archify 通过 shell 写出 HTML/JSON，不会自动进入 Produced Files 通道。需要让 agent 在交付完图后，把生成的 specification JSON 和 HTML 的精确工作区绝对路径返回给你，你从工作区里直接打开。

Q: 这个适配器会在我电脑上偷偷开端口、上报数据或读我的 key 吗？

A: 不会。integrations/deepseek-harness/lib/index.js 只有一个纯函数 resolveArchifySkillRoot，整库没有 child_process、fetch、setInterval、Worker、process.env.*TOKEN 等关键词（adapter-security.test.mjs 强制断言）。没有 telemetry、没有网络请求、没有 prepare/install/postinstall 钩子。

Q: 卸载命令是什么？

A: dsh plugin --profile web remove @tt-a1i/archify-dsh。它只会移除适配器与 Skill 注入，不会删除你之前生成的图文件。

Q: 升级 dsh 之后还能用吗？

A: 适配器当前仅在开发者预览版 @deepseek-ai/dsh@0.1.0-rc.6 上验证，README 明确写 "It is not a stable cross-version guarantee"。等 dsh 进入正式版本后需要看适配器是否同步发布新版。

Q: 我可以同时保留别的 Skill 或自定义目录吗？

A: 注入配置里 includeDefaultRoots 默认为 false，只暴露本插件打包的 skills/ 目录；如果你已经在 dsh profile 里挂了别的 Skill Provider，它们互不影响。

上手难度

入门 — 用户只需在 dsh 对话里用一句英文（或其中文版本）触发即可，Skill 内部命令由 agent 自动调度。

已知问题与限制

• 仅在开发者预览版 @deepseek-ai/dsh@0.1.0-rc.6 上验证，README 明确说明不代表跨版本稳定承诺
• 通过 shell 产出的 JSON / HTML 不会自动进入 dsh Web 客户端的 Produced Files 通道，需要让 agent 返回精确工作区路径
• 适配器不注册 render / validate / deliver 工具，Archify 的内部命令必须由 agent 在 Skill 流程里调度，用户无法手工调用
• v0.1.0 与上游 Archify 主线版本（v2.15.0）解耦，更新节奏可能滞后

English · 简体中文

Archify

Turn a codebase or system description into a polished, interactive system map — directly in chat.

Archify is an agent skill for Raven, Cursor, Claude Code, Codex CLI, and OpenCode. Give it a system description or repository; get an interactive, shareable technical map.

• Open it and present — five diagram types, four presets, dark/light themes, built-in brand marks, and finite motion
• Review architecture changes before merge — compare two validated snapshots as Before / Delta / After, with exact added, removed, changed, moved, and rerouted facts
• Every interaction stays grounded — search nodes, optionally open revision-verified source, trace upstream/downstream authored reach and exact routes, compare roles, and play guided stories without inventing topology
• One file, ready to trust and share — typed JSON IR and deterministic checks produce self-contained HTML plus PNG, SVG, WebM, and 1200×630 share cards

Current stable version: v2.15.0. See Changelog.

Project page · Scenario guide · Proof Lab

npx skills add tt-a1i/archify -g

Using Cursor? Open the agent-aware quick start for exact global and project commands.

Then ask your agent: Use archify to map this repository's runtime architecture.

❤️ Sponsors

Thanks to APINEBULA for sponsoring Archify. APINEBULA offers unified access to Claude, GPT, Gemini, and more. Register through the Archify link and use Archify for a 10% discount.

Sponsored by EverMind, building memory infrastructure for agents. Its memory-first, self-evolving agent harness Raven supports Archify as a Skill, bringing verified, interactive system maps into Raven workflows.

See Archify in action

These are generated Archify artifacts, not product mockups. Click a frame to open its live, shareable state.

_{Three real generated artifacts. Signal Flow · Blueprint · Classic · open the interactive Proof Lab ↗}

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

A real repository, mapped from source

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

Preview

Same diagram, two themes, one click to switch:

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

Use Copy Share Card when you want a canonical 1200×630 image for a README, release, or social post.

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

1. Install

npx skills add tt-a1i/archify -g

For an explicit, non-interactive Cursor install:

npx -y skills add tt-a1i/archify --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/archify-dsh@0.1.0

The agent switcher covers cursor, codex, claude-code, and opencode. For Raven's manual ZIP install, extract archify.zip into ~/.raven/workspace/skills; it yields ~/.raven/workspace/skills/archify. Raven is not a switcher target.

2. Ask for one bounded view

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.

For a focused flow:

Use archify to draw this login flow: Browser -> Web App -> API -> JWT validation ->
Redis session lookup -> PostgreSQL fallback. Keep the cache-miss path secondary.

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

For a production deployment review, Architecture can optionally enable the deployment-ownership engineering profile. It fails closed when owners, single-region placement, private database scope, or named boundary crossings are missing. It is never enabled silently and validates authored facts—not 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 exact authored change or play one finite Review—viewer-only, with no impact, risk, or merge-safety inference.

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:

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

Why Archify

• 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

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 desktop authoring mode, not a default background service: it binds only to 127.0.0.1 on a random port, watches the one named JSON file, preserves the last verified output through failures, and stops with Ctrl-C. Add --no-open for tests or when you will open the printed local URL yourself. It adds no runtime to the generated HTML.

Use deliver --open for a one-shot interactive local handoff. It is off by default, runs only after the verified artifact is committed, and never turns a successful delivery into a failure when the OS opener is unavailable; JSON stays on stdout and the absolute manual-open path goes to stderr.

On failure, validate --json and deliver --json still emit exactly one JSON object. Read diagnostics[] and change only the named subject using its supportedFixes; do not rewrite the whole diagram or exceed the Skill's two focused correction rounds. Deterministic diagnostics remain separate from visual review.

Optional motion and presentation styling are explicit:

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

Omit animation for a truly static diagram. classic remains default; editorial adds a warm publication look.

Explore and share the output

Stable links can restore #focus=<id>, #focus=<id>&reach=upstream|downstream, #relation=<id>, #route=<source>~<target>, #lens=<kind>~<kind>, and #view=<view-id>. 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

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.

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.