Rivet Dev Skills

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web…

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking…

Build an AI agent backend with persistent memory: one Rivet Actor per conversation, queued message handling, and streaming LLM responses as realtime events.

Build an AI agent backend with persistent memory: one Rivet Actor per conversation, queued message handling, and streaming LLM responses as realtime events.

Give every AI agent its own computer: a persistent workspace with a filesystem, processes, shells, networking, and agent sessions on a lightweight in-process…

Give every AI agent its own computer: a persistent workspace with a filesystem, processes, shells, networking, and agent sessions on a lightweight in-process…

Build a realtime chat room backend with Rivet Actors: one actor per room, SQLite-backed message history, and WebSocket broadcast to every connected client.

Build a realtime chat room backend with Rivet Actors: one actor per room, SQLite-backed message history, and WebSocket broadcast to every connected client.

Build a collaborative text editor backend with Yjs CRDTs and Rivet Actors: per-document actors relay sync and awareness updates and persist snapshots.

Build a collaborative text editor backend with Yjs CRDTs and Rivet Actors: per-document actors relay sync and awareness updates and persist snapshots.

Durable cron jobs with Rivet Actors: schedule.after and schedule.at timers survive restarts and crashes, plus re-arming recurring jobs and idempotent handlers.

Patterns for durable one-shot, calendar, and fixed-interval work on Rivet Actors.

Methodically run the RivetKit driver test suite file by file across the native (NAPI) and wasm runtimes, tracking progress in…

Methodically run the RivetKit driver test suite file by file across the native (NAPI) and wasm runtimes, tracking progress in…

Live cursors and multiplayer presence with Rivet Actors: per-connection cursor state, realtime updates over events or raw WebSockets, and throttling.

Live cursors and multiplayer presence with Rivet Actors: per-connection cursor state, realtime updates over events or raw WebSockets, and throttling.

Pragmatic patterns for building multiplayer games: matchmaking, tick loops, realtime state, interest management, and validation. Includes starter code and architecture patterns for 10 game types (battle royale, arena, IO style, open world, party, physics 2D/3D, ranked, turn-based, idle) with actor topology, lifecycle diagrams, and netcode strategies. Covers server simulation fundamentals: fixed realtime loops vs. action-driven updates, physics engine selection (Rapier 2D/3D), and spatial...

Pragmatic patterns for building multiplayer games: matchmaking, tick loops, realtime state, interest management, and validation.

Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

Archive multiple completed changes at once. Use when archiving several parallel changes.

Archive multiple completed changes at once. Use when archiving several parallel changes.

Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue…

Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue…

Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through…

Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through…

Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through…

Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through…

Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured…

Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured…

Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.

Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.

Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.

Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.

Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.

Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.

Multi-tenant data isolation with one Rivet Actor per tenant: the actor key is the tenant id, so each tenant gets its own isolated dataset and migrations.

Multi-tenant data isolation with one Rivet Actor per tenant: the actor key is the tenant id, so each tenant gets its own isolated dataset and migrations.

Actors: The primitive for stateful workloads.

agentOS: Agent execution, filesystems, and orchestration.

Dynamic Apps: Deploy an AI-generated backend for every user.

Workflows: Durable, replayable multi-step operations.

Long-lived, stateful compute for AI agents, multiplayer apps, and workflow automation. Actors are persistent in-memory processes that maintain state across requests without database round trips, with automatic scaling from zero to millions of concurrent instances. Built-in realtime communication via WebSockets and events, durable queues for ordered message processing, and SQLite for structured data queries. State persists across restarts and crashes through Rivet Cloud or self-hosted...

RivetKit backend and Rivet Actor runtime guidance. Use for building, modifying, debugging, or testing Rivet Actors, registries, serverless/runner modes,…

Build stateful backends with Rivet Actors: high-performance, long-lived, in-memory, persisted processes. Use when you outgrow HTTP, databases, or queues.…

Build stateful backends with Rivet Actors: high-performance, long-lived, in-memory, persisted processes. Use when you outgrow HTTP, databases, or queues.…

JavaScript client for connecting to Rivet Actors with stateless or stateful connections. Supports browser, Node.js, and Bun environments with automatic endpoint detection via environment variables or explicit configuration Offers two interaction modes: stateless action calls for independent requests and stateful connections with real-time event subscriptions Includes low-level HTTP and WebSocket access for actors implementing onRequest or onWebSocket handlers Provides compound array-based...

RivetKit JavaScript client guidance. Use for browser, Node.js, or Bun clients that connect to Rivet Actors with rivetkit/client, create clients, call actions,…

React client for connecting to Rivet Actors with hooks and realtime state management. Create typed hooks with createRivetKit() and connect to actor instances using useActor() with keys and optional parameters Subscribe to actor events with useEvent() and monitor connection lifecycle through connStatus and error states Use createClient() for stateless one-off calls, actor discovery methods (get, getOrCreate, create, getForId), and low-level HTTP/WebSocket access Supports compound array keys...

RivetKit React client guidance. Use for React apps that connect to Rivet Actors with @rivetkit/react, create hooks with createRivetKit, or manage realtime…

RivetKit Rust client guidance. Use for Rust clients and backends that connect to Rivet Actors with rivetkit::client, create typed actor handles, call actions,…

RivetKit Rust client guidance. Use for Rust clients and backends that connect to Rivet Actors with rivetkit::client, create typed actor handles, call actions,…

Swift client for connecting to Rivet Actors with stateless and stateful connection modes. Supports both stateless action calls and persistent WebSocket connections with real-time event streaming via AsyncStream Provides typed action calls with 0–5 positional arguments, plus raw JSON fallback for larger argument counts Includes connection lifecycle monitoring through status changes, errors, opens, and closes streams Supports low-level HTTP and WebSocket access for custom onRequest and...

RivetKit Swift client guidance. Use for Swift clients that connect to Rivet Actors with RivetKitClient, create actor handles, call actions, or manage…

SwiftUI client library for connecting to Rivet Actors with reactive bindings and event streaming. Provides @Actor property wrapper for get-or-create semantics with connection lifecycle management, plus view modifiers for environment setup and event subscription Supports typed async actions, fire-and-forget sends, and AsyncStream event subscriptions with 0–5 typed arguments Includes connection status tracking, error handling via ActorError , and compound key support for hierarchical actor...

RivetKit SwiftUI client guidance. Use for SwiftUI apps that connect to Rivet Actors with RivetKitSwiftUI, @Actor, rivetKit view modifiers, and SwiftUI bindings.

Use this skill for RivetKit building, modification, debugging, testing, or performance analysis. Trigger on RivetKit imports, Rivet/actor discussion,…

Universal API for orchestrating multiple AI coding agents in sandboxed environments. Supports four coding agents (Claude Code, Codex, OpenCode, Amp) with a unified schema for responses, events, and session management Deploy locally or to cloud sandboxes including E2B, Daytona, Docker, Vercel, and Cloudflare with environment-specific configuration Stream agent events, manage session persistence across multiple backends (in-memory, SQLite, Postgres, IndexedDB), and handle human-in-the-loop...

Run an E2E smoke test that installs rivetkit packages from npm in an isolated temp project, starts the hello-world counter actor, then verifies both HTTP…

Run an E2E smoke test that installs rivetkit packages from npm in an isolated temp project, starts the hello-world counter actor, then verifies both HTTP…

Bulk-merge a Graphite stack into main via admin-bypass fast-forward push. Replaces the Graphite merge queue for rivet-dev/rivet. Invoke when the user says…

Bulk-merge a Graphite stack into main via admin-bypass fast-forward push. Replaces the Graphite merge queue for rivet-dev/rivet. Invoke when the user says…

Run Rivet entirely inside your own perimeter: single-binary or Docker Compose install, file system storage with no database infrastructure, and no outbound…

Run Rivet entirely inside your own perimeter: single-binary or Docker Compose install, file system storage with no database infrastructure, and no outbound…