Turn any idea, plan, or codebase into a beautiful interactive diagram. An agent skill for Claude Code, Codex, and more.
HTML agent-skillsai-agentsarchitecture-diagramclaude-codeclaude-skillscodexcoding-agentsdeepseek-harnessdeveloper-toolsdiagramsdiagrams-as-codedsh-pluginflowchartllmmermaidopencodesequence-diagramsoftware-architecturesystem-designvisualization
docs(readme): list all ten diagram types in the chooser
tt-a1i37f882ff921d
diff --git a/README.md b/README.mdindex 8cc81ca6..4acb9c72 100644--- a/README.md+++ b/README.md@@ -257,7 +257,7 @@ Continue with focused requests such as `add Redis`, `move auth to the left`, or## Choose the right diagram<details>-<summary>Five diagram types, architecture comparisons, and examples</summary>+<summary>Ten diagram types, architecture comparisons, and examples</summary>| Type | Best for | Include in your prompt |@@ -267,6 +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 |+| **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 |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).@@ -299,6 +304,8 @@ Lifecycle separates progress, waits, retries, and terminal outcomes:+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.+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)</details>diff --git a/README_EN.md b/README_EN.mdindex 8cc81ca6..4acb9c72 100644--- a/README_EN.md+++ b/README_EN.md@@ -257,7 +257,7 @@ Continue with focused requests such as `add Redis`, `move auth to the left`, or## Choose the right diagram<details>-<summary>Five diagram types, architecture comparisons, and examples</summary>+<summary>Ten diagram types, architecture comparisons, and examples</summary>| Type | Best for | Include in your prompt |@@ -267,6 +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 |+| **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 |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).@@ -299,6 +304,8 @@ Lifecycle separates progress, waits, retries, and terminal outcomes:+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.+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)</details>diff --git a/README_JA.md b/README_JA.mdindex 457d4ee0..e654991f 100644--- a/README_JA.md+++ b/README_JA.md@@ -223,7 +223,7 @@ Put supporting detail in cards instead of adding more edges.## 適切な図を選ぶ<details>-<summary>5 種類の図、アーキテクチャの比較、サンプル</summary>+<summary>10 種類の図、アーキテクチャの比較、サンプル</summary>| 種類 | 向いている対象 | プロンプトに含めるもの |@@ -233,6 +233,11 @@ Put supporting detail in cards instead of adding more edges.| **Sequence** | API 呼び出し、キャッシュフォールバック、認証、非同期トレース | 呼び出し元、呼び出し先、戻り、タイミング || **Data Flow** | パイプライン、リネージ、PII、コンシューマ | ソース、変換、ストア、境界 || **Lifecycle** | 状態、リトライ、待機、終端結果 | 状態、イベント、リトライとキャンセルの経路 |+| **ERD** | データベーススキーマ: テーブル、カラム、キー、カーディナリティ | テーブル、各カラムと型、主キーと外部キー |+| **Class** | クラス、インターフェース、主要メンバー、型同士の関係 | 型、主要メンバー、継承・コンポジション・依存 |+| **Tree** | 親が 1 つの階層: リポジトリ、モジュール、機能の分解 | ルート、階層、各ブランチの中身 |+| **Timeline** | いつ何が起きたか: インシデントレビュー、リリース履歴 | タイムスタンプ、イベント、ソースレーン |+| **Waterfall** | 1 つのリクエストやエージェント実行の時間の内訳 | スパン、開始時刻と所要時間、ネスト |Architecture の任意プロファイル `deployment-ownership` は、記述されたオーナー、リージョン配置、データベースのプライベートスコープ、名前付きの境界越えが欠けている場合は fail-closed で停止します。暗黙的に有効化されることはなく、ライブのインフラを検査することもありません。[検証済みのデプロイ実証](https://archify.si/gallery.html#proof-deployment-ownership)を参照してください。@@ -265,6 +270,8 @@ Lifecycle は進行、待機、リトライ、終端結果を切り分けます:+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 の例は説明用のデータです。実際のログやトレースに基づく値だけを実測値として扱ってください。+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)</details>diff --git a/README_ZH.md b/README_ZH.mdindex 03268770..cb87f633 100644--- a/README_ZH.md+++ b/README_ZH.md@@ -255,7 +255,7 @@ DeepSeek Harness(社区集成、显式启用):运行 `dsh plugin --profile## 选择合适的图表<details>-<summary>五种图表、架构差异对比与示例</summary>+<summary>十种图表、架构差异对比与示例</summary>| 类型 | 最适合 | Prompt 中应包含 |@@ -265,6 +265,11 @@ DeepSeek Harness(社区集成、显式启用):运行 `dsh plugin --profile| **Sequence** | API 调用、缓存回源、鉴权、异步链路 | 调用方、被调用方、返回、时序 || **Data Flow** | 数据管线、血缘、PII、下游消费者 | 来源、转换、存储、边界 || **Lifecycle** | 状态、重试、等待、终态 | 状态、事件、重试与取消路径 |+| **ERD** | 数据库结构:表、字段、键、基数关系 | 表、每个字段及类型、主键与外键 |+| **Class** | 类、接口、关键成员与类型关系 | 类型、关键成员、继承、组合与依赖 |+| **Tree** | 单一父级的层级结构:仓库、模块、能力拆解 | 根节点、层级、各分支包含的内容 |+| **Timeline** | 事情发生的时间:故障复盘、发布历史 | 时间点、事件、来源泳道 |+| **Waterfall** | 一次请求或 Agent 运行的耗时分布 | 区间、开始时间与时长、嵌套关系 |做生产部署评审时,Architecture 可以按需启用 `deployment-ownership`工程画像:负责人、单一区域归属、数据库私有边界或边界穿越机制缺失时会直接阻断。@@ -300,6 +305,8 @@ Lifecycle 区分正常进展、等待、重试和终态:+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 示例使用示意数据;只有来自真实日志或链路追踪的数值,才应表述为实测结果。+Architecture 示例:[`Web App`](examples/web-app.html) · [`Archify Pipeline`](examples/archify-repo.html) · [`Grid 布局`](examples/archify-repo-grid.html) · [`桌面 Agent`](examples/maka-architecture.html)</details>