Add CursorAI Forum Feature Request for Project Rules Subdirectory Scanning

- Create new page documenting Cursor forum feature request for scanning project rules in subdirectories
- Update "Share Cursor Project Rules" page with reference to new forum feature request
- Highlight the importance of modular project rule sharing and collaboration

Author: codekiln

pages/CursorAI___Forum___25___03___Scan for Project Rules in Subdirectories of .cursor___rules.md

@@ -0,0 +1,9 @@
+created-by:: [[Person/codekiln]]
+date-created:: [[2025/03]]
+
+- # [Scan for Project Rules in Subdirectories of .cursor/rules - Feature Requests - Cursor - Community Forum](https://forum.cursor.com/t/scan-for-project-rules-in-subdirectories-of-cursor-rules/61534)
+	- ## #OP
+		- According to [my tests](https://codekiln.github.io/logseq-encode-garden/#/page/cursorai%2Fproject%20rule%2Ftest), as of `v0.46.11`, Cursor does not activate project rules which are stored in sub-directories of the `.cursor/rules/` location. See [codekiln/cursor-project-rule-test: Testing the Cursor Project Rule feature](https://github.com/codekiln/cursor-project-rule-test/tree/main) for an independent repository you can clone and test.
+		- If Cursor did, then we would be able to use [Git Submodules](https://git-scm.com/book/en/v2/Git-Tools-Submodules) to reference Cursor Project Rules stored in a centralized repository and shared among many users and projects. This would unlock a whole new way to share project rules between users and repositories. In my opinion, it’s very important that Cursor enable its community develop to collaborate together on developing mature, open source cursor rules, and adding this feature would be an important step in that direction.
+		  A number of users in the community have been interested in this functionality; see [Mastering Cursor Rules: A Developer’s Guide to Smart AI Integration - DEV Community](https://dev.to/dpaluy/mastering-cursor-rules-a-developers-guide-to-smart-ai-integration-1k65) for an example.
+		- I’ve listed a number of dynamics and workarounds at [CursorAI/How To/Share Cursor Project Rules Across Repositories and Users](https://codekiln.github.io/logseq-encode-garden/#/page/cursorai%2Fhow%20to%2Fshare%20cursor%20project%20rules%20across%20repositories%20and%20users).

pages/CursorAI___How To___Share Cursor Project Rules Across Repositories and Users.md

@@ -1,11 +1,12 @@
 # How to share [[CursorAI/Project Rules]] across multiple projects and users
-	- Cursor project rules are a unique set of [[Metaprogramming]] tools. A set of related cursor project rules define the [[CursorAI Agent Mode]]'s [[Agentic System]], each encapsulating a particular aspect of the overall capabilities.
+	- Cursor project rules are a unique set of [[Metaprogramming]] tools. A set of related cursor project rules define the [[CursorAI Agent Mode]]'s [[Agentic System]], each encapsulating a particular aspect of the overall capabilities of that system.
 	- It is important for Cursor's users be able to share and collaborate on cursor project rules in a modular, open-source manner, while maintaining the ability to version the rules and obtain updates to the rules after they have been tested.
-	- In my opinion, they deserve a new type of  [[Package Manager]] that allows for rapid prototyping, that is, that allowed one to install a particular version of a "package" of rules, and then modify the library on the fly in response to observed behavior, and have the option to easily offer those contributions back to the source as a merge request. The proposal for such a package manager is out of the scope of this page, however.
+	- In my opinion, Cursor Project Rules deserve a new type of  [[Package Manager]] that allows for rapid prototyping, that is, that allowed one to install a particular version of a "package" of rules, and then modify the library on the fly in response to observed behavior, and have the option to easily offer those contributions back to the source as a merge request. The proposal for such a package manager is out of the scope of this page, however.
 	- This page focuses on how to achieve collaborative sharing of versioned, vetted project rules across repositories and users.
 	- ## It is not currently feasible to create git submodules under `.cursor/rules`
 		- It would be great if Cursor sourced project rules in subdirectories. This would enable a modular and related collection of cursor project rules to be located in a single git repository. Then downstream projects could use [[git submodules]] to link them in under `.cursor/rules/<submodule_folder>`. Any changes to the rule could be contributed back to the source repository for sharing with others.
 		- Unfortunately, according to my tests at [[CursorAI Project Rule Tests]], in particular, [[CursorAI/Project Rule/Test/Agent/❌/Find MDC/in Subfolder]], this is not currently possible.
+		- See [[CursorAI/Forum/25/03/Scan for Project Rules in Subdirectories of .cursor/rules]] for a feature request that has been submitted.
 	- ## Possible workarounds
 		- ### Copy and paste
 			- Of course, it's possible to copy and paste cursor project rules from one repository into the `.cursor/rules` directory of each project or user. Over time, though, there will be drift between the most up-to-date version of the rules from the upstream repository and the one that was copied in.