Skip to content

feat: move cursor rules to .cursor/rules, add metadata #474

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

JowiAoun
Copy link

@JowiAoun JowiAoun commented Jul 5, 2025

What does this do?

  • This template uses the legacy way of defining cursor rules with .cursorrules. Other rules are found in prompts/. The new way of defining rules is outlined on the Cursor context rules documentation, and defines rules under .cursor/rules/. With the new way of defining rules, it is easy to define globs and when rules should be used by Agents.

Why did you do this?

Defining rules this way gives developers more flexibility in using and creating rules as the new way of creating rules through Cursor will create them in .cursor/rules/, reducing project clutter. Additionally, rules are now visible from the context Rules selection.
image
image

Who/what does this impact?

Since this update has been here for some time now, users should be acquainted with the new way of defining and using rules. Otherwise, this should not affect any current users.

How did you test this?

Each rule was ran to accomplish the same goal using the current prompts/ and new .cursor/rules/.

Copy link

netlify bot commented Jul 5, 2025

Deploy Preview for obytes-starter canceled.

Name Link
🔨 Latest commit 4e2f3d5
🔍 Latest deploy log https://app.netlify.com/projects/obytes-starter/deploys/68689ecd6d24a40008156df9

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

Successfully merging this pull request may close these issues.

2 participants