McpServer / rules
Cursor rule4 starsChanged 28 days agoApache-2.0View on GitHub
Mandatory MCP session logging before any work
We split this mcp-session-logging.mdc into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Before doing ANY work on ANY user request, you MUST complete these steps in order:
≈ “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.
Files
--- description: Mandatory MCP session logging before any work alwaysApply: true --- # MCP Session Logging — Mandatory Precondition ## ⚠️ PRIORITY ORDER — NON-NEGOTIABLE ⚠️ **Speed is never more important than following workspace procedures.** Before doing ANY work on ANY user request, you MUST complete these steps in order: 1. **Read `AGENTS-README-FIRST.yaml`** in the repo root for the current API key and endpoints 2. **GET `/health`** to verify the MCP server is running 3. **POST `/mcp/sessionlog`** with your session entry — do NOT proceed until this succeeds 4. **GET `/mcp/sessionlog?limit=5`** to review recent session history for context 5. **GET `/mcp/todo`** to check current tasks 6. **THEN** begin working on the user's request On EVERY subsequent user message: 1. POST an updated session log entry BEFORE starting work 2. Complete the user's request 3. POST the final session log with results, actions taken, and files modified **If you skip any of these steps, STOP and go back and do them before continuing.** Session logging is not optional, not deferred, and not secondary to the task. Failure to maintain the session log is a compliance violation.
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 3,978 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 repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- bash-usageSkill
- byrd-tdd-processSkill
- edit-file-usageSkill
- git-usageSkill
- mcp-requirements-traceabilitySkill
- mcp-session-loggingSkill
- mcp-todoSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.