zen-mcpzen-mcp/browser/.cursor/rules/00-project.mdc

browser / rules

Cursor rule2 starsChanged 7 months agoApache-2.0View on GitHub

Core browser-mcp agent instructions

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,157 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 repository8 other files it gives its agents.
- .agents/AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/10-python.mdcCursor rule
- .cursor/rules/20-mcp-tools.mdcCursor rule
- capture-evidence-bundleSkill
- guidelinesSkill
- safe-loginSkill
- scrape-with-paginationSkill

The file

We split this 00-project.mdc into the rules it gives an agent

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

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

Common
Distinctive
Very specific

Very specific:
Before code edits, apply .agents/skills/guidelines/SKILL.md.
line 8
Distinctive:
Keep edits surgical, simple, and verified.
line 9
Distinctive:
Read AGENTS.md first; it is the source of truth for agent work.
line 10
Very specific:
Follow .agents/RULES.md and .agents/REPO_RULES.md for safety and repo gotchas.
line 11
Very specific:
Keep runtime browser code async-first and headless.
line 13
Distinctive:
Do not log or return credentials, cookies, auth headers, passwords, API keys, or TOTP secrets.
line 16

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

00-project.mdc

---
description: Core browser-mcp agent instructions
alwaysApply: true
---

# browser-mcp core rules

- Before code edits, apply `.agents/skills/guidelines/SKILL.md`.
- Keep edits surgical, simple, and verified.
- Read `AGENTS.md` first; it is the source of truth for agent work.
- Follow `.agents/RULES.md` and `.agents/REPO_RULES.md` for safety and repo
  gotchas.
- Keep runtime browser code async-first and headless.
- Preserve legacy `browse_and_act` string output; use structured sibling tools
  for dict output.
- Do not log or return credentials, cookies, auth headers, passwords, API keys,
  or TOTP secrets.
- For multi-step browser workflows, check `.agents/SKILLS.md` before inventing
  a new procedure.

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