Durable Objects

A Cloudflare building block for code that needs to remember state and coordinate — think a single source of truth per thing (per user, per room, per job). Some of our connectors lean on this for their data mirror and scheduling.

Claude Code only

How to use it

Ask Claude to create or review a Durable Object and it handles the storage, alarms (timers), RPC methods, and the wrangler config + migrations, checking the live docs for the current rules. Useful when reviewing connector code that uses a per-entity store. Claude Code only: needs the project and local testing.

How to invoke / keep it on

Mention Durable Objects (or describe stateful coordination) in Claude Code and it loads. Add it to a connector project’s instructions for repeat work.

20 powerful examples for Melinda Maria

Copy, tweak, make them yours. Just describe the task — Claude loads the skill automatically.

01"Review the Durable Object that backs our shipbob order-history mirror and check it follows current best practices for storage + alarms."

02"I’m getting a concurrency-looking bug in a connector that stores per-account data — explain how Durable Object single-threading works and where my code is fighting it."

03"Show me the wrangler config + migration to add a new Durable Object class to an existing connector without breaking the live one."

04"Explain in plain English when a connector should use a Durable Object versus just D1, so I can decide for the next build."

05"Walk me through using a Durable Object alarm to run the loudcrowd nightly refresh, and how to confirm the alarm fired."

06"Help me design a per-creator Durable Object for ShopMy data so each influencer’s rollup stays consistent under heavy reads."

07"Explain the Durable Objects storage API (get/put/list/delete) with a concrete example from our order-mirror code."

08"I think two requests are stepping on each other while updating a connector’s state — show me how Durable Objects serialize access and how to verify it’s fixed."

09"Help me migrate a connector from a fragile in-memory cache to a proper Durable Object so state survives a redeploy."

10"Show me how to add an RPC method to a Durable Object so another part of the connector can ask it for the latest sync status."

11"Explain how alarms differ from cron triggers for scheduling, using our connectors as the example, and which is right when."

12"Review whether the apparelmagic mirror should be one big Durable Object or split per data type (orders, inventory, customers), with tradeoffs."

13"Walk me through deleting old keys from a Durable Object’s storage on a schedule so the mirror doesn’t grow forever."

14"Help me add a “last successful sync” timestamp in a Durable Object and surface it through the connector’s health tool."

15"Explain the cost model of Durable Objects (requests, duration, storage) in plain English so I can estimate it for a new connector."

16"I need to rename a Durable Object class safely on a live connector — show me the migration steps so I don’t lose the stored history."

17"Show me how to test Durable Object alarms locally so I’m confident the nightly job works before deploy."

18"Help me reason about whether a single global Durable Object would become a bottleneck for the edgemesh connector under spiky traffic."

19"Explain how to recover gracefully if a Durable Object alarm throws mid-refresh, so a failed ShipHero sync retries instead of silently stopping."

20"Draft a plain-English note for the team explaining what “state” means here and why a couple of our connectors need Durable Objects to stay accurate."

← Back to Cloudflare & infrastructure