agentleFS
Sign inStart free
sandraschisandraschi/onenote-mcp/.cursor/rules/general.md

onenote-mcp / rules

Cursor rule1 starsChanged 50 days agoMITView on GitHub

BEFORE making any changes, ALWAYS check: - Central Docs: D:\Dev\repos\mcp-central-docs\ - Standards: mcp-central-docs/STANDARDS.md - FastMCP Guide: mcp-central-docs/FASTMCP_2.13_MIGRATION.md When switching to work on this repo in a multi-workspace setup: 1. Start a fresh shell (don't reuse terminals from other repos) 2. Always cd D:\Dev\repos\onenote-mcp as the first command 3. Verify Get-Location shows correct directory before running other commands NEVER use Linux syntax: - ❌ &&, ||, ls, cat, grep, rm -rf - ✅ Use PowerShell: Get-ChildItem, Get-Content, Select-String, Remove-Item -Recurse -Force

  • Deletes or force-pushes
  • 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 repository6 other files it gives its agents.

The file

We split this general.md 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
  1. Distinctive:

    When switching to work on this repo in a multi-workspace setup:

    line 12
  2. Distinctive:

    Start a fresh shell (don't reuse terminals from other repos)

    line 13
  3. Very specific:

    Always cd D:\Dev\repos\onenote-mcp as the first command

    line 14
  4. Very specific:

    Verify Get-Location shows correct directory before running other commands

    line 15
  5. Very specific:

    NEVER: use description= parameter in @mcp.tool()

    line 25
  6. Distinctive:

    ALWAYS: use comprehensive docstrings (50+ lines minimum)

    line 26

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

OneNote MCP - General Rules

Rule #1: Check Central Documentation First

BEFORE making any changes, ALWAYS check:

  • Central Docs: D:\Dev\repos\mcp-central-docs\
  • Standards: mcp-central-docs/STANDARDS.md
  • FastMCP Guide: mcp-central-docs/FASTMCP_2.13_MIGRATION.md

Rule #2: Shell Context for Multi-Workspace

When switching to work on this repo in a multi-workspace setup:

  1. Start a fresh shell (don't reuse terminals from other repos)
  2. Always cd D:\Dev\repos\onenote-mcp as the first command
  3. Verify Get-Location shows correct directory before running other commands

Rule #3: PowerShell Only (Windows)

NEVER use Linux syntax:

  • ❌ &&, ||, ls, cat, grep, rm -rf
  • ✅ Use PowerShell: Get-ChildItem, Get-Content, Select-String, Remove-Item -Recurse -Force

Rule #4: FastMCP Standards

  • NEVER use description= parameter in @mcp.tool()
  • ALWAYS use comprehensive docstrings (50+ lines minimum)
  • ALWAYS include: Args, Returns, Examples, Notes sections

OneNote-Specific

This MCP server integrates with Microsoft OneNote:

  • Handle Microsoft Graph API authentication
  • Respect rate limits
  • Handle notebook/section/page hierarchy properly

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