agentleFS
MetaMaskMetaMask/metamask-docs/.cursor/rules/product-infura.mdc

metamask-docs / rules

Cursor rule869 starsChanged 7 days agoApache-2.0View on GitHub

Infura documentation has moved to docs.infura.io. Do not add Infura API or dashboard content to metamask-docs.

We split this product-infura.mdc into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When MetaMask product docs need to reference Infura:

    line 13
  2. Very specific:

    Use absolute links to https://docs.infura.io/ (for example, https://docs.infura.io/dashboard/get-started/create-api/).

    line 15
  3. Very specific:

    Do not recreate Infura content under services/ or developer-tools/dashboard/ in this repository.

    line 16
  4. Distinctive:

    Do not link to the MetaMask or Infura faucet products.

    line 17

≈ “Common” is an estimate: at least 1 in 5 of the 6,350 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
product-infura.mdc
---
description: Infura documentation has moved to docs.infura.io. Do not add Infura API or dashboard content to metamask-docs.
alwaysApply: true
---

# Infura documentation

Infura API reference, guides, and dashboard documentation are published at [docs.infura.io](https://docs.infura.io/).

- **Repository:** [INFURA/docs.infura](https://github.com/INFURA/docs.infura)
- **Dashboard:** [app.infura.io](https://app.infura.io/)

When MetaMask product docs need to reference Infura:

- Use absolute links to `https://docs.infura.io/` (for example, `https://docs.infura.io/dashboard/get-started/create-api/`).
- Do not recreate Infura content under `services/` or `developer-tools/dashboard/` in this repository.
- Do not link to the MetaMask or Infura faucet products; both are deprecated. For testnet ETH, use a
  generic note (for example, “use a public Sepolia faucet”) with no specific faucet URL.

Cross-domain redirects in `vercel.json` send legacy `/services/*`, `/developer-tools/dashboard/*`,
and `/developer-tools/faucet/` URLs to Infura. List specific rules before the catch-all fallbacks;
map renamed paths (for example `/services/gas-api/` → `https://docs.infura.io/reference/gas-api/`).
The deprecated faucet path `/developer-tools/faucet/` redirects to `https://docs.infura.io/dashboard/`.

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.