archify

Turn a codebase or system description into an interactive, verifiable, shareable technical map — right in chat.

What problem it solves

Explaining a system’s architecture or reviewing a change usually means hand-drawing diagrams in a generic editor: slow, and easy to drift from the actual code. Archify is an agent skill that lets your in-session agent turn a repository or a text description into a structured, verifiable diagram. Five diagram types — architecture, workflow, sequence, data flow, and lifecycle — cover everything from the whole system to a single interaction.

It is not just “pretty”. Every render passes through a typed JSON IR and deterministic checks; schema, layout, HTML/SVG, route, and label-clearance gates must all pass before a new artifact replaces the last known good one, and failures come with a machine-readable repair receipt. Architecture Delta compares validated Before / Delta / After snapshots to list exactly which nodes and relations were added, removed, changed, moved, or rerouted — so you review verified facts, not a guessed-at picture.

Key features

• Five diagram types: architecture / workflow / sequence / data flow / lifecycle, each matched to its scenario (components and boundaries, CI/CD and approvals, API calls and fallbacks, data lineage, states and retries)
• Interactive viewer: search nodes, trace upstream/downstream reach, probe exact routes, compare semantic roles, and play finite guided stories — always reusing authored nodes and relations instead of inventing topology
• Architecture Delta: compare validated Before / Delta / After snapshots with a machine receipt of added, removed, changed, moved, and rerouted facts
• Atomic validated delivery: schema, layout, HTML/SVG, route, and label checks must all pass before replacing the last good artifact; failures carry stable rule codes and repair controls
• Self-contained output: one HTML file, with PNG, SVG, WebM, and 1200×630 share-card exports and dark/light themes
• Source evidence on demand: evidence-backed architecture nodes mark themselves SRC n and open Git-verified file/line ranges pinned to a public commit
• Broad agent support: Raven, Cursor, Claude Code, Codex CLI, OpenCode, plus the DSH community integration

Quick start

Install:

dsh plugin --profile web add @tt-a1i/archify-dsh@0.1.0

Then ask in conversation:

Use the archify skill to map this repository’s runtime architecture.

Be more specific when you want, e.g. “analyze this repository and draw a high-level runtime architecture with 8–12 core components.” Refine in chat afterwards (“add Redis”, “move auth to the left”) — the typed source stays available for targeted iteration. On other agents, install with npx skills add tt-a1i/archify -g.

Who it is for

• Developers and architects who need trustworthy diagrams for reviews, docs, and walkthroughs
• Teams that want to compare before/after differences during design or PR review
• DSH users who would rather have the in-session agent draw the map than hand-draw it