Cloudflare Do Turn Based Multiplayer

Design, implement, debug, or verify a remote turn-based multiplayer game whose rooms run on Cloudflare Durable Objects. Use for room and invite identity, reconnectable seats, WebSocket hibernation, concurrent turns, action idempotency, revision conflicts, or cross-browser game-state agreement. Do not trigger for generic Durable Object applications or local-only games.

201 stars 12 forksDevOps & Cloud

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add swyxio/skills --skill cloudflare-do-turn-based-multiplayer
Manual install
git clone --depth 1 https://github.com/swyxio/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/cloudflare-do-turn-based-multiplayer ~/.claude/skills/cloudflare-do-turn-based-multiplayer

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Cloudflare DO Turn-Based Multiplayer

Model each room as one server-authoritative state machine. Keep the deterministic
game reducer independent from Cloudflare transport so rules and concurrency can
be tested without Wrangler.

## Establish authority

Before editing, identify:

- the room's deterministic Durable Object ID;
- the public room code and any private invite credential;
- how a device resumes and which seats it owns;
- the persisted room revision and action identity; and
- how clients recover after an unknown result.

The URL room code is the room selector, not authentication. Store resume
credentials per room, exchange private invites for device credentials, and
remove invite secrets from the visible URL after exchange. Re-authorize the
device against current room state on every mutation.

Read [protocol-and-architecture.md](references/protocol-and-architecture.md)
when changing URLs, identity, message schemas, persistence, or recovery.

## Serialize mutations

Durable Objects serialize events, but handlers can interleave at external
`await` boundaries. For every authoritative action:

1. enter one room mutation gate;
2. re-read state and re-authorize the device inside it;
3. check immutable `actionId` duplication before checking `expectedRevision`;
4. validate the fresh revision and deterministic game rule;
5. persist the accepted state before acknowledgement or broadcast; and
6. return the canonical snapshot for acceptance, duplication, or rejection.
Read the full skill on GitHub

Details

Skill name
cloudflare-do-turn-based-multiplayer
Repository
swyxio/skills
Path
cloudflare-do-turn-based-multiplayer/SKILL.md
License
MIT
Repo updated
16 November 2026

FAQ

What does the Cloudflare Do Turn Based Multiplayer skill do?

Design, implement, debug, or verify a remote turn-based multiplayer game whose rooms run on Cloudflare Durable Objects. Use for room and invite identity, reconnectable seats, WebSocket hibernation, concurrent turns, action idempotency, revision conflicts, or cross-browser game-state agreement. Do not trigger for generic Durable Object applications or local-only games.

How do I install the Cloudflare Do Turn Based Multiplayer skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add swyxio/skills --skill cloudflare-do-turn-based-multiplayer. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Cloudflare Do Turn Based Multiplayer popular?

It lives in swyxio/skills, which has 201 GitHub stars and 12 forks.

Related skills

Accelevents API

201

swyxio/skills

Use when reading or updating AI Engineer Europe speaker records through the Accelevents REST API, especially for full-record PUT updates, auth header quirks, and preserving existing speaker fields.

Software Development12

Accelevents Speaker Sync

201

swyxio/skills

Use when website speaker, session, schedule, room, track, or headshot changes must be synchronized back to Accelevents for AI Engineer Europe 2026.

AI, LLMs & Agents12

Agents SDK

201

swyxio/skills

Build or debug stateful applications that specifically use Cloudflare's `agents` package, including Agent classes, routing, callable methods, synchronized state, scheduling, AIChatAgent, durable execution, or Agents SDK client hooks. Do not trigger for generic AI-agent design, the OpenAI Agents SDK, or ordinary Durable Object work that does not use the Cloudflare Agents SDK.

AI, LLMs & Agents12

Cloudflare Email Service

201

swyxio/skills

Implement or debug Cloudflare Email Service sending, Email Routing, or an Agents SDK email handler. Use for the Workers email binding, Email Service REST API, SMTP, inbound `email()` handlers, domain onboarding, deliverability, or Cloudflare email tooling. Do not trigger for provider-neutral email design or non-Cloudflare mail services.

DevOps & Cloud12

Cloudflare

201

swyxio/skills

Route an ambiguous or cross-product Cloudflare platform request to the appropriate product, documentation, or narrower local skill. Use when the user needs help choosing among Cloudflare compute, storage, AI, networking, security, media, or infrastructure products. Do not trigger when the request already names a specific Cloudflare product or matches a narrower installed skill.

DevOps & Cloud12

Cloudflare One

201

swyxio/skills

Guides Cloudflare One Zero Trust and SASE work across Access, Gateway, WARP, Tunnel, Cloudflare WAN, DLP, CASB, device posture, and identity. Use when designing, configuring, troubleshooting, or reviewing Cloudflare One deployments. Retrieval-first: use current Cloudflare docs/API schemas instead of embedded product docs.

DevOps & Cloud12

Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.