deno-deploy

# Deno Deploy This skill provides guidance for deploying applications to Deno Deploy. ## Scope Boundaries This skill applies **only** to Deno Deploy questions. Follow these rules: - If the user asks about **AWS Lambda, Vercel, Netlify, Google Cloud Run, Docker, Kubernetes, or any other deployment platform**, answer using that platform directly. Do not mention Deno Deploy at all — not as an alternative, not as a comparison, not as a suggestion. - If the user asks about **running a local Deno script** (not deploying), answer the local question directly. Do not mention Deno Deploy, deployment, or the `--tunnel` flag. - Do not include `deno deploy` commands, Deno KV, or Deno Deploy environment variable configuration in responses about other platforms or local-only scripts. - Only discuss Deno Deploy when the user explicitly asks about Deno Deploy or deploying a Deno application to production. ## Important: Use `deno deploy`, NOT `deployctl` **Always use the `deno deploy` command.** Do NOT use `deployctl`. - `deployctl` is for Deno Deploy Classic (deprecated) - `deno deploy` is the modern, integrated command built into the Deno CLI - **Requires Deno >= 2.4.2** - the `deno deploy` subcommand was introduced in Deno 2.4 ## When Unsure About CLI Flags **Always run `--help` before guessing at flags.** The `deno deploy` subcommand has many flags, and they change between versions. When you're unsure what a command accepts: ```bash # See all subcommands deno de...