Skip to content

Turn any idea, plan, or codebase into a beautiful interactive diagram. An agent skill for Claude Code, Codex, and more.

docs(readme): add previews for the five diagram types added in 3.1

tt-a1ie16df7fb93a5
diff --git a/README.md b/README.md
index 841578cb..8694f91a 100644
--- a/README.md
+++ b/README.md
@@ -304,7 +304,27 @@ Lifecycle separates progress, waits, retries, and terminal outcomes:
![Lifecycle example](docs/assets/archify-lifecycle.png)
-New in 3.1: [`ERD`](https://archify.si/gallery/artifacts/orders.erd.html) · [`Class`](examples/class-payments-rendered.html) · [`Tree`](examples/tree-payment-platform-rendered.html) · [`Timeline`](examples/timeline-payment-incident-rendered.html) · [`Waterfall`](examples/waterfall-checkout-request-rendered.html). The Timeline and Waterfall examples use illustrative data; treat timestamps or durations as real only when they come from logs or traces.
+New in 3.1, ERD keeps tables, every column and key, and relationship cardinality together:
+
+![ERD example: an order management schema with customer, order, payment, inventory, product and order item tables grouped by domain](docs/assets/archify-erd.png)
+
+Class shows contracts, selected members, and which types depend on or implement them:
+
+![Class example: OrderService depends on the PaymentGateway interface, implemented by card and wallet gateways](docs/assets/archify-class.png)
+
+Tree shows single-parent containment, such as a capability breakdown:
+
+![Tree example: a payment platform broken down into orders, payments and operations capabilities](docs/assets/archify-tree.png)
+
+Timeline places events on one proportional clock, with a lane per source:
+
+![Timeline example: an illustrative payment incident with release, monitoring and response events on one clock](docs/assets/archify-timeline.png)
+
+Waterfall shows where the time went across nested and overlapping spans:
+
+![Waterfall example: illustrative timing of a checkout request with concurrent inventory and discount lookups](docs/assets/archify-waterfall.png)
+
+Explore these examples: [`ERD`](https://archify.si/gallery/artifacts/orders.erd.html) · [`Class`](examples/class-payments-rendered.html) · [`Tree`](examples/tree-payment-platform-rendered.html) · [`Timeline`](examples/timeline-payment-incident-rendered.html) · [`Waterfall`](examples/waterfall-checkout-request-rendered.html). The Timeline and Waterfall examples use illustrative data; treat timestamps or durations as real only when they come from logs or traces.
Architecture examples: [`web-app`](examples/web-app.html) · [`Archify pipeline`](examples/archify-repo.html) · [`grid placement`](examples/archify-repo-grid.html) · [`desktop agent`](examples/maka-architecture.html)
diff --git a/README_EN.md b/README_EN.md
index 841578cb..8694f91a 100644
--- a/README_EN.md
+++ b/README_EN.md
@@ -304,7 +304,27 @@ Lifecycle separates progress, waits, retries, and terminal outcomes:
![Lifecycle example](docs/assets/archify-lifecycle.png)
-New in 3.1: [`ERD`](https://archify.si/gallery/artifacts/orders.erd.html) · [`Class`](examples/class-payments-rendered.html) · [`Tree`](examples/tree-payment-platform-rendered.html) · [`Timeline`](examples/timeline-payment-incident-rendered.html) · [`Waterfall`](examples/waterfall-checkout-request-rendered.html). The Timeline and Waterfall examples use illustrative data; treat timestamps or durations as real only when they come from logs or traces.
+New in 3.1, ERD keeps tables, every column and key, and relationship cardinality together:
+
+![ERD example: an order management schema with customer, order, payment, inventory, product and order item tables grouped by domain](docs/assets/archify-erd.png)
+
+Class shows contracts, selected members, and which types depend on or implement them:
+
+![Class example: OrderService depends on the PaymentGateway interface, implemented by card and wallet gateways](docs/assets/archify-class.png)
+
+Tree shows single-parent containment, such as a capability breakdown:
+
+![Tree example: a payment platform broken down into orders, payments and operations capabilities](docs/assets/archify-tree.png)
+
+Timeline places events on one proportional clock, with a lane per source:
+
+![Timeline example: an illustrative payment incident with release, monitoring and response events on one clock](docs/assets/archify-timeline.png)
+
+Waterfall shows where the time went across nested and overlapping spans:
+
+![Waterfall example: illustrative timing of a checkout request with concurrent inventory and discount lookups](docs/assets/archify-waterfall.png)
+
+Explore these examples: [`ERD`](https://archify.si/gallery/artifacts/orders.erd.html) · [`Class`](examples/class-payments-rendered.html) · [`Tree`](examples/tree-payment-platform-rendered.html) · [`Timeline`](examples/timeline-payment-incident-rendered.html) · [`Waterfall`](examples/waterfall-checkout-request-rendered.html). The Timeline and Waterfall examples use illustrative data; treat timestamps or durations as real only when they come from logs or traces.
Architecture examples: [`web-app`](examples/web-app.html) · [`Archify pipeline`](examples/archify-repo.html) · [`grid placement`](examples/archify-repo-grid.html) · [`desktop agent`](examples/maka-architecture.html)
diff --git a/README_JA.md b/README_JA.md
index 505887d2..a819490f 100644
--- a/README_JA.md
+++ b/README_JA.md
@@ -270,7 +270,27 @@ Lifecycle は進行、待機、リトライ、終端結果を切り分けます:
![Lifecycle の例](docs/assets/archify-lifecycle.png)
-3.1 で追加された例: [`ERD`](https://archify.si/gallery/artifacts/orders.erd.html) · [`Class`](examples/class-payments-rendered.html) · [`Tree`](examples/tree-payment-platform-rendered.html) · [`Timeline`](examples/timeline-payment-incident-rendered.html) · [`Waterfall`](examples/waterfall-checkout-request-rendered.html)。Timeline と Waterfall の例は説明用のデータを使用しています。ログやトレースに基づく時刻や所要時間だけを実データとして扱ってください。
+3.1 で追加された ERD は、テーブル、すべてのカラムとキー、リレーションのカーディナリティをまとめて示します:
+
+![ERD の例: customer、order、payment、inventory、product、order_item テーブルをドメインごとにまとめた注文管理スキーマ](docs/assets/archify-erd.png)
+
+Class は契約、主要メンバー、どの型がそれに依存し実装しているかを示します:
+
+![Class の例: OrderService が PaymentGateway インターフェースに依存し、カードとウォレットのゲートウェイが実装する](docs/assets/archify-class.png)
+
+Tree は機能の分解のような、親が 1 つの包含関係を示します:
+
+![Tree の例: 注文、決済、運用の機能に分解された決済プラットフォーム](docs/assets/archify-tree.png)
+
+Timeline はイベントを比例した 1 本の時間軸に置き、ソースごとにレーンを分けます:
+
+![Timeline の例: リリース、監視、対応のイベントを 1 本の時間軸に並べた説明用の決済障害](docs/assets/archify-timeline.png)
+
+Waterfall はネストし重なり合うスパンのどこに時間がかかったかを示します:
+
+![Waterfall の例: 在庫照会と割引計算が並行して走るチェックアウトリクエストの説明用の所要時間](docs/assets/archify-waterfall.png)
+
+サンプルを開く: [`ERD`](https://archify.si/gallery/artifacts/orders.erd.html) · [`Class`](examples/class-payments-rendered.html) · [`Tree`](examples/tree-payment-platform-rendered.html) · [`Timeline`](examples/timeline-payment-incident-rendered.html) · [`Waterfall`](examples/waterfall-checkout-request-rendered.html)。Timeline と Waterfall の例は説明用のデータを使用しています。ログやトレースに基づく時刻や所要時間だけを実データとして扱ってください。
Architecture の例: [`web-app`](examples/web-app.html) · [`Archify pipeline`](examples/archify-repo.html) · [`grid placement`](examples/archify-repo-grid.html) · [`desktop agent`](examples/maka-architecture.html)
diff --git a/README_ZH.md b/README_ZH.md
index 4dacc55d..9a4b95bb 100644
--- a/README_ZH.md
+++ b/README_ZH.md
@@ -305,7 +305,27 @@ Lifecycle 区分正常进展、等待、重试和终态:
![Lifecycle 示例](docs/assets/archify-lifecycle.png)
-3.1 新增示例:[`ERD`](https://archify.si/gallery/artifacts/orders.erd.html) · [`Class`](examples/class-payments-rendered.html) · [`Tree`](examples/tree-payment-platform-rendered.html) · [`Timeline`](examples/timeline-payment-incident-rendered.html) · [`Waterfall`](examples/waterfall-checkout-request-rendered.html)。其中 Timeline 和 Waterfall 示例使用示意数据;只有来自日志或链路追踪的时间和耗时,才能当作真实数据。
+3.1 新增的 ERD 把表、每个字段与键、以及关系基数放在一起:
+
+![ERD 示例:订单管理库,customer、order、payment、inventory、product 和 order_item 表按业务域分组](docs/assets/archify-erd.png)
+
+Class 展示接口契约、关键成员,以及哪些类型依赖或实现它们:
+
+![Class 示例:OrderService 依赖 PaymentGateway 接口,由银行卡和钱包网关实现](docs/assets/archify-class.png)
+
+Tree 展示单一父级的包含关系,例如能力拆解:
+
+![Tree 示例:支付平台拆解为订单、支付和运营能力](docs/assets/archify-tree.png)
+
+Timeline 把事件放在同一条按比例的时间轴上,每个来源一条泳道:
+
+![Timeline 示例:一次示意性的支付故障,发布、监控和响应事件位于同一时间轴](docs/assets/archify-timeline.png)
+
+Waterfall 展示嵌套、重叠的 Span 中时间花在了哪里:
+
+![Waterfall 示例:一次结账请求的示意耗时,库存查询与折扣计算并发执行](docs/assets/archify-waterfall.png)
+
+打开这些示例:[`ERD`](https://archify.si/gallery/artifacts/orders.erd.html) · [`Class`](examples/class-payments-rendered.html) · [`Tree`](examples/tree-payment-platform-rendered.html) · [`Timeline`](examples/timeline-payment-incident-rendered.html) · [`Waterfall`](examples/waterfall-checkout-request-rendered.html)。其中 Timeline 和 Waterfall 示例使用示意数据;只有来自日志或链路追踪的时间和耗时,才能当作真实数据。
Architecture 示例:[`Web App`](examples/web-app.html) · [`Archify Pipeline`](examples/archify-repo.html) · [`Grid 布局`](examples/archify-repo-grid.html) · [`桌面 Agent`](examples/maka-architecture.html)
diff --git a/docs/assets/archify-class.png b/docs/assets/archify-class.png
new file mode 100644
index 00000000..da888a4a
Binary files /dev/null and b/docs/assets/archify-class.png differ
diff --git a/docs/assets/archify-erd.png b/docs/assets/archify-erd.png
new file mode 100644
index 00000000..cc91db9d
Binary files /dev/null and b/docs/assets/archify-erd.png differ
diff --git a/docs/assets/archify-timeline.png b/docs/assets/archify-timeline.png
new file mode 100644
index 00000000..5f9e2b56
Binary files /dev/null and b/docs/assets/archify-timeline.png differ
diff --git a/docs/assets/archify-tree.png b/docs/assets/archify-tree.png
new file mode 100644
index 00000000..b3c8e3ed
Binary files /dev/null and b/docs/assets/archify-tree.png differ
diff --git a/docs/assets/archify-waterfall.png b/docs/assets/archify-waterfall.png
new file mode 100644
index 00000000..6fee6c52
Binary files /dev/null and b/docs/assets/archify-waterfall.png differ