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/static-assets/configuration.md

Static Assets Configuration

Inspect the build script, output directory, Wrangler configuration, and any framework-generated deployment configuration first. Configure the files actually produced by the build, and identify which paths need Worker logic.

| Task | Documentation | |------|---------------| | Set the asset directory and exclude non-public files | Directory and ignoring assets | | Make assets available to Worker code | Asset binding configuration | | Select paths that must run Worker logic before asset serving | Worker-first configuration | | Configure SPA fallback and navigation behavior | SPA configuration | | Configure generated HTML and missing-page responses | SSG configuration | | Choose canonical HTML URLs and trailing slash handling | HTML handling modes | | Configure assets produced by the Cloudflare Vite plugin | Vite asset configuration | | Configure static response headers or redirects | Headers and redirects |

For Vite projects, inspect generated output before overriding asset paths. For protected routes, ensure that the selected routing configuration reaches the authorization logic before returning an asset. Use patterns.md to decide routing intent and gotchas.md to verify it.