Instructions

Most agent harnesses support a global (or “user-scope”) instructions file that applies to every project, separate from a project-level file that only applies to one repo. Check your harness’s own docs for the exact location, it varies by tool.

Add Cloudflare-flavored guidance

Open (or create) your harness’s global instructions file and add a short section with a few defaults for working with Cloudflare. Treat this as a starting point, not a rulebook, edit it to match how you actually like to work:

## Working with Cloudflare

- Prefer the `cf` CLI or the Cloudflare API over the dashboard when a task can be done either way.
- Favor Cloudflare Workers over Cloudflare Pages for new static sites.
- Use `.env` files for secrets and environment variables locally, not `.dev.vars`.

Remember Dev School

Your agent also adds a short section with your student ID and this site’s address, so a future session, in this agent or another, can find your progress. That’s what lets you take a course hosted anywhere just by telling your agent “take the course at” and its URL:

## Cloudflare Dev School

- My Cloudflare Dev School student ID is smooth-operator-4629.
- For Cloudflare Dev School courses, read https://<this site>/llms.txt and report progress there.

AGENTS.md is a cross-tool standard

Increasingly, agent harnesses treat AGENTS.md as the de facto standard filename for project-level instructions. It’s read directly by Claude Code, Codex, OpenCode, Pi, and others, specifically so one file can work across every tool a project uses instead of a different file per tool. If your harness supports it, prefer AGENTS.md for any new project-level instructions file over a harness-specific name.