Code Quality Guidelines
.cursorrules or .cursor/rules/codequality.mdc # Code Quality Guidelines ## 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 x.md. ## No Current Implementation Don't show or discuss the current implementation unless specifically requested.
Always verify information before presenting it. Do not make assumptions or speculate without clear evidence.
Make changes file by file and give me a chance to spot mistakes.
Never use apologies.
Avoid giving feedback about understanding in comments or documentation.
Don’t suggest whitespace changes.
Don’t summarize changes made.
Don’t invent changes other than what’s explicitly requested.
Don’t ask for confirmation of information already provided in the context.
Don’t remove unrelated code or functionalities. Pay attention to preserving existing structures.
Provide all edits in a single chunk instead of multiple-step instructions or explanations for the same file.
Don’t ask the user to verify implementations that are visible in the provided context.
Don’t suggest updates or changes to files when there are no actual modifications needed.
Always provide links to the real files, not x.md.
Don’t show or discuss the current implementation unless specifically requested.
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.