Cursor rule

1---
2description: Code Patterns & Guidelines
3globs:
4alwaysApply: true
5---
6 
7# Cursor AI Assistant Rules
8 
9## Assistant Behavior
10 
11- Be terse and direct in responses
12- Ask clarifying questions before implementing complex features
13- Anticipate needs and suggest improvements proactively
14- Focus on high-quality, production-ready code
15- Use analogies when explaining complex concepts
16 
17## Code Generation Principles
18 
19### Quality Standards
20- Generate code that could ship to production
21- Follow established patterns in the codebase
22- Maintain consistency with existing architecture
23- Every piece of code should be testable
24- Documentation is not optional
25 
26### Style Guidelines
27- Respect .prettierrc and linting configurations
28- Prefer clarity over cleverness
29- Use descriptive names that reveal intent
30- Keep line lengths reasonable
31- Consistent indentation and formatting
32 
33### Architecture Focus
34- Think in systems, not just functions
35- Consider scalability implications
36- Design for maintainability
37- Separate concerns appropriately
38- Make dependencies explicit
39 
40## Project Awareness
41 
42### Context Loading
43Always check for `.cursor/PROJECT_CONTEXT.md` which contains:
44- Current architectural patterns
45- Technology stack decisions
46- Team conventions and preferences
47- Recent design decisions
48- Performance considerations
49- Known technical debt
50 
51### File Organization
52- Follow existing project structure
53- Keep related code together
54- Use standard naming conventions
55- Maintain clear module boundaries
56 
57## Code Patterns
58 
59### Error Handling
60- Fail fast with clear messages
61- Use appropriate error types
62- Handle errors at the right level
63- Provide actionable error messages
64- Log errors appropriately
65 
66### Testing Approach
67- Write tests alongside implementation
68- Test edge cases explicitly
69- Use descriptive test names
70- Keep tests simple and focused
71- Mock external dependencies
72 
73### Documentation
74- Document why, not what
75- Include examples for complex APIs
76- Keep docs in sync with code
77- Use consistent documentation format
78- Document assumptions and constraints
79 
80## Language-Specific Rules
81 
82### Ruby on Rails
83Refer to `rails-rules.md` for:
84- Rails conventions and patterns
85- ActiveRecord best practices
86- Testing with RSpec
87- API design guidelines
88 
89 
90## Performance & Security
91 
92### Performance
93- Consider algorithmic complexity
94- Profile before optimizing
95- Cache strategically
96- Use appropriate data structures
97- Avoid premature optimization
98 
99### Security
100- Sanitize all inputs
101- Use secure defaults
102- Follow OWASP guidelines
103- Never expose sensitive data
104- Keep dependencies updated
105 
106## AI Assistant Guidelines
107 
108### When Generating Code
1091. Check `PROJECT_CONTEXT.md` first
1102. Follow existing patterns in codebase
1113. Include appropriate tests
1124. Add necessary documentation
1135. Consider edge cases
114 
115### When Explaining Concepts
116- Use clear analogies
117- Provide concrete examples
118- Link to authoritative sources
119- Keep explanations concise
120- Focus on practical application
121 
122### When Suggesting Improvements
123- Consider the bigger picture
124- Propose incremental changes
125- Explain trade-offs clearly
126- Respect existing constraints
127- Suggest best-in-class solutions
128 
129---
130 
131*Note: Language-specific and PROJECT_CONTEXT rules override these defaults.*
132