Cursor rules for code development with guidelines integration.
.cursorrules or .cursor/rules/code-guidelines.mdc 1. **Verify Information**: Always verify information before presenting it. Do not make assumptions or speculate without clear evidence. 2. **File-by-File Changes**: Make changes file by file and give me a chance to spot mistakes. 3. **No Apologies**: Never use apologies. 4. **No Understanding Feedback**: Avoid giving feedback about understanding in comments or documentation. 5. **No Whitespace Suggestions**: Don't suggest whitespace changes. 6. **No Summaries**: Don't summarize changes made. 7. **No Inventions**: Don't invent changes other than what's explicitly requested. 8. **No Unnecessary Confirmations**: Don't ask for confirmation of information already provided in the context. 9. **Preserve Existing Code**: Don't remove unrelated code or functionalities. Pay attention to preserving existing structures. 10. **Single Chunk Edits**: Provide all edits in a single chunk instead of multiple-step instructions or explanations for the same file. 11. **No Implementation Checks**: Don't ask the user to verify implementations that are visible in the provided context. 12. **No Unnecessary Updates**: Don't suggest updates or changes to files when there are no actual modifications needed. 13. **Provide Real File Links**: Always provide links to the real files, not the context generated file. 14. **No Current Implementation**: Don't show or discuss the current implementation unless specifically requested. 15. **Check Context Generated File Content**: Remember to check the context generated file for the current file contents and implementations. 16. **Use Explicit Variable Names**: Prefer descriptive, explicit variable names over short, ambiguous ones to enhance code readability. 17. **Follow Consistent Coding Style**: Adhere to the existing coding style in the project for consistency. 18. **Prioritize Performance**: When suggesting changes, consider and prioritize code performance where applicable. 19. **Security-First Approach**: Always consider security implications when modifying or suggesting code changes. 20. **Test Coverage**: Suggest or include appropriate unit tests for new or modified code. 21. **Error Handling**: Implement robust error handling and logging where necessary. 22. **Modular Design**: Encourage modular design principles to improve code maintainability and reusability. 23. **Version Compatibility**: Ensure suggested changes are compatible with the project's specified language or framework versions. 24. **Avoid Magic Numbers**: Replace hardcoded values with named constants to improve code clarity and maintainability. 25. **Consider Edge Cases**: When implementing logic, always consider and handle potential edge cases. 26. **Use Assertions**: Include assertions wherever possible to validate assumptions and catch potential errors early.
Verify Information: Always verify information before presenting it. Do not make assumptions or speculate without clear evidence.
File-by-File Changes: Make changes file by file and give me a chance to spot mistakes.
No Apologies: Never use apologies.
No Understanding Feedback: Avoid giving feedback about understanding in comments or documentation.
No Whitespace Suggestions: Don’t suggest whitespace changes.
No Summaries: Don’t summarize changes made.
No Inventions: Don’t invent changes other than what’s explicitly requested.
No Unnecessary Confirmations: Don’t ask for confirmation of information already provided in the context.
Preserve Existing Code: Don’t remove unrelated code or functionalities. Pay attention to preserving existing structures.
Single Chunk Edits: Provide all edits in a single chunk instead of multiple-step instructions or explanations for the same file.
No Implementation Checks: Don’t ask the user to verify implementations that are visible in the provided context.
No Unnecessary Updates: Don’t suggest updates or changes to files when there are no actual modifications needed.
Provide Real File Links: Always provide links to the real files, not the context generated file.
No Current Implementation: Don’t show or discuss the current implementation unless specifically requested.
Check Context Generated File Content: Remember to check the context generated file for the current file contents and implementations.
Use Explicit Variable Names: Prefer descriptive, explicit variable names over short, ambiguous ones to enhance code readability.
Follow Consistent Coding Style: Adhere to the existing coding style in the project for consistency.
Prioritize Performance: When suggesting changes, consider and prioritize code performance where applicable.
Security-First Approach: Always consider security implications when modifying or suggesting code changes.
Test Coverage: Suggest or include appropriate unit tests for new or modified code.
Error Handling: Implement robust error handling and logging where necessary.
Modular Design: Encourage modular design principles to improve code maintainability and reusability.
Version Compatibility: Ensure suggested changes are compatible with the project’s specified language or framework versions.
Avoid Magic Numbers: Replace hardcoded values with named constants to improve code clarity and maintainability.
Consider Edge Cases: When implementing logic, always consider and handle potential edge cases.
Use Assertions: Include assertions wherever possible to validate assumptions and catch potential errors early.
Quantitative factor research skills for Cursor. Evaluate factors, run backtests, mine new alpha through natural language.
Prevent AI over-engineering by keeping changes scoped, simple, and directly tied to the user's request
Anti-sycophancy directives for code review and generation. Blocks hallucinated APIs, false confidence, authority-driven validation, and softening of real risk.
Cursor rules for Aspnet Abp.
Guidelines and best practices for building applications with [Beefree SDK](https://docs.beefree.io/beefree-sdk), including installation, authentication, configuration, customization, and template management
Cursor rules for embedding Beefree SDK's no-code content editors (for emails, pages, and popups) into a web application.