Skip to content

Add Cursorrules Collection to Directories#164

Open
nedcodes-ok wants to merge 3 commits intoPatrickJS:mainfrom
nedcodes-ok:add-cursorrules-collection
Open

Add Cursorrules Collection to Directories#164
nedcodes-ok wants to merge 3 commits intoPatrickJS:mainfrom
nedcodes-ok:add-cursorrules-collection

Conversation

@nedcodes-ok
Copy link

@nedcodes-ok nedcodes-ok commented Feb 11, 2026

Hi! Adding our open-source Cursorrules Collection to the Directories section.

It's a curated, categorized collection of .cursorrules organized by language (Python, TypeScript, Go, etc.), framework (React, Next.js, Django, etc.), and development practice (testing, security, clean code, etc.).

All MIT licensed. Hope it's useful to the community!

Summary by CodeRabbit

  • Documentation
    • Added a new directory entry "Cursorrules Collection" with coverage details.
    • Removed the "CursorDirectory" entry.
    • Retained the "CursorList" entry (ordering adjusted).

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 11, 2026

📝 Walkthrough

Walkthrough

Removed the CursorDirectory entry from the README Directories section and added a new Cursorrules Collection entry; CursorList remains present (ordering adjusted). No code, API, or behavioral changes.

Changes

Cohort / File(s) Summary
Documentation Update
README.md
Removed CursorDirectory entry and inserted Cursorrules Collection in the Directories section (two locations). CursorList retained with adjusted ordering. No code or behavior changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Suggested reviewers

  • PatrickJS

Poem

🐰 I hopped into the README light,
Swapped a directory for rules tonight.
Thirty-three files now softly sing,
A tiny change — a little spring. 🥕

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: adding Cursorrules Collection to the Directories section, which is clearly reflected in the file summary.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

No actionable comments were generated in the recent review. 🎉


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🤖 Fix all issues with AI agents
In `@README.md`:
- Line 294: The README contains an external link for "Cursorrules Collection"
that violates the guideline requiring relative links; either convert that GitHub
URL to the appropriate relative path within the repo or get explicit
confirmation that external links are permitted for this section, then update the
"Cursorrules Collection" entry accordingly so the link is relative (or document
the exception) and ensure the link target exists.
- Around line 292-294: The README list is inconsistent: "Cursorrules Collection"
has a descriptive sentence while "CursorList" and "CursorDirectory" do not;
update the three list items to be consistent by either adding short one-line
descriptions to "CursorList" and "CursorDirectory" matching the style of
"Cursorrules Collection" or removing the description from "Cursorrules
Collection" so all three are plain links—edit the list entries for CursorList,
CursorDirectory, and Cursorrules Collection accordingly to enforce uniform
formatting.
- Around line 292-294: Reorder the three directory links in README.md so they
are alphabetized: replace the current block containing "CursorList",
"CursorDirectory", and "Cursorrules Collection" with the alphabetical sequence
"CursorDirectory", then "CursorList", then "Cursorrules Collection"; update only
the entries in that Directories category (look for the list items mentioning
CursorDirectory, CursorList, and Cursorrules Collection) and keep URLs and
descriptions unchanged.

README.md Outdated
Comment on lines +292 to +294
- [CursorList](https://cursorlist.com)
- [CursorDirectory](https://cursor.directory/)
- [Cursorrules Collection](https://github.com/cursorrulespacks/cursorrules-collection) - A curated, categorized collection of .cursorrules organized by language, framework, and practice.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Make Directories list item formatting consistent.

This new entry includes a description, but the two existing Directories entries do not. Either add descriptions to the other entries or remove the description here to keep formatting consistent.

As per coding guidelines, “Use consistent formatting for list items in the README.md file.”

🤖 Prompt for AI Agents
In `@README.md` around lines 292 - 294, The README list is inconsistent:
"Cursorrules Collection" has a descriptive sentence while "CursorList" and
"CursorDirectory" do not; update the three list items to be consistent by either
adding short one-line descriptions to "CursorList" and "CursorDirectory"
matching the style of "Cursorrules Collection" or removing the description from
"Cursorrules Collection" so all three are plain links—edit the list entries for
CursorList, CursorDirectory, and Cursorrules Collection accordingly to enforce
uniform formatting.

⚠️ Potential issue | 🟡 Minor

Fix alphabetical ordering in Directories.

“CursorDirectory” should come before “CursorList,” and “Cursorrules Collection” should be placed accordingly to preserve alphabetical order within the category.

Suggested reorder
- - [CursorList](https://cursorlist.com)
- - [CursorDirectory](https://cursor.directory/)
- - [Cursorrules Collection](https://github.com/cursorrulespacks/cursorrules-collection) - A curated, categorized collection of .cursorrules organized by language, framework, and practice.
+ - [CursorDirectory](https://cursor.directory/)
+ - [CursorList](https://cursorlist.com)
+ - [Cursorrules Collection](https://github.com/cursorrulespacks/cursorrules-collection) - A curated, categorized collection of .cursorrules organized by language, framework, and practice.

As per coding guidelines, “Maintain alphabetical order within each category in the README.md file.”

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- [CursorList](https://cursorlist.com)
- [CursorDirectory](https://cursor.directory/)
- [Cursorrules Collection](https://github.com/cursorrulespacks/cursorrules-collection) - A curated, categorized collection of .cursorrules organized by language, framework, and practice.
- [CursorDirectory](https://cursor.directory/)
- [CursorList](https://cursorlist.com)
- [Cursorrules Collection](https://github.com/cursorrulespacks/cursorrules-collection) - A curated, categorized collection of .cursorrules organized by language, framework, and practice.
🤖 Prompt for AI Agents
In `@README.md` around lines 292 - 294, Reorder the three directory links in
README.md so they are alphabetized: replace the current block containing
"CursorList", "CursorDirectory", and "Cursorrules Collection" with the
alphabetical sequence "CursorDirectory", then "CursorList", then "Cursorrules
Collection"; update only the entries in that Directories category (look for the
list items mentioning CursorDirectory, CursorList, and Cursorrules Collection)
and keep URLs and descriptions unchanged.

README.md Outdated

- [CursorList](https://cursorlist.com)
- [CursorDirectory](https://cursor.directory/)
- [Cursorrules Collection](https://github.com/cursorrulespacks/cursorrules-collection) - A curated, categorized collection of .cursorrules organized by language, framework, and practice.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Confirm link format requirement (relative links).

The new entry links to an external GitHub URL, which conflicts with the guideline to keep README links relative. If external links are allowed in this section, please confirm; otherwise, adjust to a relative link if applicable.

As per coding guidelines, “Ensure all links in the README.md file are relative and correct.”

🤖 Prompt for AI Agents
In `@README.md` at line 294, The README contains an external link for "Cursorrules
Collection" that violates the guideline requiring relative links; either convert
that GitHub URL to the appropriate relative path within the repo or get explicit
confirmation that external links are permitted for this section, then update the
"Cursorrules Collection" entry accordingly so the link is relative (or document
the exception) and ensure the link target exists.

@nedcodes-ok nedcodes-ok force-pushed the add-cursorrules-collection branch from fc31d13 to 811ac03 Compare February 12, 2026 16:28
@nedcodes-ok
Copy link
Author

Hey — just checking in on this. All review feedback has been addressed and it should be ready to merge. Let me know if anything else is needed!

@nedcodes-ok
Copy link
Author

Hey @nicepkg — just checking in on this. Addressed all the CodeRabbit feedback and the PR is mergeable. Let me know if anything else needs updating. No rush, just wanted to make sure it didn't fall off the radar.

@nedcodes-ok
Copy link
Author

Friendly bump — the collection is at 77 rules now (languages, frameworks, practices, tools) with both .mdc and .cursorrules formats. Let me know if anything needs updating on this PR.

@nedcodes-ok
Copy link
Author

Hey @PatrickJS — friendly bump on this. The collection is at 110+ rules now with MDC format support. Happy to make any changes needed to get this merged. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant