agentleFS
arthurcuriarthurcuri/mcp-instructure-canvas/.cursor/rules/repository.mdc

mcp-instructure-canvas / rules

Cursor rule2 starsChanged 34 days agoMITView on GitHub

Canvas MCP architecture, validation and local data handling

  • 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,243 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 repository4 other files it gives its agents.

The file

We split this repository.mdc into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the root @AGENTS.md as the shared repository instructions.

    line 6
  2. Very specific:

    Keep Canvas read/write tools separate and respect CANVAS_READ_ONLY.

    line 9

≈ “Common” is an estimate: at least 1 in 5 of the 6,809 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
repository.mdc
---
description: Canvas MCP architecture, validation and local data handling
alwaysApply: true
---

Use the root @AGENTS.md as the shared repository instructions. Cursor can also
discover that file directly. Read it before changing server or automation code.

Keep Canvas read/write tools separate and respect `CANVAS_READ_ONLY`. Mock HTTP
in tests; do not open `.env` while exploring the source. Put reports and logs in
`.local/`. Keep MCP configurations specific
to a contributor's computer out of commits. Use the root README's setup steps.

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.