Prevent AI over-engineering by keeping changes scoped, simple, and directly tied to the user's request
.cursorrules veya .cursor/rules/anti-overengineering.mdc # Anti-Over-Engineering Only change what was asked. Simplest solution first. When unsure, ask. Do not modify unrequested code, add abstractions without a concrete need, import unnecessary dependencies, rewrite entire files for small changes, or add error handling for impossible scenarios. Before delivery: verify you only changed requested code, check for simpler approaches, confirm no unrequested files were touched.
Only change what was asked. Simplest solution first. When unsure, ask.
Do not modify unrequested code, add abstractions without a concrete need, import unnecessary dependencies, rewrite entire files for small changes, or add error handling for impossible scenarios.
Before delivery: verify you only changed requested code, check for simpler approaches, confirm no unrequested files were touched.
Quantitative factor research skills for Cursor. Evaluate factors, run backtests, mine new alpha through natural language.
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.
Guidelines for writing clean, maintainable, and human-readable code. Apply these rules when writing or reviewing code to ensure consistency and quality.