386 件 ・ 関連度順
概要と使いどころ
Cloudflare Workers is an edge computing platform for running JavaScript, TypeScript, and WebAssembly close to users worldwide with sub-millisecond cold starts. Use when working with the Workers runtime, the Wrangler CLI, KV, D1, R2, Durable Objects, Queues, or Hyperdrive, or when a user asks to build and deploy an edge function.
日本語の概要は準備中です。原文の説明を表示しています。
Protect and accelerate websites with Cloudflare. Use when a user asks to add CDN, DDoS protection, DNS management, SSL, WAF, or edge computing to a website or API.
日本語の概要は準備中です。原文の説明を表示しています。
Provides domain knowledge and guidance for the Flare Data Connector (FDC)—attestation types, request flow, Merkle proofs, verifier/DA Layer, and smart contract integration. Use when working with FDC, cross-chain attestations, EVMTransaction, Web2Json, Payment, AddressValidity, proof-of-reserves, weather insurance, or Flare Developer Hub FDC guides and starter repos.
日本語の概要は準備中です。原文の説明を表示しています。
Deploy containerized applications to AWS EC2 and expose them publicly via Cloudflare Tunnel with automatic HTTPS. Eliminates need for load balancers, SSL certificates, or public inbound ports.
日本語の概要は準備中です。原文の説明を表示しています。
Deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services. Use when the user asks to deploy, host, publish, or set up a project on Cloudflare.
日本語の概要は準備中です。原文の説明を表示しています。
Deploy serverless applications on Cloudflare Workers. Covers project setup, JavaScript handler patterns, routing, deployment with Wrangler, and API token configuration. Suitable for APIs, proxies, edge computing, and request transformation.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive Cloudflare platform skill covering Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), networking (Tunnel, Spectrum), security (WAF, DDoS), and infrastructure-as-code (Terraform, Pulumi). Use for any Cloudflare development task.
日本語の概要は準備中です。原文の説明を表示しています。
Deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services. Use when the user asks to deploy, host, publish, or set up a project on Cloudflare.
日本語の概要は準備中です。原文の説明を表示しています。
Cloudflare Workers edge computing — Durable Objects, KV, R2, D1, Workers AI, AI Gateway
日本語の概要は準備中です。原文の説明を表示しています。
Cloudflare Pages and Workers deployment checklist for wrangler deploys, secret audits, D1 migrations, Worker-compatible SDK checks, and browser-auth verification. Use when shipping Cloudflare changes to production. NOT for general CI/CD architecture, non-Cloudflare deployments, or post-launch UX QA.
日本語の概要は準備中です。原文の説明を表示しています。
Use when wrangler deploys silently fail or produce wrong artifacts, secrets upload as empty strings, custom domain DNS is not resolving, route assignment broke after rename, observability/tail logs are needed, D1/KV/R2 bindings are missing, OAuth scope errors block a command, cookies on a redirect are not attaching, or the worker exceeds CPU time. Triggers: "Tenant or user not found", "Authentication error" on wrangler d1 push, secret length is 0 after upload, route returns origin not worker, "compatibility_date too old", 1101 errors, custom_domain assignment lost on script rename. NOT for AWS Lambda / Vercel Edge / Deno Deploy (different runtimes), Cloudflare Zero Trust, or R2-specific tuning.
日本語の概要は準備中です。原文の説明を表示しています。
Implante aplicações e infraestrutura na Cloudflare usando Workers, Pages e serviços relacionados da plataforma. Use quando o usuário pedir para implantar, hospedar, publicar ou configurar um projeto na Cloudflare.
日本語の概要は準備中です。原文の説明を表示しています。
Cloudflare Email Service（Email Sending + Email Routing）でトランザクションメールの送受信を実装するスキル。Workers bindingまたはREST APIによるメール送信、Email Routing、Agents SDKのemail handler、Workers・Node.js・Python・Go等への組み込みで使う。到達性、SPF/DKIM/DMARC、wrangler email設定、MCP email tools、coding agentからのメール送信も対象。「Workerにメール機能を追加」のような依頼でも、重要な設定要件があるため必ず使用する。
Manage Cloudflare DNS zones, Workers, Pages, R2, KV, D1, and analytics via REST API. Use when the user wants to query DNS, deploy a Worker, list R2 buckets, manage KV namespaces, run D1 queries, or check analytics without the Cloudflare MCP installed.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Cloudflare Workers Deep — deep analysis of Cloudflare Workers deployments including script inventory, route mappings, KV namespace usage, Durable Objects, cron triggers, CPU time metrics, and error rate tracking. Use for comprehensive Workers platform health checks and optimization.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Cloudflare Dns Deep — advanced Cloudflare DNS management covering zone records, DNSSEC configuration, DNS analytics, load balancing pools, health checks, and DNS firewall. Use for deep DNS record management, DNSSEC troubleshooting, DNS traffic analytics, configuring DNS-based load balancing, or auditing DNS security settings.
日本語の概要は準備中です。原文の説明を表示しています。
Cloudflare GraphQL Analytics for zone traffic, firewall events, Workers metrics, and schema exploration. Use when querying Cloudflare analytics data or exploring the GraphQL API.
日本語の概要は準備中です。原文の説明を表示しています。
Expert en Cloudflare avancé (Workers, Pages, R2, D1, Durable Objects, KV, WAF)
日本語の概要は準備中です。原文の説明を表示しています。
Deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services. Use when the user asks to deploy, host, publish, or set up a project on Cloudflare.
日本語の概要は準備中です。原文の説明を表示しています。
Cloudflareでの新規アプリ設計や大規模移行に先立ち、構成の選定理由と制約を短い設計メモにまとめる。通常のコード修正には使わない。
Manage Cloudflare DNS records, Tunnels (cloudflared), and Zero Trust policies. Use for pointing domains, exposing local services via tunnels, and updating ingress rules.
日本語の概要は準備中です。原文の説明を表示しています。
Cloudflare Pages and Workers deployment checklist for wrangler deploys, secret audits, D1 migrations, Worker-compatible SDK checks, and browser-auth verification. Use when shipping Cloudflare changes to production. NOT for general CI/CD architecture, non-Cloudflare deployments, or post-launch UX QA.
日本語の概要は準備中です。原文の説明を表示しています。
Architecture-level decisions for putting a CDN in front of a web app's static assets, API responses, and file/media delivery: provider selection (hyperscaler vs. specialist $/GB), signed-URL / tokenized access for gating private content at the edge, cache invalidation strategy (versioned URLs vs. purge APIs), origin shield / tiered caching for high-miss-rate content, and CDN-layer geo-restriction. Use when deciding which CDN to put in front of a new or growing service, when private/paywalled files need edge delivery without an origin round-trip per request, or when purge/invalidation behavior is being designed rather than debugged. NOT for HTTP cache-control header syntax, Vary, stale-while-revalidate, or surrogate-key purge mechanics (see `cdn-cache-control-headers`); NOT for Cloudflare-specific product configuration once Cloudflare is already chosen (see `cloudflare`); NOT for video-specific transcoding, adaptive bitrate ladders, or streaming-protocol packaging (see `managed-video-streaming-pipeline`).
日本語の概要は準備中です。原文の説明を表示しています。
Use when wrangler deploys silently fail or produce wrong artifacts, secrets upload as empty strings, custom domain DNS is not resolving, route assignment broke after rename, observability/tail logs are needed, D1/KV/R2 bindings are missing, OAuth scope errors block a command, cookies on a redirect are not attaching, or the worker exceeds CPU time. Triggers: "Tenant or user not found", "Authentication error" on wrangler d1 push, secret length is 0 after upload, route returns origin not worker, "compatibility_date too old", 1101 errors, custom_domain assignment lost on script rename. NOT for AWS Lambda / Vercel Edge / Deno Deploy (different runtimes), Cloudflare Zero Trust, or R2-specific tuning.
日本語の概要は準備中です。原文の説明を表示しています。