cloudflare-production-builder
Design, review, debug, migrate, or deploy production systems on Cloudflare Workers and related Developer Platform products. Use for material architecture, durability, release, migration, rollback, or live-verification decisions across Workers, Durable Objects, D1, R2, Queues, Workflows, bindings, and routes.
swyxio · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add swyxio/skills --skill cloudflare-production-builder技能说明
name: cloudflare-production-builder description: Design, review, debug, migrate, or deploy production systems on Cloudflare Workers and related Developer Platform products. Use for material architecture, durability, release, migration, rollback, or live-verification decisions across Workers, Durable Objects, D1, R2, Queues, Workflows, bindings, and routes.
Cloudflare Production Builder
Apply this guidance proportionally. It is a production reasoning aid, not a mandatory ceremony layer. Stay within the user's requested operation and do not turn a diagnosis or recovery into an architecture program.
Choose the operating mode
- Answer or diagnose: inspect only the evidence needed to explain the behavior. Do not mutate or design a replacement unless asked.
- Recover: restore a known-good capability with the smallest supported, reversible operation. Preserve evidence and defer refactoring.
- Change or migrate: design compatibility, durability, rollout, verification, and rollback for the surfaces actually affected.
Do not mix recovery and refactoring in one production operation.
Core contract
- Identify authoritative state, the coordination key, the durability boundary, and user-visible completion.
- Treat source, build, upload, configuration, migration, traffic, route, stateful lifecycle, and live behavior as separate facts only when the task depends on those surfaces.
- Prefer immutable artifacts and conditional pointer changes. Make external mutations idempotent, fenced, conditional, or compensatable.
- Classify errors before retrying. Persist terminal domain failures; bound transient retries; read authoritative provider state after an ambiguous mutation before replay. Do not turn artifact verification into a resumable controller unless the product operation itself requires durable execution.
- Preserve accepted work across handoff failures. Use a durable record and a repair path when an initiating request can disappear.
- Verify the owning live path and exact identity after a production mutation.
Use precise language such as
version uploaded,traffic switched, andlive smoke passed.
For SHA-derived, write-once release artifacts, reconcile means bounded
provider readback and a fail-closed decision. Adopt an existing artifact only
when every immutable property matches. Never repair a mismatch in place, add a
durable current-artifact pointer, or create another publication authority merely
to make image, host, application, namespace, or version creation retryable.
Traffic publication and rollback should switch one recorded immutable pointer
when the topology supports it; build-time artifact preparation stays outside
that publication path.
Prefer provider-native hot paths
For a measured Cloudflare bottleneck, identify the existing binding, bulk API,
or authenticated REST operation before starting Wrangler or making a network
round trip per item. Consider R2 bindings or direct REST uploads with an
existing scoped token, D1 batch() or set-based SQL, KV bulk writes, Queue
sendBatch(), direct Workers version/deployment readbacks, content-addressed
asset reuse, and coalesced Durable Object writes when semantics permit.
Keep concurrency and transient retries bounded; preserve credential scope, provider limits, metadata, immutable verification, publication ordering, and rollback. Do not introduce S3 credentials, broader permissions, or a new service merely to optimize transport. Keep Wrangler for infrequent complex deployment mutations unless a supported API preserves every safety invariant; verify provider response schemas with a real canary.
Proportional workflow
- Inspect current code and provisioned state for the touched surface. Resolve the exact account, environment, resource, bindings, and live version before mutation.
- State the intended authority and repair/rollback path. For simple work, one sentence is enough.
- Run focused local or remote checks that can falsify the change. Do not add unrelated global gates.
- When authorized to deploy, upload and inspect before switching when the provider supports it. Use a verification path supported by the topology.
- After mutation, verify only the affected rollout axes plus the user-visible capability. Record exact identities and rollback evidence.
When a cutover temporarily retains an old Worker, Durable Object namespace, or container application as the exact rollback target, leave it byte-for-byte and configuration-for-configuration unchanged through the rollback-compatibility window. Retention is temporary compatibility, not permanent dual-running. Remove the old artifact only in a separate bounded cleanup after live and rollback compatibility have been proven; do not hide that deletion inside the cutover or ordinary artifact garbage collection.
Pause when the exact production target, current state, retry safety, or rollback target cannot be resolved. A blocker in an unrelated surface is not permission to broaden the operation.
Integrate preview and newly launched capabilities safely
When a preview or newly launched Cloudflare capability materially improves the design, use it deliberately rather than trusting remembered APIs:
- Retrieve current first-party docs and changelog entries at action time. Note the capability's maturity, launch date, documented limits, and production support status.
- Inspect the installed package's
package.json, README/examples, exports, and.d.tsfiles. Installed types are the compilation contract; marketing docs are not. - Put the preview surface behind a narrow adapter so churn does not spread through domain code. Keep a supported fallback or an explicit failure mode when the capability is not production-suitable.
- Pin the exact package version during the proving release. Compile and build immediately after wiring each preview primitive; do not defer integrati