Skip to content

Commit fa59f45

Browse files
committed
Merge remote-tracking branch 'upstream/main' into add-styleseed
# Conflicts: # README.md
2 parents 28493cd + b044f95 commit fa59f45

1,532 files changed

Lines changed: 27909 additions & 29251 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

.cursorrules

Lines changed: 0 additions & 82 deletions
This file was deleted.

.github/CODEOWNERS

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
# Require maintainer review for repository automation and policy controls.
2+
.github/workflows/** @PatrickJS
3+
scripts/** @PatrickJS
4+
.github/CODEOWNERS @PatrickJS

.github/ISSUE_TEMPLATE/config.yml

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
blank_issues_enabled: false
2+
contact_links:
3+
- name: Cursor product, account, or billing support
4+
url: https://docs.cursor.com/
5+
about: Use Cursor's official docs, forum, or support channels for editor, account, billing, subscription, and license questions.
Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
name: Repository maintenance
2+
description: Report a broken link, duplicate entry, categorization problem, or repository hygiene issue.
3+
title: "[Maintenance]: "
4+
body:
5+
- type: markdown
6+
attributes:
7+
value: |
8+
Use this form for issues with this repository itself. Do not use it for Cursor product support, account or billing questions, third-party tools, license sharing, or license bypasses.
9+
10+
- type: dropdown
11+
id: issue_type
12+
attributes:
13+
label: Issue type
14+
options:
15+
- Broken README link
16+
- Duplicate or near-duplicate rule
17+
- Incorrect category
18+
- Rule file formatting problem
19+
- Repository hygiene problem
20+
validations:
21+
required: true
22+
23+
- type: textarea
24+
id: details
25+
attributes:
26+
label: Details
27+
description: Include the relevant file path, README section, link, or rule name and explain what needs maintainer attention.
28+
validations:
29+
required: true
30+
31+
- type: checkboxes
32+
id: scope_acknowledgement
33+
attributes:
34+
label: Scope acknowledgement
35+
options:
36+
- label: I am not asking for third-party tool support, account sharing, or license bypass help.
37+
required: true
Lines changed: 52 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,52 @@
1+
name: Cursor rule request
2+
description: Request a new Cursor rule or a focused change to an existing rule in this repository.
3+
title: "[Rule]: "
4+
body:
5+
- type: markdown
6+
attributes:
7+
value: |
8+
Thanks for helping improve Awesome Cursor Rules. This repository is for reusable Cursor rule content and repository maintenance, not support for Cursor accounts, subscriptions, third-party tools, license sharing, or license bypasses.
9+
10+
- type: dropdown
11+
id: request_type
12+
attributes:
13+
label: Request type
14+
options:
15+
- New Cursor rule
16+
- Update to an existing rule
17+
- Rule quality or correctness issue
18+
validations:
19+
required: true
20+
21+
- type: input
22+
id: affected_rule
23+
attributes:
24+
label: Existing rule path or proposed topic
25+
description: For updates, include the existing path. For new rules, name the framework, language, workflow, or tool the rule should cover.
26+
placeholder: rules/nextjs-typescript.mdc
27+
validations:
28+
required: true
29+
30+
- type: textarea
31+
id: cursor_workflow
32+
attributes:
33+
label: Cursor workflow this improves
34+
description: Explain the concrete Cursor coding workflow, failure mode, or repeatable best practice this rule should cover.
35+
validations:
36+
required: true
37+
38+
- type: textarea
39+
id: proposed_rule
40+
attributes:
41+
label: Proposed rule content or expected change
42+
description: Include draft rule text when possible. Keep it neutral, practical, and specific to Cursor-assisted development.
43+
validations:
44+
required: true
45+
46+
- type: checkboxes
47+
id: scope_acknowledgement
48+
attributes:
49+
label: Scope acknowledgement
50+
options:
51+
- label: I am not asking for third-party tool support, account sharing, or license bypass help.
52+
required: true

.github/pull_request_template.md

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
## Summary
2+
3+
<!-- What are you adding or fixing? Keep it specific. -->
4+
5+
## Contribution Type
6+
7+
<!-- Check one. Standalone external tool, product, directory, marketplace, or service listings are not accepted. -->
8+
9+
- [ ] New Cursor rule file or rules folder
10+
- [ ] Update/fix to an existing rule
11+
- [ ] New `rules/*.mdc` rule
12+
- [ ] Documentation or README cleanup
13+
14+
## Value To Cursor Users
15+
16+
<!-- Explain the practical Cursor workflow this improves. Keep it neutral and focused on reusable rule value, not product marketing. -->
17+
18+
## Added Or Changed Files
19+
20+
<!-- List the important files and why they changed. -->
21+
22+
-
23+
24+
## Quality Checklist
25+
26+
- [ ] The contribution includes original rule content, or clearly credits the source.
27+
- [ ] New rule files use a descriptive kebab-case filename, such as `react-typescript.mdc`.
28+
- [ ] New `rules/*.mdc` files include frontmatter with a non-empty `description`, relevant `globs`, and `alwaysApply: false` unless the rule is universal.
29+
- [ ] README links use canonical GitHub URLs for repo files and point to the correct category.
30+
- [ ] The text is neutral and useful, not sales copy.
31+
- [ ] This is not a standalone external tool, product, directory, marketplace, or service listing.
32+
- [ ] No secrets, tokens, affiliate links, tracking links, or unrelated product claims are included.
33+
- [ ] I checked for duplicate or near-duplicate existing entries.
34+
35+
## Notes For Maintainers
36+
37+
<!-- Anything maintainers should review closely, such as licensing, source attribution, or why this belongs in the main README. -->

0 commit comments

Comments
 (0)