neotoma / rules
Cursor rule38 starsChanged 2 months agoMITView on GitHub
Load when editing rules or commands: edit source in docs/ or foundation/agent_instructions/, never .cursor/rules or .cursor/commands; run setup_cursor_copies after editing.
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,144 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 repository101 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- .cursor/rules/autonomous_execution.mdcCursor rule
- .cursor/rules/cursor_rules_sync.mdcCursor rule
- .cursor/rules/cursor_rules_sync_requirement.mdcCursor rule
- site_pages/llms.txtllms.txt
- advisorySkill
- analyzeSkill
- auditSkill
- commitSkill
- create-planSkill
- create_planSkill
- create-prototypeSkill
- create_prototypeSkill
- create_prSkill
- create-releaseSkill
- create_releaseSkill
- create-ruleSkill
- create_ruleSkill
- debugSkill
- draft-illustrationSkill
- draft_illustrationSkill
- endSkill
- evaluate_positioningSkill
- final-reviewSkill
- final_reviewSkill
- fix-feature-bugSkill
- fix_feature_bugSkill
- learnSkill
- manage-error-debuggingSkill
- manage_error_debuggingSkill
- neversight_learn_skills.dev_obviously_awesomeSkill
- process_issuesSkill
- process_prsSkill
- publish-planSkill
- publish_planSkill
- publishSkill
- pullSkill
- pushSkill
- recover_sqlite_databaseSkill
- releaseSkill
- report-errorSkill
- report_errorSkill
- reportSkill
- reviewSkill
- run-feature-workflowSkill
- run_feature_workflowSkill
- setup-commandsSkill
- setup_commandsSkill
- setup-cursor-copiesSkill
- setup_cursor_copiesSkill
- store-neotomaSkill
- store_neotomaSkill
- sync-env-from-1passwordSkill
- sync_env_from_1passwordSkill
- analyzeSkill
- auditSkill
- commitSkill
- create-planSkill
- create-prototypeSkill
- The first 60 shown.
The file
We split this cursor_rules_editing.mdc into the rules it gives an agent
9 rules. About 0 are common, 5 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 44
Not the source of truth
- Distinctive: line 63
Check the header comment (added by setup script) for source file path
- Very specific: line 67
Look for pattern: docs/{subdirectory}/*_rules.mdc or foundation/agent_instructions/cursor_rules/*.mdc
- Distinctive: line 68
Use file naming pattern:
- Very specific: line 75
MUST NOT edit files in .cursor/rules/ or .cursor/commands/
- Very specific: line 76
MUST edit source files in docs/ or foundation/agent_instructions/
- Very specific: line 77
MUST run /setup_cursor_copies after editing source files to sync changes
- Distinctive: line 78
MUST verify edits are in source files, not copies
- Distinctive: line 90
Before committing rule or command changes:
≈ “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: "Load when editing rules or commands: edit source in docs/ or foundation/agent_instructions/, never .cursor/rules or .cursor/commands; run setup_cursor_copies after editing."
alwaysApply: false
---
# ⚠️ DO NOT EDIT THIS FILE DIRECTLY
#
# This is a copy of: foundation/agent_instructions/cursor_rules/cursor_rules_editing.mdc
# Source of truth: foundation/agent_instructions/cursor_rules/cursor_rules_editing.mdc
#
# To edit this rule:
# 1. Edit the source file: foundation/agent_instructions/cursor_rules/cursor_rules_editing.mdc
# 2. Run '/setup_cursor_copies' to sync changes
#
# This file will be overwritten when running setup_cursor_copies.
# Cursor Rules Editing Rule
## Purpose
Ensures agents always edit the source files for cursor rules and commands, never the copies in `.cursor/rules/` or `.cursor/commands/` directories.
## Source of Truth Locations
**Foundation rules and commands:**
- Source: `foundation/agent_instructions/cursor_rules/` and `foundation/agent_instructions/cursor_commands/`
- Copies: `.cursor/rules/` and `.cursor/commands/` (created by `/setup_cursor_copies`)
**Repository rules:**
- Source: `docs/` subdirectories (e.g., `docs/foundation/`, `docs/conventions/`, `docs/developer/`)
- Copies: `.cursor/rules/` (created by `/setup_cursor_copies`)
**Repository commands:**
- Source: `docs/` subdirectories or repository-specific command locations
- Copies: `.cursor/commands/` (created by `/setup_cursor_copies`)
## Rule
**MUST NOT edit files in `.cursor/rules/` or `.cursor/commands/`**
These directories contain copies that are:
- Automatically generated by `/setup_cursor_copies`
- Overwritten when running `/setup_cursor_copies`
- Not the source of truth
## Agent Actions
### When Editing Rules or Commands
1. **Identify the source file:**
- Foundation rules: `foundation/agent_instructions/cursor_rules/{name}.mdc`
- Foundation commands: `foundation/agent_instructions/cursor_commands/{name}.md`
- Repository rules: `docs/{subdirectory}/{name}_rules.mdc` or `docs/{subdirectory}/{name}_rules.md`
- Repository commands: `docs/{subdirectory}/{name}_command.md` or repository-specific command locations
2. **Edit the source file directly**
3. **After editing, run `/setup_cursor_copies`** to sync changes to `.cursor/` directory
### Detecting Source Files
**For files in `.cursor/rules/` or `.cursor/commands/`:**
- Check the header comment (added by setup script) for source file path
- Header format:
- `.mdc` files: YAML frontmatter comment style (`---` with `#` comments)
- `.md` files: HTML comment style (`<!-- -->`)
- Look for pattern: `docs/{subdirectory}/*_rules.mdc` or `foundation/agent_instructions/cursor_rules/*.mdc`
- Use file naming pattern:
- Foundation rules use original filenames (no prefix)
- `{subdirectory}_{name}_rules.mdc` → `docs/{subdirectory}/{name}_rules.mdc`
- Commands use original filenames (no prefix)
## Constraints
- MUST NOT edit files in `.cursor/rules/` or `.cursor/commands/`
- MUST edit source files in `docs/` or `foundation/agent_instructions/`
- MUST run `/setup_cursor_copies` after editing source files to sync changes
- MUST verify edits are in source files, not copies
## Forbidden Patterns
- Editing `.cursor/rules/*.mdc` or `.cursor/rules/*.md` directly
- Editing `.cursor/commands/*.md` directly (foundation commands or repository commands)
- Assuming `.cursor/` files are the source of truth
- Skipping `/setup_cursor_copies` after editing source files
- Removing header comments from copied files (they will be re-added by the script)
## Validation
Before committing rule or command changes:
- [ ] Changes are in source files (`docs/` or `foundation/agent_instructions/`)
- [ ] No changes were made to `.cursor/rules/` or `.cursor/commands/`
- [ ] `/setup_cursor_copies` has been run to sync changes
- [ ] All copied files in `.cursor/` have header comments (verify by checking first few lines)
## Related Documents
- `foundation/agent_instructions/cursor_rules/instruction_documentation.mdc` - How to document instructions
- `foundation/agent_instructions/cursor_commands/setup_cursor_copies.md` - Command to sync copies
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.

