Archify
An agent skill that produces five families of diagrams from a repository: architecture, workflow, sequence, data flow, lifecycle. The agent is not allowed to draw: it emits a typed JSON graph that a local compiler validates, then turns into self-contained HTML with PNG export. A diagram failing validation does not replace the last one that passed. It also starts from a plain sentence, with no repository ("checkout with a queue and Postgres"): the diagram is then just as interactive, but it cites no line, since there is no file to check.
Strengths
- The diagram is edited in conversation ("add authentication", "switch to the light theme") and flips between dark and light themes in one click
- The agent emits a typed JSON graph, not a drawing: five checks must pass before a diagram replaces the previous one
- Nodes cite their sources (`SRC n`) pointing at a file and a line range pinned to a commit
- A validation failure returns actionable repair guidance instead of a plain retry
- Before / after comparison of two validated snapshots, with a receipt of what moved in the structure
- Self-contained HTML output with PNG export, readable with no server and no build, under the MIT licence
- Clicking a node traces what depends on it, upstream or downstream, and the traced path exports as a share card; animated export on top of PNG
Limitations
- A verifiable diagram is not a correct diagram: validation proves graph consistency, not the relevance of the breakdown
- The before / after comparison says nothing about execution or merge safety, only about the graph
- A young repository that breaks fast: five months after its creation, 3.0 removed views and exports from 2.x, and one integration requires Node 22.19 or 24 depending on the host
- Started from a description, the diagram has no source to cite: the verification the videos praise only holds on a repository it has read
Best for
- Documenting the architecture of a repository you are taking over, with diagrams that cite their lines of code
- Showing in code review what the change moved in the structure, before and after
- Producing a sequence or data-flow diagram without letting the agent invent components