blitzhash360-webblitzhash360-web/blitzhash-cloudflare-production-skills/.cursor/rules/cloudflare-zones-overview.mdcblitzhash-cloudflare-production-skills / rules
Cursor rule0 starsChanged 10 days agoMITView on GitHub
Show which domains (zones) a Cloudflare account has, their status, plan, nameservers and DNS record summary, read-only. Use when the user asks what domains they have on Cloudflare, whether a domain is active, or which nameservers to set at the registrar.
- Reads credentials
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,181 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/cloudflare-dns-records.mdcCursor rule
- .cursor/rules/cloudflare-rate-limiting.mdcCursor rule
- .cursor/rules/cloudflare-safety.mdcCursor rule
- .cursor/rules/cloudflare-turnstile.mdcCursor rule
- .cursor/rules/cloudflare-waf-rules.mdcCursor rule
- .cursor/rules/cloudflare-zone-audit.mdcCursor rule
- cloudflare-dns-recordsSkill
- cloudflare-rate-limitingSkill
- cloudflare-turnstileSkill
- cloudflare-waf-rulesSkill
- cloudflare-zone-auditSkill
- cloudflare-zones-overviewSkill
The file
We split this cloudflare-zones-overview.mdc into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Run commands with npx -y github:blitzhash360-web/blitzhash-cloudflare-production-skills <command> or, inside a clone of the repo, node …
- Very specific: line 27
Every write command is a dry run by default.
- Very specific: line 28
Only after that "yes", re-run the same command with --apply --yes (your shell is not interactive).
- Distinctive: line 29
Never delete records or rules the user did not name.
- Very specific: line 30
Run cf-skills audit before and after changes and tell the user what moved.
≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
--- description: Show which domains (zones) a Cloudflare account has, their status, plan, nameservers and DNS record summary, read-only. Use when the user asks what domains they have on Cloudflare, whether a domain is active, or which nameservers to set at the registrar. alwaysApply: false --- <!-- Generated from skills/cloudflare-zones-overview/SKILL.md by scripts/build-cursor-rules.mjs. Edit the skill, not this file. --> # Cloudflare domains and zones overview Run commands with `npx -y github:blitzhash360-web/blitzhash-cloudflare-production-skills <command>` or, inside a clone of the repo, `node bin/cf-skills.mjs <command>`. Below, `cf-skills` means either. Zone is `--zone <domain or zone id>` or `$CLOUDFLARE_ZONE_ID`. ## Commands - All zones: `cf-skills zones list` - One zone: `cf-skills zones show --zone example.com` (status, plan, nameservers, record counts) - Token check: `cf-skills verify-token` ## Guidance - A zone that is not `active` is not protecting the site yet; the user must set the two nameservers shown at their registrar. - `paused` means Cloudflare is passing traffic straight to the origin with no protection. - Registering, transferring or deleting domains is out of scope for these scripts; send the user to the dashboard for that. - Token: Zone Read (+ DNS Read for record counts). ## Safety rules (always) - The API token lives only in the environment (`CLOUDFLARE_API_TOKEN`) or a git-ignored `.env`. Never ask the user to paste it into chat, never print it, never pass it as a flag, never commit it. - Every write command is a **dry run** by default. Run it without `--apply` first, show the user the printed plan, and wait for an explicit "yes" in chat. - Only after that "yes", re-run the **same** command with `--apply --yes` (your shell is not interactive). Never add `--yes` on your own initiative. - Never delete records or rules the user did not name. Never widen the token's permissions. - Run `cf-skills audit` before and after changes and tell the user what moved.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.