We split this RULE.md into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈0

  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. Very specific:

   CRITICAL RULE: All planning-related markdown files MUST be created in the planning/ directory, never at the top level.

   line 8

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

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

  • AGENTS.mdAGENTS.md
  • CLAUDE.mdCLAUDE.md
  • .cursor/rules/code-quality/RULE.mdCursor rule
  • .cursor/rules/testing-standards/RULE.mdCursor rule
  • github-issue-trackingSkill
  • nanovm-opcode-debuggingSkill
  • reading-nanolangSkill
  • release-readinessSkill
  • releasing-documentationSkill
  • releasing-presentationSkill
  • releasingSkill
  • roadmap-executionSkill
  • session-completionSkill