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): sharpen prompt hints for the five new diagram types

tt-a1i86540fda68f1
diff --git a/README.md b/README.md
index 4acb9c72..841578cb 100644
--- a/README.md
+++ b/README.md
@@ -267,11 +267,11 @@ Continue with focused requests such as `add Redis`, `move auth to the left`, or
| **Sequence** | API calls, cache fallback, auth, async traces | Callers, callees, returns, timing |
| **Data Flow** | Pipelines, lineage, PII, consumers | Sources, transforms, stores, boundaries |
| **Lifecycle** | States, retries, waits, terminal outcomes | States, events, retry and cancellation paths |
-| **ERD** | Database schemas: tables, columns, keys, cardinality | Tables, every column with its type, primary and foreign keys |
-| **Class** | Classes, interfaces, selected members, type relationships | Types, key members, inheritance, composition, dependencies |
+| **ERD** | Database schemas: tables, columns, keys, cardinality | Tables, every column with its type, primary/foreign/unique keys, relationship cardinality |
+| **Class** | Classes, interfaces, selected members, type relationships | Types, key members, inheritance and implementations, composition, dependencies |
| **Tree** | Single-parent hierarchies: repositories, modules, capability breakdowns | Root, levels, what each branch contains |
-| **Timeline** | When things happened: incident reviews, release histories | Timestamps, events, source lanes |
-| **Waterfall** | Where the time went in one request or agent run | Spans, start times and durations, nesting |
+| **Timeline** | When things happened: incident reviews, release histories | Timestamps with time zone, events, source lanes, whether times are observed or illustrative |
+| **Waterfall** | Where the time went in one request or agent run | Spans, start times and durations, nesting, whether timings are measured or illustrative |
Architecture's optional `deployment-ownership` profile fails closed when authored owners, region placement, private database scope, or named crossings are missing; it is never implicit and does not inspect live infrastructure. See the [checked deployment proof](https://archify.si/gallery.html#proof-deployment-ownership).
@@ -304,7 +304,7 @@ Lifecycle separates progress, waits, retries, and terminal outcomes:
![Lifecycle example](docs/assets/archify-lifecycle.png)
-New in 3.1: [`ERD`](examples/erd-orders-rendered.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; present values as measured only when they come from real logs or traces.
+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.
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 4acb9c72..841578cb 100644
--- a/README_EN.md
+++ b/README_EN.md
@@ -267,11 +267,11 @@ Continue with focused requests such as `add Redis`, `move auth to the left`, or
| **Sequence** | API calls, cache fallback, auth, async traces | Callers, callees, returns, timing |
| **Data Flow** | Pipelines, lineage, PII, consumers | Sources, transforms, stores, boundaries |
| **Lifecycle** | States, retries, waits, terminal outcomes | States, events, retry and cancellation paths |
-| **ERD** | Database schemas: tables, columns, keys, cardinality | Tables, every column with its type, primary and foreign keys |
-| **Class** | Classes, interfaces, selected members, type relationships | Types, key members, inheritance, composition, dependencies |
+| **ERD** | Database schemas: tables, columns, keys, cardinality | Tables, every column with its type, primary/foreign/unique keys, relationship cardinality |
+| **Class** | Classes, interfaces, selected members, type relationships | Types, key members, inheritance and implementations, composition, dependencies |
| **Tree** | Single-parent hierarchies: repositories, modules, capability breakdowns | Root, levels, what each branch contains |
-| **Timeline** | When things happened: incident reviews, release histories | Timestamps, events, source lanes |
-| **Waterfall** | Where the time went in one request or agent run | Spans, start times and durations, nesting |
+| **Timeline** | When things happened: incident reviews, release histories | Timestamps with time zone, events, source lanes, whether times are observed or illustrative |
+| **Waterfall** | Where the time went in one request or agent run | Spans, start times and durations, nesting, whether timings are measured or illustrative |
Architecture's optional `deployment-ownership` profile fails closed when authored owners, region placement, private database scope, or named crossings are missing; it is never implicit and does not inspect live infrastructure. See the [checked deployment proof](https://archify.si/gallery.html#proof-deployment-ownership).
@@ -304,7 +304,7 @@ Lifecycle separates progress, waits, retries, and terminal outcomes:
![Lifecycle example](docs/assets/archify-lifecycle.png)
-New in 3.1: [`ERD`](examples/erd-orders-rendered.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; present values as measured only when they come from real logs or traces.
+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.
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 e654991f..505887d2 100644
--- a/README_JA.md
+++ b/README_JA.md
@@ -233,11 +233,11 @@ Put supporting detail in cards instead of adding more edges.
| **Sequence** | API 呼び出し、キャッシュフォールバック、認証、非同期トレース | 呼び出し元、呼び出し先、戻り、タイミング |
| **Data Flow** | パイプライン、リネージ、PII、コンシューマ | ソース、変換、ストア、境界 |
| **Lifecycle** | 状態、リトライ、待機、終端結果 | 状態、イベント、リトライとキャンセルの経路 |
-| **ERD** | データベーススキーマ: テーブル、カラム、キー、カーディナリティ | テーブル、各カラムと型、主キーと外部キー |
-| **Class** | クラス、インターフェース、主要メンバー、型同士の関係 | 型、主要メンバー、継承・コンポジション・依存 |
+| **ERD** | データベーススキーマ: テーブル、カラム、キー、カーディナリティ | テーブル、各カラムと型、主キー・外部キー・ユニークキー、リレーションのカーディナリティ |
+| **Class** | クラス、インターフェース、主要メンバー、型同士の関係 | 型、主要メンバー、継承とインターフェース実装、コンポジション、依存 |
| **Tree** | 親が 1 つの階層: リポジトリ、モジュール、機能の分解 | ルート、階層、各ブランチの中身 |
-| **Timeline** | いつ何が起きたか: インシデントレビュー、リリース履歴 | タイムスタンプ、イベント、ソースレーン |
-| **Waterfall** | 1 つのリクエストやエージェント実行の時間の内訳 | スパン、開始時刻と所要時間、ネスト |
+| **Timeline** | いつ何が起きたか: インシデントレビュー、リリース履歴 | タイムゾーン付きのタイムスタンプ、イベント、ソースレーン、時刻が実測か説明用か |
+| **Waterfall** | 1 つのリクエストやエージェント実行の時間の内訳 | スパン、開始時刻と所要時間、ネスト、所要時間が実測か説明用か |
Architecture の任意プロファイル `deployment-ownership` は、記述されたオーナー、リージョン配置、データベースのプライベートスコープ、名前付きの境界越えが欠けている場合は fail-closed で停止します。暗黙的に有効化されることはなく、ライブのインフラを検査することもありません。[検証済みのデプロイ実証](https://archify.si/gallery.html#proof-deployment-ownership)を参照してください。
@@ -270,7 +270,7 @@ Lifecycle は進行、待機、リトライ、終端結果を切り分けます:
![Lifecycle の例](docs/assets/archify-lifecycle.png)
-3.1 で追加された例: [`ERD`](examples/erd-orders-rendered.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`](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 cb87f633..4dacc55d 100644
--- a/README_ZH.md
+++ b/README_ZH.md
@@ -265,11 +265,11 @@ DeepSeek Harness(社区集成、显式启用):运行 `dsh plugin --profile
| **Sequence** | API 调用、缓存回源、鉴权、异步链路 | 调用方、被调用方、返回、时序 |
| **Data Flow** | 数据管线、血缘、PII、下游消费者 | 来源、转换、存储、边界 |
| **Lifecycle** | 状态、重试、等待、终态 | 状态、事件、重试与取消路径 |
-| **ERD** | 数据库结构:表、字段、键、基数关系 | 表、每个字段及类型、主键与外键 |
-| **Class** | 类、接口、关键成员与类型关系 | 类型、关键成员、继承、组合与依赖 |
+| **ERD** | 数据库结构:表、字段、键、基数关系 | 表、每个字段及类型、主键/外键/唯一键、关系基数 |
+| **Class** | 类、接口、关键成员与类型关系 | 类型、关键成员、继承与接口实现、组合与依赖 |
| **Tree** | 单一父级的层级结构:仓库、模块、能力拆解 | 根节点、层级、各分支包含的内容 |
-| **Timeline** | 事情发生的时间:故障复盘、发布历史 | 时间点、事件、来源泳道 |
-| **Waterfall** | 一次请求或 Agent 运行的耗时分布 | 区间、开始时间与时长、嵌套关系 |
+| **Timeline** | 何时发生了什么:故障复盘、发布历史 | 带时区的时间点、事件、来源泳道,以及时间是真实观测还是示意 |
+| **Waterfall** | 一次请求或 Agent 运行的耗时分布 | Span、开始时间与时长、嵌套关系,以及耗时是实测还是示意 |
做生产部署评审时,Architecture 可以按需启用 `deployment-ownership`
工程画像:负责人、单一区域归属、数据库私有边界或边界穿越机制缺失时会直接阻断。
@@ -305,7 +305,7 @@ Lifecycle 区分正常进展、等待、重试和终态:
![Lifecycle 示例](docs/assets/archify-lifecycle.png)
-3.1 新增示例:[`ERD`](examples/erd-orders-rendered.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`](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)