# archify

> System diagrams for coding-agent users — Exports architecture and data-flow diagrams as self-contained HTML.

- Page: https://tesign.com/en/item/archify/
- JSON: https://tesign.com/en/item/archify/index.json
- Korean Markdown: https://tesign.com/item/archify/index.md
- Generated: 2026-09-17 01:56 UTC

## RANKS

- All-time #95 · Rising this week #3 · DEV TOOLS #20 · DESIGN #3 (As of 2026-09-16 21:00 UTC)

## Numbers

- 63,560 stars — checked on GitHub 2026-09-15 19:33 UTC (+205 observed since the check)
- 7-day +1,307 observed via GH Archive (as of 2026-09-16 21:00 UTC)
- 24h +176 ★ · 30d +3,596 ★ (as of 2026-09-16 21:00 UTC)
- Star total = the value last checked on GitHub (stars_checked_at) + increases observed via GH Archive since. The 24h · 7d · 30d gains are GH Archive hourly events summed to the reference time (as_of). No score of ours.

## AT A GLANCE

- LICENSE: MIT (permissive) — https://spdx.org/licenses/MIT.html
- USAGE: Use, change and redistribute, commercially too. Keep the notice.
- OPEN SOURCE: YES
- LANGUAGE: JavaScript
- PLATFORM: [unconfirmed]
- CATEGORY: DEV TOOLS · DESIGN
- Tags: diagrams · agent-skills · docs
- How to start: For developers
- SOURCES: GitHub https://github.com/tt-a1i/archify
- USE PACKAGE: https://tt-a1i.github.io/archify

## ACTIVITY

- Last commit: 2026-09-15 08:27 UTC
- Latest release: v2.16.0 (2026-08-30)
- Contributors: 29
- Open issues (incl. PRs): 173
- Made by: an individual
- Checked on GitHub: 2026-09-15 19:33 UTC

## Signals and evidence

- RISING · +176 ★ / 24h

## TESIGN TAKE

Letting the agent draw and validate diagrams next to the code is what keeps them from going stale.

## WHY IT MATTERS

Architecture drawings go stale quickly, and every correction means opening the drawing tool again. archify comes as a skill for coding agents, so architecture, workflow, sequence, data-flow and lifecycle diagrams get produced next to the code. The output is a single self-contained HTML file you can open or export as is. Published under MIT.

## BUILD FROM THIS

- Onboarding-document diagrams that explain the repository layout
- A one-page system flow diagram for a client proposal
- An architecture page redrawn with every release

## WHO IT'S FOR

- Backend developer — keeps onboarding diagrams current
- Tech consultant — needs a system flow diagram for a proposal
- Tech lead — shows architecture before and after a PR

## START IN 5 MINUTES

```
$ npx skills add tt-a1i/archify -g
# To try without installing (Codex example):
$ npx skills use tt-a1i/archify@archify --agent codex
# Describe the system in the agent chat and ask Archify to draw it
```

## CAVEATS

- Needs an agent host (Cursor, Claude Code, Codex, OpenCode) plus Node.js
- Sends an update-check request by default; an env var disables it
- Mermaid import and WYSIWYG editing are stated as out of scope

## RECEIPT

- FIRST SEEN BY TESIGN: 2026-09-13 07:43 UTC
- AT SOURCE: 2026-04-15 05:27 UTC
- KEPT: 2026-09-13 11:32 UTC
- Published on TESIGN: 2026-09-13 11:32 UTC
- Text last updated: 2026-09-15 04:36 UTC

## How to read this

- This file was produced by the same build, from the same data, as the tesign.com item page. The text is editorial; the numbers are stored observations.
- null in the JSON means not observed — never zero. The Markdown writes [unconfirmed] for it.
- Star total = the value last checked on GitHub (stars_checked_at) + increases observed via GH Archive since. The 24h · 7d · 30d gains are GH Archive hourly events summed to the reference time (as_of). No score of ours.
- A summary, not legal advice.

[Image] https://tesign.com/img/archify-78b7af839e.png