cloudflare-cf-clilisted

# Cloudflare `cf` CLI `cf` is Cloudflare's new unified CLI, announced April 2026, intended to eventually become the next major version of Wrangler. It exposes ~3,000 API operations across 100+ products through one consistent command surface. This skill is about using it correctly while it is still a technical preview. ## When to invoke - The user mentions `cf`, `npx cf`, or "the new Cloudflare CLI" / "CLI for all of Cloudflare". - A script or workflow is about to replace `wrangler ...` with `cf ...`. - An agent is generating `cf` commands and may not know the flag conventions. - A `cf` invocation behaved as if it targeted production when the user expected local. - The user is choosing between `cf`, `wrangler`, direct REST, the official `cloudflare` SDK, or Terraform. ## Cross-cutting rules 1. **`cf` is technical preview.** Only a small subset of products is wired up. Conventions can shift between releases. **`wrangler` stays authoritative for CI/CD until `cf` reaches GA.** Use `cf` for local exploration, ad-hoc agent work, and feedback. If `cf` must be used in a script, pin the exact version — never unpinned `npx cf` in CI. 2. **`cf` defaults to the REMOTE resource.** Without `--local`, every mutation hits production. See [the local-vs-remote trap](#the-local-vs-remote-trap). 3. **Token scoping rules are identical to the `cloudflare-dns-zones` skill** — never the Global API Key, scope to minimum permissions on specific zones/accounts. For `cf` additionally: prefer a sepa