iii-architecture-patterns

This skill guides an agent in composing iii's backend primitives into complete architectures when a task is larger than a single function or trigger. It solves the problem of mapping a product requirement to the right backend shape by offering a pattern map: durable workflows, reactive backends, agentic pipelines, event-driven CQRS, effect pipelines, and low-code trigger-transform-action automation. Each pattern is expressed in terms of iii's Function, Trigger, Worker, state, queues, streams, and pub/sub building blocks.

For each pattern it provides concrete implementations. Durable workflows chain functions through named queues with progress tracked in state, shown in TypeScript, Python, and Rust. Reactive backends use state triggers plus stream or pub/sub side effects to push live updates and avoid polling. Agentic backends model each agent as a single-responsibility function handing off work through named queues with shared context in state. Event-driven CQRS has command functions publish domain events that independent projection triggers consume. Selection rules explain when to use synchronous composition, enqueue for reliable must-complete steps, pub/sub for fan-out, state triggers for derived views, and cron for scheduled work, while keeping each function independently testable. Boundary notes point to sibling skills for exact trigger config, engine config, and SDK reference.

The target users are backend developers building on the iii platform who need to design workflows, agentic systems, reactive apps, CQRS, effect pipelines, or automation chains across TypeScript, Python, and Rust. Use cases arise when a request describes product behavior rather than a single SDK call.