.cursorrules (deprecated)

11. **Verify Information**: Always verify information before presenting it. Do not make assumptions or speculate without clear evidence.
2 
32. **File-by-File Changes**: Make changes file by file and give me a chance to spot mistakes.
4 
53. **No Apologies**: Never use apologies.
6 
74. **No Understanding Feedback**: Avoid giving feedback about understanding in comments or documentation.
8 
95. **No Whitespace Suggestions**: Don't suggest whitespace changes.
10 
116. **No Summaries**: Don't summarize changes made.
12 
137. **No Inventions**: Don't invent changes other than what's explicitly requested.
14 
158. **No Unnecessary Confirmations**: Don't ask for confirmation of information already provided in the context.
16 
179. **Preserve Existing Code**: Don't remove unrelated code or functionalities. Pay attention to preserving existing structures.
18 
1910. **Single Chunk Edits**: Provide all edits in a single chunk instead of multiple-step instructions or explanations for the same file.
20 
2111. **No Implementation Checks**: Don't ask the user to verify implementations that are visible in the provided context.
22 
2312. **No Unnecessary Updates**: Don't suggest updates or changes to files when there are no actual modifications needed.
24 
2513. **Provide Real File Links**: Always provide links to the real files, not the context generated file.
26 
2714. **No Current Implementation**: Don't show or discuss the current implementation unless specifically requested.
28 
2915. **Check Context Generated File Content**: Remember to check the context generated file for the current file contents and implementations.
30 
3116. **Use Explicit Variable Names**: Prefer descriptive, explicit variable names over short, ambiguous ones to enhance code readability.
32 
3317. **Follow Consistent Coding Style**: Adhere to the existing coding style in the project for consistency.
34 
3518. **Prioritize Performance**: When suggesting changes, consider and prioritize code performance where applicable.
36 
3719. **Security-First Approach**: Always consider security implications when modifying or suggesting code changes.
38 
3920. **Test Coverage**: Suggest or include appropriate unit tests for new or modified code.
40 
4121. **Error Handling**: Implement robust error handling and logging where necessary.
42 
4322. **Modular Design**: Encourage modular design principles to improve code maintainability and reusability.
44 
4523. **Version Compatibility**: Ensure suggested changes are compatible with the project's specified language or framework versions.
46 
4724. **Avoid Magic Numbers**: Replace hardcoded values with named constants to improve code clarity and maintainability.
48 
4925. **Consider Edge Cases**: When implementing logic, always consider and handle potential edge cases.
50 
5126. **Use Assertions**: Include assertions wherever possible to validate assumptions and catch potential errors early.
52 
53