rivet-actors
by rivet-dev
Actors: The primitive for stateful workloads.
npx skills add https://github.com/rivet-dev/skills --skill rivet-actorsDocumentation
- Actors
- Actions
- Actor Configuration
- Icons & Names
- Authentication
- Clients
- Node.js & Bun
- React
- Rust
- Swift
- SwiftUI
- Communicating Between Actors
- Connections
- Cross-Origin Resource Sharing
- Crash Course
- Debugging Actors
- KV
- preventSleep
- Queues
- run
- State
- Design Patterns
- Destroying Actors
- Environment Variables
- Errors
- Realtime
- HTTP Server
- Input Parameters
- Actor Keys
- Low-Level KV Storage
- Lifecycle
- Limits
- Logging
- Metadata
- Performance Monitoring & Tuning
- Permissions
- Production Checklist
- Queues & Run Loops
- Node.js & Bun Quickstart
- Effect.ts Quickstart (Beta)
- React Quickstart
- Rust Quickstart
- Registry Configuration
- Low-Level HTTP Request Handler
- Schedule & Cron
- SQLite
- SQLite + Drizzle
- SQLite Profiling
- In-Memory State
- Testing
- Troubleshooting
- Types
- WASM vs Native SDK
- Low-Level WebSocket Handler
- A Radically Simpler Architecture
- AI Agent
- Arena Game
- Authenticate Users End to End
- Battle Royale
- Chat Room
- Collaborative Text Editor (CRDT)
- Collaborative Text Editor (OT)
- Cron Jobs and Scheduled Tasks
- Idle Game
- IO Game
- Live Cursors and Presence
- Open World Game
- Party Game
- Database per Tenant
- 2D Physics Game
- 3D Physics Game
- Ranked Matchmaking
- Turn-Based Game
Examples
Runnable code the documentation above embeds, mirrored under examples/ in this skill directory.
- examples/chat-room
- examples/collaborative-document
- examples/collaborative-document-ot
- examples/cursors
- examples/docs/actors-actions
- examples/docs/actors-appearance
- examples/docs/actors-communicating-between-actors
- examples/docs/actors-connections
- examples/docs/actors-crash-course
- examples/docs/actors-deprecated-kv
- examples/docs/actors-deprecated-prevent-sleep
- examples/docs/actors-deprecated-queues
- examples/docs/actors-deprecated-run
- examples/docs/actors-deprecated-state
- examples/docs/actors-design-patterns
- examples/docs/actors-destroy
- examples/docs/actors-errors
- examples/docs/actors-events
- examples/docs/actors-input
- examples/docs/actors-keys
- examples/docs/actors-kv
- examples/docs/actors-lifecycle
- examples/docs/actors-limits
- examples/docs/actors-metadata
- examples/docs/actors-performance-monitoring
- examples/docs/actors-permissions
- examples/docs/actors-queues
- examples/docs/actors-quickstart-backend
- examples/docs/actors-quickstart-react
- examples/docs/actors-request-handler
- examples/docs/actors-sqlite
- examples/docs/actors-sqlite-drizzle
- examples/docs/actors-state
- examples/docs/actors-testing
- examples/docs/actors-types
- examples/docs/actors-websocket-handler
- examples/docs/clients-javascript
- examples/docs/clients-react
- examples/docs/general-actor-configuration
- examples/docs/general-cors
- examples/docs/general-http-server
- examples/docs/general-jwt
- examples/docs/general-logging
- examples/docs/general-registry-configuration
- examples/docs/general-wasm-vs-native-sdk
- examples/multiplayer-game-patterns
- examples/per-tenant-database
- examples/scheduling