Cursor User Rules Configuration
# Cursor User Rules Configuration
Expert-level AI coding assistant rules for Cursor IDE that transform the AI into a senior engineer and meticulous coding partner.
## 📋 **Overview**
This configuration file contains comprehensive rules that guide Cursor's AI assistant to behave like an expert senior software engineer, providing structured, systematic, and high-quality assistance for software development tasks.
## 📁 **Files**
- **[template.md](template.md)** - Complete Cursor user rules configuration
## 🎯 **What This Configuration Provides**
### **Expert Persona**
- Configures AI as an expert senior software engineer
- Emphasizes accuracy, robustness, and maintainability
- Focuses on understanding context before acting
### **Structured Workflow**
- **Context Synthesis** - Systematic review of project state and requirements
- **Detailed Planning** - Step-by-step execution plans before implementation
- **Incremental Execution** - One change at a time with verification
- **Quality Assurance** - Built-in code review and best practices
### **Code Quality Standards**
- Comprehensive type hinting and documentation requirements
- Robust error handling for all I/O and API operations
- Adherence to language-specific best practices
- Self-verification and review processes
## 🚀 **How to Use**
### **Installation**
1. Copy the contents of `template.md`
2. Paste into your Cursor user rules configuration
3. Customize project-specific elements as needed
### **Customization**
The template includes sections for:
- **Project-specific patterns** - Adapt to your codebase conventions
- **Technology stack requirements** - Configure for your frameworks and tools
- **Quality standards** - Adjust requirements for your development standards
### **Team Deployment**
1. Share the configuration across your team
2. Ensure consistent application of rules
3. Document any team-specific customizations
## 🔧 **Key Features**
### **Context Synthesis Protocol**
Every interaction begins with:
- Review of conversation history and project state
- Analysis of current files and recent changes
- Understanding of goals and constraints
### **Structured Planning Requirement**
All non-trivial changes require:
- Detailed execution plan with numbered steps
- Clear goal statement and file identification
- Verification checkpoints throughout implementation
### **Quality Assurance Framework**
Built-in requirements for:
- Comprehensive error handling
- Clear documentation and comments
- Language-specific best practices
- Self-review before presenting solutions
### **Incremental Development**
Enforces systematic approach:
- One logical change at a time
- Explicit confirmation before proceeding
- Verification after each step
## 💡 **Benefits**
**For Developers:**
- Consistent, high-quality AI assistance
- Reduced cognitive load through systematic workflows
- Better code quality through built-in best practices
**For Teams:**
- Standardized AI behavior across team members
- Consistent code patterns and quality
- Improved collaboration through shared methodologies
**For Projects:**
- Maintained architectural integrity
- Comprehensive documentation of changes
- Reduced technical debt through systematic development
## 🎨 **Customization Examples**
**For Python Projects:**when to use it
Community prompt sourced from the open-source GitHub repo belumume/prompt-craft (MIT). A "Cursor User Rules Configuration" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
codingcommunitydeveloper
source
belumume/prompt-craft · MIT
more in Coding
Coding✓ tested
Senior code review (strict mode)
senior staff engineer running a merciless but fair review
Coding✓ tested
Debug by hypothesis, not by guessing
debugging partner who forms theories before touching code
Coding✓ tested
Generate tests from described behavior
test engineer who writes tests that would actually catch regressions