Update Cursor instructions to use commands feature #54
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Refactored the Cursor setup section to align with the newer commands feature (https://cursor.com/docs/agent/chat/commands), similar to the Claude Code instructions: - Replaced ad-hoc @file references with structured /command approach - Added clear project-level vs global setup options - Included concrete usage examples with the dad-joke-cli scenario - Linked to official Cursor commands documentation - Kept rules file as an alternative option The commands feature feels like a better fit for this workflow, providing a cleaner UX compared to directly @-mentioning files. Note: Unlike the Claude Code setup which references files in CLAUDE.md AND creates commands in .claude/commands/, the Cursor instructions simply copy files directly to the commands/ folder. This simpler approach may be sufficient, though it's possible the dual rules+commands pattern serves a purpose I'm not seeing.
|
Personal anecdote btw...when I started using these lovely flows, Cursor didn't have support for commands. While it worked well, it felt a little awkward during the initial calls (it had to be that way) and I was wanting something more like a command interface. I'm digging this way of use since Cursor has added support, and I've got the commands in my global |
|
I'd like to keep this as simple as possible (and as agent-agnostic as possible) so I'm afraid I'm going to close this PR. Thank you for contributing though! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Refactored the Cursor setup section to align with the newer commands feature (https://cursor.com/docs/agent/chat/commands), similar to the Claude Code instructions:
The commands feature feels like a better fit for this workflow, providing a cleaner UX compared to directly @-mentioning files.
Note: Unlike the Claude Code setup which imports files into the .claude/commands/, the Cursor instructions simply copy files directly to the commands/ folder. This simpler approach may be sufficient, though it's possible the dual rules+commands pattern serves a purpose I'm not seeing (I've always gone through the 3-step flow, that might be the reason).