-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy path.cursorrules
More file actions
32 lines (24 loc) · 1.14 KB
/
.cursorrules
File metadata and controls
32 lines (24 loc) · 1.14 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
# Cursor Agent Rules
Follow these patterns for Cursor IDE integrations.
## Tool Usage
- Use cursor.extensions.* APIs for integration
- Register hooks in extension manifest
- Activate on workbench ready
## Agent Pattern
- Load agents from agents/
- Initialize on startup
## Semantic Code Search
Your editor uses **semantic code search** to understand your intent, not just syntax patterns.
### How It Works
- **Intent-based**: Describe what you're looking for in plain language
- "Find authentication validation" → locates auth checks, guards, permission logic
- "Where is database initialization?" → finds connection setup, migrations, schemas
- "Show error handling patterns" → discovers try/catch patterns, error boundaries
- **NOT syntax-based**: Unlike regex patterns, semantic search understands meaning across files
- **Cross-file understanding**: Finds related code patterns regardless of implementation details
### When to Use Code Search
- Exploring unfamiliar codebases
- Finding similar patterns you've seen before
- Understanding how components integrate
- Locating where features are implemented
- Discovering related code sections