blitzhash360-webblitzhash360-web/blitzhash-cloudflare-production-skills/.cursor/rules/cloudflare-safety.mdc

blitzhash-cloudflare-production-skills / rules

Cursor rule0 starsChanged 9 days agoMITView on GitHub

Safety rules for any Cloudflare change made by the agent (tokens, dry run, confirmation)

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,183 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-turnstile.mdcCursor rule
- .cursor/rules/cloudflare-waf-rules.mdcCursor rule
- .cursor/rules/cloudflare-zone-audit.mdcCursor rule
- .cursor/rules/cloudflare-zones-overview.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-safety.mdc into the rules it gives an agent

5 rules. About 0 are common, 0 are distinctive, and 5 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Read the Cloudflare API token only from CLOUDFLARE_API_TOKEN (env or git-ignored .env).
line 7
Very specific:
Use the scripts in this repo (node bin/cf-skills.mjs ...) instead of hand-written curl calls, so every change is planned and logged.
line 8
Very specific:
Every write runs as a dry run first.
line 9
Very specific:
Never delete DNS records or rules the user did not name.
line 10
Very specific:
Run node bin/cf-skills.mjs audit before and after changes and report the score change.
line 11

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

cloudflare-safety.mdc

---
description: Safety rules for any Cloudflare change made by the agent (tokens, dry run, confirmation)
alwaysApply: true
---
# Cloudflare change safety

- Read the Cloudflare API token only from `CLOUDFLARE_API_TOKEN` (env or git-ignored .env). Never ask for it in chat, print it, pass it as a flag, or commit it.
- Use the scripts in this repo (`node bin/cf-skills.mjs ...`) instead of hand-written curl calls, so every change is planned and logged.
- Every write runs as a dry run first. Show the plan, wait for the user's explicit "yes", then re-run the same command with `--apply --yes`.
- Never delete DNS records or rules the user did not name. Never request a token with more permissions than docs/TOKEN-PERMISSIONS.md lists.
- Run `node bin/cf-skills.mjs audit` before and after changes and report the score change.

Download now (ZIP)

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

What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free