live-cursors

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

npx skills add https://github.com/rivet-dev/skills --skill live-cursors

More skills from rivet-dev

multiplayer-game
rivet-dev
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...
rivetkit
rivet-dev
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...
ai-agent
rivet-dev
Build an AI agent backend with persistent memory: one Rivet Actor per conversation, queued message handling, and streaming LLM responses as realtime events.
ai-agent-workspace
rivet-dev
Give every AI agent its own computer: a persistent workspace with a filesystem, processes, shells, networking, and agent sessions on a lightweight in-process…
chat-room
rivet-dev
Build a realtime chat room backend with Rivet Actors: one actor per room, SQLite-backed message history, and WebSocket broadcast to every connected client.
collaborative-text-editor
rivet-dev
Build a collaborative text editor backend with Yjs CRDTs and Rivet Actors: per-document actors relay sync and awareness updates and persist snapshots.
cron-jobs
rivet-dev
Durable cron jobs with Rivet Actors: schedule.after and schedule.at timers survive restarts and crashes, plus re-arming recurring jobs and idempotent handlers.
per-tenant-database
rivet-dev
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.