Skip to content

Added cursor rules docs page #1965

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

Merged
merged 1 commit into from
Apr 22, 2025
Merged

Added cursor rules docs page #1965

merged 1 commit into from
Apr 22, 2025

Conversation

D-K-P
Copy link
Member

@D-K-P D-K-P commented Apr 22, 2025

Summary by CodeRabbit

  • New Features

    • Introduced a new guide on integrating and using Cursor rules with Trigger.dev, including setup instructions, practical tips, and a demonstration video.
  • Documentation

    • Added "Cursor rules" to the Guides section for easier navigation.
    • Improved organization of the "Guides & examples" dropdown by adjusting page order and grouping.
    • Removed redundant "Cursor rules" section from the introduction guide.

Copy link

changeset-bot bot commented Apr 22, 2025

⚠️ No Changeset found

Latest commit: b088adb

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link
Contributor

coderabbitai bot commented Apr 22, 2025

Walkthrough

This update introduces a new documentation guide on using Cursor rules with Trigger.dev, explaining how to integrate and utilize these rules for task writing within the Cursor AI coding editor. The documentation navigation structure is updated to include the new guide under the "Guides" section, and the order of some existing pages is adjusted. Additionally, the introduction guide is revised to reference the new Cursor rules guide and removes a now-redundant section about Cursor rules.

Changes

File(s) Change Summary
docs/docs.json Updated navigation: reordered "AI Agents" pages and added "guides/cursor-rules" as a new guide entry.
docs/guides/cursor-rules.mdx Added a new guide detailing how to use Cursor rules with Trigger.dev, including installation, usage, and tips.
docs/guides/introduction.mdx Added Cursor rules to the Guides table and removed the old standalone Cursor rules section.

Possibly related PRs

Suggested reviewers

  • nicktrn

Poem

In the warren of docs, a new guide appears,
Cursor rules for bunnies with coding careers!
With tips and a table, and a helpful how-to,
Now writing tasks is much easier to do.
Hop through the guides, let your knowledge unfurl—
Trigger.dev and Cursor, a bright bunny world!
🐇✨


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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

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: 0

🧹 Nitpick comments (2)
docs/guides/cursor-rules.mdx (2)

49-49: Fix verb spelling in guidance
The term “roll-back” should be the verb phrase “roll back” in this context.

- so you can roll-back if something changes unexpectedly.
+ so you can roll back if something changes unexpectedly.
🧰 Tools
🪛 LanguageTool

[grammar] ~49-~49: The word “roll-back” is a noun. The verb is spelled with a space.
Context: ...ab**, and commit frequently, so you can roll-back if something changes unexpectedly. Curs...

(NOUN_VERB_CONFUSION)


[style] ~49-~49: Consider shortening or rephrasing this to strengthen your wording.
Context: ...ething changes unexpectedly. Cursor can make changes to multiple files at once, so it's best to...

(MAKE_CHANGES)


49-51: Consider rephrasing for conciseness
The sentence on commit frequency is a bit verbose. Tightening it will improve readability.

- Cursor can make changes to multiple files at once, so it's best to commit often to keep track of all your changes.
+ Cursor can modify multiple files at once; commit frequently to track changes clearly.
🧰 Tools
🪛 LanguageTool

[grammar] ~49-~49: The word “roll-back” is a noun. The verb is spelled with a space.
Context: ...ab**, and commit frequently, so you can roll-back if something changes unexpectedly. Curs...

(NOUN_VERB_CONFUSION)


[style] ~49-~49: Consider shortening or rephrasing this to strengthen your wording.
Context: ...ething changes unexpectedly. Cursor can make changes to multiple files at once, so it's best to...

(MAKE_CHANGES)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2c19693 and b088adb.

📒 Files selected for processing (3)
  • docs/docs.json (1 hunks)
  • docs/guides/cursor-rules.mdx (1 hunks)
  • docs/guides/introduction.mdx (1 hunks)
🧰 Additional context used
🪛 LanguageTool
docs/guides/cursor-rules.mdx

[grammar] ~49-~49: The word “roll-back” is a noun. The verb is spelled with a space.
Context: ...ab**, and commit frequently, so you can roll-back if something changes unexpectedly. Curs...

(NOUN_VERB_CONFUSION)


[style] ~49-~49: Consider shortening or rephrasing this to strengthen your wording.
Context: ...ething changes unexpectedly. Cursor can make changes to multiple files at once, so it's best to...

(MAKE_CHANGES)

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Analyze (javascript-typescript)
🔇 Additional comments (3)
docs/docs.json (2)

275-276: AI Agents pages reordered as intended
The entries for "guides/ai-agents/translate-and-refine" and "guides/ai-agents/verify-news-article" have been swapped to reflect the updated guide sequence.


279-279: Inserted new Cursor rules guide
The "guides/cursor-rules" entry is correctly added within the "Guides" group in docs.json, ensuring the new guide will appear in the site navigation.

docs/guides/introduction.mdx (1)

28-30: Add Cursor rules entry to Guides table
The new [Cursor rules](/guides/cursor-rules) row has been inserted into the Guides table. Verify that the description accurately represents the guide’s content.

@D-K-P D-K-P merged commit c0172d4 into main Apr 22, 2025
7 checks passed
@D-K-P D-K-P deleted the docs/using-cursor branch April 22, 2025 14:23
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.

2 participants