Iii Architecture Patterns

作者 iii-hqf95eab270f73無授權條款18K 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫今天更新

Use when composing iii primitives into backend architectures: durable workflows, reactive backends, agentic pipelines, event-driven CQRS, effect pipelines, and trigger-transform-action automation.

僅含說明Software DevelopmentAI & Agents
AI 產生的概覽

指導選擇並實作 iii 後端架構模式，例如持久化工作流程、CQRS 與代理式管線。

功能
此技能會把後端需求對應到 iii 架構模式，包括持久化工作流程、反應式後端、代理式後端、事件驅動 CQRS、效果管線，以及觸發器-轉換-動作自動化。它提供模式對照表、選擇規則，以及 TypeScript、Python 與 Rust 的程式碼範例，示範如何組合函式、觸發器、工作器、狀態、佇列、串流與發布/訂閱等 iii 基本元件。它產出的是架構指引與實作草稿，而非可直接執行的成品。
適用情境
當任務規模超過單一函式或觸發器、需要完整後端模式時使用。它適合描述產品行為的需求，例如工作流程、代理式系統、反應式應用程式、CQRS、效果管線或自動化鏈。它不適用於精確的觸發器設定、引擎設定或特定套件的 SDK 語法，這些由其他技能涵蓋。
執行需求
不隨附指令碼，僅為說明性指示。範例假定已有 iii 執行環境與 SDK（TypeScript 用 iii-sdk，Python 用 iii，Rust 用 iii_sdk），以及正在運作的 iii 工作器端點，例如 ws://localhost:49134。

Architecture Patterns

Use this skill when the task is larger than one function or trigger. Pick the pattern from the requirement, then implement it with Function, Trigger, Worker, state, queues, streams, and pub/sub.

Pattern Map

RequirementPatterniii shape
Sequential work with retries, DLQ, step trackingDurable workflowFunctions chained through named queues, progress in state
Keep views, metrics, cache, or clients in syncReactive backendState triggers plus stream/pubsub side effects
Specialized AI agents hand work to each otherAgentic backendOne function per agent, queue handoffs, shared state
Commands publish events and projections update independentlyEvent-driven CQRSCommand functions, event log in state, subscribe triggers
Pure, traceable compositionEffect pipelineSmall functions composed synchronously with trigger()
Webhook/cron automation chainsLow-code automationTrigger, transform, action nodes chained by enqueue

Durable Workflow

Use named queues when steps need different retry, FIFO, or concurrency policy.

TypeScript

typescript
import { registerWorker, TriggerAction } from "iii-sdk";
const iii = registerWorker("ws://localhost:49134", { workerName: "order-workflow" });
async function track(orderId: string, step: string, status: string) {  await iii.trigger({    function_id: "state::update",    payload: { scope: "orders", key: orderId, ops: [{ type: "merge", path: ["steps"], value: { [step]: status } }] },  });}
iii.registerFunction("orders::validate", async (order) => {  await track(order.id, "validate", "done");  return iii.trigger({    function_id: "orders::charge",    payload: order,    action: TriggerAction.Enqueue({ queue: "order-payment" }),  });});
iii.registerFunction("orders::charge", async (order) => {  await track(order.id, "payment", "done");  return iii.trigger({    function_id: "orders::ship",    payload: order,    action: TriggerAction.Enqueue({ queue: "order-ship" }),  });});

Python

python
from iii import register_worker
iii = register_worker("ws://localhost:49134")
def track(order_id, step, status):    iii.trigger({        "function_id": "state::update",        "payload": {            "scope": "orders",            "key": order_id,            "ops": [{"type": "merge", "path": ["steps"], "value": {step: status}}],        },    })
def validate(order):    track(order["id"], "validate", "done")    return iii.trigger({        "function_id": "orders::charge",        "payload": order,        "action": {"type": "enqueue", "queue": "order-payment"},    })
iii.register_function("orders::validate", validate)

Rust

rust
use iii_sdk::TriggerAction;use iii_sdk::protocol::TriggerRequest;use serde_json::json;
async fn enqueue_charge(iii: iii_sdk::IIIClient, order: serde_json::Value) -> Result<serde_json::Value, iii_sdk::Error> {    iii.trigger(TriggerRequest {        function_id: "state::update".into(),        payload: json!({            "scope": "orders",            "key": order["id"],            "ops": [{ "type": "merge", "path": ["steps"], "value": { "validate": "done" } }]        }),        action: None,        timeout_ms: None,    }).await?;
    iii.trigger(TriggerRequest {        function_id: "orders::charge".into(),        payload: order,        action: Some(TriggerAction::Enqueue { queue: "order-payment".into() }),        timeout_ms: None,    }).await}

Reactive Backend

Use state triggers when the requirement says "after create/update, do this", "avoid polling", or "push live updates".

typescript
iii.registerFunction("todos::on-change", async (event) => {  await iii.trigger({    function_id: "stream::send",    payload: { stream_name: "todos-live", group_id: "default", data: event.new_value },    action: TriggerAction.Void(),  });});
iii.registerTrigger({  type: "state",  function_id: "todos::on-change",  config: { scope: "todos" },});

Agentic Backend

Model each agent as a function with one responsibility. Store shared context in state and hand off work through named queues.

typescript
iii.registerFunction("agents::researcher", async (task) => {  await iii.trigger({    function_id: "state::set",    payload: { scope: "research", key: task.id, value: { findings: [] } },  });  return iii.trigger({    function_id: "agents::critic",    payload: task,    action: TriggerAction.Enqueue({ queue: "agent-tasks" }),  });});

Event-Driven CQRS

Commands validate and publish domain events. Projections subscribe independently and write query-optimized state.

typescript
iii.registerFunction("cmd::add-inventory-item", async (input) => {  const event = { type: "inventory.item-added", itemId: input.itemId, quantity: input.quantity };  await iii.trigger({    function_id: "state::set",    payload: { scope: "inventory-events", key: `${Date.now()}-${input.itemId}`, value: event },  });  await iii.trigger({ function_id: "publish", payload: { topic: event.type, data: event } });  return { accepted: true };});
iii.registerTrigger({  type: "subscribe",  function_id: "proj::inventory-list",  config: { topic: "inventory.item-added" },});

Selection Rules

  • Use sync composition for short effect pipelines where the caller needs the final result.
  • Use enqueue for unreliable, slow, or must-complete steps.
  • Use pub/sub for independent fan-out where each subscriber can tolerate event-style delivery.
  • Use state triggers for derived views and side effects that should run automatically after writes.
  • Use cron triggers for scheduled maintenance and periodic starts.
  • Keep each function small enough to test independently.

When to Use

  • Use this skill for complete backend patterns: workflows, agentic systems, reactive apps, CQRS, effect pipelines, and automation chains.
  • Use this when the request describes product behavior rather than a single SDK API call.

Boundaries

  • For exact trigger config, function registration syntax, custom triggers, channels, and HTTP-invoked functions, use iii-core-primitives.
  • For engine ports, adapters, engine-owned workers, and RBAC (rbac-proxy), use iii-engine-config; queue retry and FIFO policy live with the queue worker's docs.
  • For package-specific SDK syntax, use iii-sdk-reference.
  • Worker-backed capability details live with the worker docs, not as top-level iii skills.

來源與署名

來源：iii-hq/iii位於skills/iii-architecture-patterns提交f95eab2

授權條款： 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架

更多來自 iii-hq/iii 的技能

Iii Sdk Reference

iii-hq

iii SDK 跨 Node.js、瀏覽器、Python 與 Rust 的 API 參考，涵蓋安裝、worker、觸發器與通道。

Software Development18K今天更新

Iii Error Handling

iii-hq

說明如何處理 Node、Python、Rust 與瀏覽器 worker 中的 iii 引擎與 SDK 錯誤。

Software Development18K今天更新

Iii Engine Config

iii-hq

Configure a managed iii engine through worker-compose.yaml or a directly supervised engine through config.yaml. Use for engine ports, RBAC via the rbac-proxy worker, streams, sandboxes, and configuration storage.

待分類18K今天更新

Iii Core Primitives

iii-hq

iii 核心原語參考：註冊函式、綁定觸發器、呼叫模式與 worker。

Software Development18K今天更新

更多Software Development技能

Playground

anthropics

精選

建立自成一體的互動式 HTML 遊樂場，包含控制項、即時預覽與可複製的提示詞輸出。

Software Development37K今天更新

M5 Onboard

anthropics

精選

透過 USB 偵測 M5Stack ESP32 開發板，燒錄 UIFlow 2.0 韌體並安裝 MicroPython 應用程式套件。

Software Development37K今天更新

Cardputer Buddy

anthropics

精選

指導迭代 Cardputer-Adv 的 MicroPython 應用程式套件：新增應用程式、透過 USB 序列埠推送檔案、查看日誌並執行 REPL 指令。

Software Development37K今天更新

Web Design Guidelines

vercel-labs

精選

依據從遠端來源取得的 Web Interface Guidelines 審查 UI 程式碼，並以 file:line 形式回報問題。

Software Development32K5 週前更新

Vercel React Native Skills

vercel-labs

精選

React Native 與 Expo 最佳實務規則，涵蓋清單效能、動畫、導覽、UI 模式、狀態與 monorepo 設定。

Software Development32K5 週前更新

Vercel React Best Practices

vercel-labs

精選

Vercel 的 React 與 Next.js 效能指南，以 70 條規則的形式用於撰寫、審查與重構程式碼。

Software Development32K5 週前更新