transcripts-mcp / rules
Cursor rule8 starsChanged 2 months agoMITView on GitHub
Defines the workaround process for creating and editing cursor rule files
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 repository33 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .deepsec/AGENTS.mdAGENTS.md
- .cursor/rules/010-workflow.mdcCursor rule
- .cursor/rules/020-codebase-structure.mdcCursor rule
- .cursor/rules/030-coding-style.mdcCursor rule
- .cursor/rules/031-never-use-any.mdcCursor rule
- .cursor/rules/032-import-rules.mdcCursor rule
- .cursor/rules/050-testing.mdcCursor rule
- .cursor/rules/070-comments-defensive-programming.mdcCursor rule
- .cursor/rules/080-ai-interaction.mdcCursor rule
- .cursor/rules/090-changesets.mdcCursor rule
- .cursor/rules/095-calldiff.mdcCursor rule
- .cursor/rules/999-mdc-format.mdcCursor rule
- adversarial-reviewSkill
- agent-browserSkill
- calldiffSkill
- changesetSkill
- commitSkill
- deslopSkill
- fix-prSkill
- git-conventionsSkill
- humanizerSkill
- improve-codebase-architectureSkill
- logging-best-practicesSkill
- opensrcSkill
- rebaseSkill
- recomposing-commitsSkill
- security-reviewSkill
- show-meSkill
- simplifySkill
- thermo-nuclear-code-quality-reviewSkill
- wait-whatSkill
- writing-for-agentsSkill
The file
We split this 990-cursor-rule-editing-workaround.mdc into the rules it gives an agent
6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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
- Distinctive: line 28
Use .mdc-tmp extension for all new or modified cursor rules
- Distinctive: line 29
Place temporary files in same location as target .mdc file pattern: "^.*\\.mdc-tmp$"
- Distinctive: line 37
Only after approval, make edits in the temporary file
- Distinctive: line 49
Use terminal command (cp or mv) to create final .mdc file - NEVER use internal file editing tools
- Very specific: line 50
Remove temporary file after successful creation notes: | Due to a known limitation, internal file editing tools cannot be used to create or …
- Very specific: line 53
Always use terminal commands like cp or mv for the final step.
≈ “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.
Files
---
description: Defines the workaround process for creating and editing cursor rule files
globs: "**/*.mdc-tmp,**/*.mdc"
---
# Cursor Rule Editing Workaround
Defines the process for creating and editing cursor rule files to work around Cursor limitations.
<rules>
<filters>
INCLUDE:
- type: file_extension
pattern: "\\.mdc(-tmp)?$"
- type: event
pattern: "(file_create|file_modify)"
</filters>
<rule>
name: mdc-file-editing-process
description: Enforces the workaround process for editing cursor rule files
ENFORCE:
- type: process
steps:
- name: temporary_file_creation
description: Create or edit files with temporary extension
requirements:
- Use .mdc-tmp extension for all new or modified cursor rules
- Place temporary files in same location as target .mdc file
pattern: "^.*\\.mdc-tmp$"
- name: existing_file_modification
description: Process for modifying existing rules
requirements:
- Copy existing .mdc file to .mdc-tmp before ANY modifications
- Get user approval of the initial copy
- Only after approval, make edits in the temporary file
- Maintain original file until changes are approved
notes: |
The initial copy step and its approval are crucial for:
- Verifying the starting point is correct
- Making the subsequent changes more visible
- Preventing accidental loss of content
- name: file_finalization
description: Process for finalizing rule files
requirements:
- Review changes in temporary file
- Use terminal command (cp or mv) to create final .mdc file - NEVER use internal file editing tools
- Remove temporary file after successful creation
notes: |
Due to a known limitation, internal file editing tools cannot be used to create or modify .mdc files directly.
Always use terminal commands like `cp` or `mv` for the final step.
examples:
- scenario: "Creating new rule"
steps:
- "Create: example-rule.mdc-tmp"
- "Get approval for initial empty file"
- "Edit temporary file"
- "Review changes"
- "Copy to: example-rule.mdc"
- "Remove temporary file"
- scenario: "Modifying existing rule"
steps:
- "Copy existing.mdc to existing.mdc-tmp"
- "Get approval for initial copy"
- "Edit temporary file"
- "Review changes"
- "Copy back to existing.mdc"
- "Remove temporary file"
metadata:
priority: high
version: 1.0
</rule>
</rules> 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
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.