AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

cloudflare

Discover and choose Cloudflare products for apps, APIs, AI agents, storage, networking, and security. Use for architecture and product selection, including when the user describes a need without naming a Cloudflare product; then find the relevant skill or documentation.

Original source
cloudflare
License
Apache-2.0
Pinned revision
e44f580f9c4fa3bf268e284ae7706c7954ba31fd

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read cloudflare--cloudflare at revision e44f580f9c4fa3bf268e284ae7706c7954ba31fd, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 135

references/bindings/patterns.md

Binding Patterns

Choose the interaction and lifecycle first, then retrieve the implementation guide.

| Task | Current documentation | | --- | --- | | Choose HTTP forwarding or RPC between Workers | Service bindings | | Forward Requests and Responses through a service binding | Service bindings over HTTP | | Expose callable methods with WorkerEntrypoint | Service bindings over RPC and RPC TypeScript | | Run connected Workers during development | Developing with multiple Workers | | Test handlers against configured bindings and mock dependencies | Workers Vitest configuration and test APIs | | Select KV, D1, R2, or Durable Objects | Storage options | | Keep clients current when bindings change | Binding lifecycle | | Manage credentials used by external API clients | Secrets |

Use service bindings for internal Worker calls when appropriate, and choose HTTP or RPC based on the interface being exposed. A service binding does not replace application-level authorization for the caller's requested operation.

Choose storage based on access patterns and consistency requirements, not copied size or latency thresholds. Parallelize independent binding operations when useful; preserve ordering where one operation depends on another's result.

Avoid retaining clients derived from mutable bindings across requests without accounting for binding updates. Importing env is supported, but binding I/O still requires an appropriate execution context; follow the lifecycle guide rather than assuming all global access is forbidden.