One-Line Pitch

Mount the Archify diagram Skill onto DeepSeek Harness, enabling dsh to read code during conversations and produce five types of validated interactive system maps (architecture/workflow/sequence/dataflow/lifecycle), ultimately generating shareable self-contained HTML files.

Core Features

• Inject the Archify filesystem Skill, allowing dsh to load pre-built architecture diagram skill packages
• Read repositories to generate five types of interactive system maps (architecture, sequence, workflow, dataflow, lifecycle)
• All output diagrams include typed JSON validation, ensuring structural consistency before rendering
• Export shareable single-file HTML with node search, upstream/downstream tracing, and dark/light theme switching
• Provide Before/Delta/After difference views for reviewing architecture changes
• Output JSON and HTML products to the workspace via shell without requiring additional services

Technical Implementation

• Language: JavaScript (ESM)
• Key Dependencies: No runtime dependencies; relies only on Node built-in modules node:module, node:path
• Architecture Pattern: DSH bundle patch (cordis.patch.yml) — uses the insert directive to inject a filesystem Skill Provider named archify-plugin into the host, implemented by @deepseek-ai/dsh-skill-filesystem
• Entry File: integrations/deepseek-harness/lib/index.js (exports only the pure function resolveArchifySkillRoot, which resolves the skills/ directory within the installation package to the DSH profile)

Use Cases

Users who want to directly converse with an agent in dsh, have it diagram a repository into shareable architecture diagrams, without installing additional desktop tools, copying prompts, or manually running CLIs. The adapter suits those who already use dsh as their daily Agent workstation and need to provide colleagues or PR reviewers with "at-a-glance" system overviews.

Prerequisites & Compatibility

Installation

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

Configuration Options

The adapter itself does not expose user-level configuration entry points; the above three options are injected into the host via cordis.patch.yml and require no manual adjustment after installation.

FAQ

Q: Is this plugin an official DeepSeek product?

A: No. Both the repository homepage and plugin README clearly state "Community integration" and "not an official DeepSeek product". It is only verified on the developer preview version of dsh and does not represent a stable cross-version guarantee.

Q: How do I invoke it after installation?

A: Simply say "Use the archify skill to map this repository's runtime architecture" (or its Chinese equivalent) in the dsh conversation, and the agent will load the Archify Skill to generate validated diagrams in typed JSON. The Skill's internal commands require shell permissions (validate / deliver / preview).

Q: Why don't the generated diagrams appear in dsh Web's Produced Files list?

A: Because Archify writes HTML/JSON via shell and does not automatically enter the Produced Files channel. You need to ask the agent to return the precise workspace absolute paths of the generated specification JSON and HTML after delivery, then open them directly from the workspace.

Q: Does this adapter secretly open ports, report data, or read my keys on my computer?

A: No. integrations/deepseek-harness/lib/index.js contains only a pure function resolveArchifySkillRoot. The entire codebase has no keywords like child_process, fetch, setInterval, Worker, or process.env.*TOKEN (enforced by adapter-security.test.mjs). No telemetry, no network requests, no prepare/install/postinstall hooks.

Q: What is the uninstall command?

A: dsh plugin --profile web remove @tt-a1i/archify-dsh. It only removes the adapter and Skill injection, not your previously generated diagram files.

Q: Will it still work after upgrading dsh?

A: The adapter is currently verified only on developer preview @deepseek-ai/[email protected], and the README clearly states "It is not a stable cross-version guarantee". After dsh reaches stable release, check whether the adapter has a new version published.

Q: Can I keep other Skills or custom directories at the same time?

A: The injection config has includeDefaultRoots defaulting to false, exposing only this plugin's bundled skills/ directory. If you have other Skill Providers mounted in your dsh profile, they won't affect each other.

Difficulty Level

Beginner — users only need to trigger it with a single English (or Chinese) sentence in the dsh conversation; the Skill's internal commands are automatically scheduled by the agent.

Known Issues & Limitations

• Verified only on developer preview @deepseek-ai/[email protected]; README clearly states it does not represent a stable cross-version guarantee
• JSON/HTML outputs via shell do not automatically enter the dsh Web client's Produced Files channel; the agent must return precise workspace paths
• The adapter does not register render/validate/deliver tools; Archify's internal commands must be scheduled by the agent within the Skill flow; users cannot manually invoke them
• v0.1.0 is decoupled from upstream Archify mainline version (v2.15.0); update节奏 may lag behind

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/[email protected]

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.