[PR #4168] Add Cursor Rules #58950

Open
opened 2026-06-21 12:24:16 -05:00 by GiteaMirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/sindresorhus/awesome/pull/4168
Author: @PatrickJS
Created: 5/14/2026
Status: 🔄 Open

Base: mainHead: codex/add-awesome-cursorrules


📝 Commits (5)

  • bd0c320 Add Cursor Rules to awesome list
  • e0101c1 Merge branch 'main' into codex/add-awesome-cursorrules
  • 6cb9caa Merge branch 'main' into codex/add-awesome-cursorrules
  • c6e17f9 Merge branch 'main' into codex/add-awesome-cursorrules
  • cf1ae91 Merge branch 'main' into codex/add-awesome-cursorrules

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 readme.md (+1 -0)

📄 Description

Supersedes #3503 after addressing the review feedback.

https://github.com/PatrickJS/awesome-cursorrules 30k+ stars

Configuration files that customize Cursor's AI-assisted coding behavior.

By submitting this pull request I confirm I've read and complied with the below requirements

Requirements for your pull request

  • Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. Instead use #2242 for incubation visibility.
  • Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
  • You have to review at least 2 other open pull requests.
  • You have read and understood the instructions for creating a list.
  • This pull request has a title in the format Add Name of List. It should not contain the word Awesome.
  • Your entry here should include a short description of the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb. It should not contain the name of the list.
  • Your entry should be added at the bottom of the appropriate category.
  • The title of your entry should be title-cased and the URL to your list should end in #readme.
  • No blockchain-related lists.
  • The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

  • Has been around for at least 30 days.
  • Run awesome-lint on your list and fix the reported issues.
  • The default branch should be named main, not master.
  • Includes a succinct description of the project/theme at the top of the readme.
  • It's the result of hard work and the best I could possibly produce.
  • The repo name of your list should be in lowercase slug format: awesome-name-of-list.
  • The heading title of your list should be in title case format: # Awesome Name of List.
  • Non-generated Markdown file in a GitHub repo.
  • The repo should have awesome-list and awesome as GitHub topics.
  • Not a duplicate. Please search for existing submissions.
  • Only has awesome items. Awesome lists are curations of the best, not everything.
  • Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs.
  • Includes a project logo/illustration whenever possible.
  • Entries have a description, unless the title is descriptive enough by itself.
  • Includes the Awesome badge.
  • Has a Table of Contents section named Contents, as the first section in the list.
  • Has an appropriate license.
  • Has contribution guidelines.
  • All non-important but necessary content is grouped in a Footnotes section at the bottom of the readme when present.
  • Has consistent formatting and proper spelling/grammar.
  • Does not use hard-wrapping.
  • Does not include a CI badge.
  • Does not include an Inspired by awesome-foo or Inspired by the Awesome project link at the top of the readme.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/sindresorhus/awesome/pull/4168 **Author:** [@PatrickJS](https://github.com/PatrickJS) **Created:** 5/14/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `codex/add-awesome-cursorrules` --- ### 📝 Commits (5) - [`bd0c320`](https://github.com/sindresorhus/awesome/commit/bd0c3200c3b2ff421cb353c1ba83bc3270220e26) Add Cursor Rules to awesome list - [`e0101c1`](https://github.com/sindresorhus/awesome/commit/e0101c1814107b2c64a61cc5cd9779707fee2004) Merge branch 'main' into codex/add-awesome-cursorrules - [`6cb9caa`](https://github.com/sindresorhus/awesome/commit/6cb9caa558a12afb063932c37d42f50434ec41ab) Merge branch 'main' into codex/add-awesome-cursorrules - [`c6e17f9`](https://github.com/sindresorhus/awesome/commit/c6e17f9102b7ce00295e7143bf3873e58c55bd26) Merge branch 'main' into codex/add-awesome-cursorrules - [`cf1ae91`](https://github.com/sindresorhus/awesome/commit/cf1ae91d838b3dd51b42fb51a1d2acfd25ebe536) Merge branch 'main' into codex/add-awesome-cursorrules ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `readme.md` (+1 -0) </details> ### 📄 Description Supersedes #3503 after addressing the review feedback. https://github.com/PatrickJS/awesome-cursorrules 30k+ stars Configuration files that customize Cursor's AI-assisted coding behavior. ### By submitting this pull request I confirm I've read and complied with the below requirements ## Requirements for your pull request - [x] Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. Instead use #2242 for incubation visibility. - [x] Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive. - [x] You have to review at least 2 other open pull requests. - [x] You have read and understood the instructions for creating a list. - [x] This pull request has a title in the format `Add Name of List`. It should not contain the word `Awesome`. - [x] Your entry here should include a short description of the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb. It should not contain the name of the list. - [x] Your entry should be added at the bottom of the appropriate category. - [x] The title of your entry should be title-cased and the URL to your list should end in `#readme`. - [x] No blockchain-related lists. - [x] The suggested Awesome list complies with the below requirements. ## Requirements for your Awesome list - [x] Has been around for at least 30 days. - [x] Run `awesome-lint` on your list and fix the reported issues. - [x] The default branch should be named `main`, not `master`. - [x] Includes a succinct description of the project/theme at the top of the readme. - [x] It's the result of hard work and the best I could possibly produce. - [x] The repo name of your list should be in lowercase slug format: `awesome-name-of-list`. - [x] The heading title of your list should be in title case format: `# Awesome Name of List`. - [x] Non-generated Markdown file in a GitHub repo. - [x] The repo should have `awesome-list` and `awesome` as GitHub topics. - [x] Not a duplicate. Please search for existing submissions. - [x] Only has awesome items. Awesome lists are curations of the best, not everything. - [x] Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. - [x] Includes a project logo/illustration whenever possible. - [x] Entries have a description, unless the title is descriptive enough by itself. - [x] Includes the Awesome badge. - [x] Has a Table of Contents section named `Contents`, as the first section in the list. - [x] Has an appropriate license. - [x] Has contribution guidelines. - [x] All non-important but necessary content is grouped in a `Footnotes` section at the bottom of the readme when present. - [x] Has consistent formatting and proper spelling/grammar. - [x] Does not use hard-wrapping. - [x] Does not include a CI badge. - [x] Does not include an `Inspired by awesome-foo` or `Inspired by the Awesome project` link at the top of the readme. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-06-21 12:24:16 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/awesome-sindresorhus#58950