iii-worker-lockfile
๐ฏSkillfrom iii-hq/iii
iii is a shared runtime platform that lets you compose, extend, and observe every service in your stack in real time, collapsing queues, cron, HTTP, agents, and sandboxes into one live system surface.
Same repository
iii-hq/iii(23 items)
Installation
npx vibeindex add iii-hq/iii --skill iii-worker-lockfilenpx skills add iii-hq/iii --skill iii-worker-lockfile~/.claude/skills/iii-worker-lockfile/SKILL.mdSKILL.md
More from this repository10
Guides configuring the iii backend engine, which unifies API routing, task queues, cron scheduling, pub/sub, state management, and observability into a single process using Function, Trigger, and Worker primitives.
Part of iii, a composable runtime that lets you add workers (services, agents, sandboxes) to a live catalog where they discover and call each other instantly through three primitives: Workers, Functions, and Triggers.
SDK reference for the iii platform covering Node.js, browser, Python, and Rust clients with APIs for worker initialization, function/trigger registration, invocation, channels, logging, and OpenTelemetry integration.
Provides architecture patterns for composing iii primitives into backend systems including durable workflows, reactive backends, agentic pipelines, event-driven CQRS, effect pipelines, and trigger-transform-action automation.
Covers trigger action modes in the iii backend engine, including fire-and-forget (Void), durable async (Enqueue), and direct invocation patterns for controlling how functions are executed across workers.
Guides building durable workflow orchestration on the iii engine, chaining functions across distributed workers with automatic retry handling, state management, and end-to-end observability.
Browser-optimized SDK for connecting web applications to the iii engine via WebSocket, enabling frontend code to register functions, invoke server-side triggers, and consume real-time streams.
Skill for configuring trigger conditions in the iii backend engine, defining when functions execute based on event sources like HTTP requests, cron schedules, queue messages, and state changes.
Guides creating custom trigger types in the iii backend engine beyond built-in HTTP, cron, and queue triggers, allowing developers to define domain-specific event sources that fire functions.
Covers the core Function and Trigger primitives of the iii backend engine, teaching how to define units of work, bind them to event sources (HTTP, cron, queue, state change), and orchestrate execution across distributed workers.