AGENTIC MEMORY

Skills

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

← Back to Skills

cloudflare-deploy

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.

Original source
openai
License
Apache-2.0
Pinned revision
49f948faa9258a0c61caceaf225e179651397431

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

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read openai--cloudflare-deploy at revision 49f948faa9258a0c61caceaf225e179651397431, 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 · 309

references/pages-functions/README.md

Cloudflare Pages Functions

Serverless functions on Cloudflare Pages using Workers runtime. Full-stack dev with file-based routing.

Quick Navigation

Need to... | Task | Go to | |------|-------| | Set up TypeScript types | configuration.md - TypeScript Setup | | Configure bindings (KV, D1, R2) | configuration.md - wrangler.jsonc | | Access request/env/params | api.md - EventContext | | Add middleware or auth | patterns.md - Middleware, Auth | | Background tasks (waitUntil) | patterns.md - Background Tasks | | Debug errors or check limits | gotchas.md - Common Errors, Limits |

Decision Tree: Is This Pages Functions?

Need serverless backend? 
├─ Yes, for a static site → Pages Functions
├─ Yes, standalone API → Workers
└─ Just static hosting → Pages (no functions)

Have existing Worker?
├─ Complex routing logic → Use _worker.js (Advanced Mode)
└─ Simple routes → Migrate to /functions (File-Based)

Framework-based?
├─ Next.js/SvelteKit/Remix → Uses _worker.js automatically
└─ Vanilla/HTML/React SPA → Use /functions

File-Based Routing

/functions
  ├── index.js              → /
  ├── api.js                → /api
  ├── users/
  │   ├── index.js          → /users/
  │   ├── [user].js         → /users/:user
  │   └── [[catchall]].js   → /users/*
  └── _middleware.js        → runs on all routes

Rules:

  • index.js → directory root
  • Trailing slash optional
  • Specific routes precede catch-alls
  • Falls back to static if no match

Dynamic Routes

Single segment [param] → string:

// /functions/users/[user].js
export function onRequest(context) {
  return new Response(`Hello ${context.params.user}`);
}
// Matches: /users/nevi

Multi-segment [[param]] → array:

// /functions/users/[[catchall]].js
export function onRequest(context) {
  return new Response(JSON.stringify(context.params.catchall));
}
// Matches: /users/nevi/foobar → ["nevi", "foobar"]

Key Features

  • Method handlers: onRequestGet, onRequestPost, etc.
  • Middleware: _middleware.js for cross-cutting concerns
  • Bindings: KV, D1, R2, Durable Objects, Workers AI, Service bindings
  • TypeScript: Full type support via wrangler types command
  • Advanced mode: Use _worker.js for custom routing logic

Reading Order

New to Pages Functions? Start here:

  1. README.md - Overview, routing, decision tree (you are here)
  2. configuration.md - TypeScript setup, wrangler.jsonc, bindings
  3. api.md - EventContext, handlers, bindings reference
  4. patterns.md - Middleware, auth, CORS, rate limiting, caching
  5. gotchas.md - Common errors, debugging, limits

Quick reference lookup:

See Also

  • pages - Pages platform overview and static site deployment
  • workers - Workers runtime API reference
  • d1 - D1 database integration with Pages Functions