dev
rules
.
directory
//
A curated collection of rules for
Cursor
,
Claude
, and other AI coding assistants
search
(
)
//
filter
(
category
)
[
API
]
[
Architecture
]
[
Assistant Behavior
]
[
Backend
]
[
Best Practices
]
[
CSS
]
[
Code Quality
]
[
Communication
]
[
Configuration
]
[
Design Patterns
]
[
DevOps
]
[
Documentation
]
[
Error Handling
]
[
Frontend
]
[
Git
]
[
Go
]
[
JavaScript
]
[
Naming
]
[
Next.js
]
[
Python
]
[
REST
]
[
React
]
[
SEO
]
[
Security
]
[
Testing
]
[
TypeScript
]
[
Workflow
]
Ask Before Large Refactors
//
Always asks clarifying questions before making significant code changes
Assistant Behavior
Best Practices
Stay Within Task Scope
//
Only changes files and code directly related to the current task
Assistant Behavior
Best Practices
Propose Options, Don't Pick Arbitrarily
//
Presents multiple valid approaches instead of choosing one without user input
Assistant Behavior
Communication
Avoid eval() and exec() Patterns
//
Prevents dangerous code execution patterns that create security vulnerabilities
Security
Best Practices
Never Break Public APIs
//
Never changes public APIs without explicit migration plan and approval
Assistant Behavior
API
Best Practices
Never Invent Facts or Dependencies
//
Always admits uncertainty instead of making up information about code or dependencies
Assistant Behavior
Best Practices
Never Log Secrets or Tokens
//
Prevents logging of sensitive data like passwords, tokens, and API keys
Security
Best Practices
Propose Minimal Diffs
//
Suggests minimal, targeted changes instead of rewriting entire files
Assistant Behavior
Code Quality
Explain Assumptions When Context Missing
//
Explicitly states assumptions and asks for clarification when context is unclear
Assistant Behavior
Communication
Never Execute Unsafe Shell Commands
//
Prevents suggesting dangerous shell commands that could harm the system
Security
Best Practices
Previous
1
2
3
Next