Loading…
Agent skill for beautiful, verifiable architecture, workflow, sequence, data-flow, and lifecycle diagrams—self-contained HTML with motion and crisp export.
Our verdict: not recommended
Measured trial, not a README read. Archify is a RENDERER over agent-authored JSON IR, not a code-graph extractor: no tree-sitter/babel/ts-morph/acorn anywhere in the repo. Trial on the assistant repo (poll_tasks subsystem, HEAD 53311297): component `sources` ARE verified against the git revision (a fabricated path returned repository-evidence/file-missing, so the gate is provably red-capable), but `connections` have NO evidence field in architecture.schema.json at all (props: id, from, to, label, variant, fromSide, toSide, route, via, labelAt, labelDx, labelDy, labelSegment, width). Two deliberately fabricated edges contradicting `codegraph callees` (ensure_default_config->get_airtasker_config, _poll_tasks_inner->debug-runner reverse dep) produced ZERO topology diagnostics under `validate --repo-root` — the only complaints were label-geometry overlaps. So its edges carry no independent signal and cannot corroborate or be diffed against codegraph; the adopt criterion is unmeetable by construction. Revisit only if a real need for presentation-grade interactive architecture HTML appears (that is what it is genuinely good at), never as a code-truth source.
Filed under claude skills in our directory.