anti overengineering
via PatrickJS/awesome-cursorrules
Keep changes scoped and simple—modify only what was asked, nothing more.
What is anti overengineering?
This rule prevents AI from over-engineering solutions by enforcing minimal, focused changes tied directly to the user's request. Use it to avoid unnecessary abstractions, extra dependencies, file rewrites, or defensive code that wasn't requested.
- Restricts changes to only the code explicitly requested
- Favors simplest solution first, deferring complexity until concrete need arises
- Prevents adding abstractions, dependencies, or error handling that weren't asked for
- Avoids rewriting entire files for small, localized changes
- Includes pre-delivery checklist: verify scope, confirm simplicity, check for unintended file modifications
Applies to
File patterns this rule matches.
Rule definition (reference)
Source of truth, from the repository.
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.
Related rules
Enforce technical rigor in code review and generation by blocking hallucinated APIs, false confidence, and authority-driven validation.
Turn-based ASCII simulation where AI nations compete for resources on a procedurally generated 100x100 grid.
Expert guidance for ABP Framework development with C#, ASP.NET Core, and Entity Framework Core.
Astro + TypeScript development rules with conventional commits and TailwindCSS styling guidelines.
AutoML and hyperparameter optimization rules for Python ML projects using Ray Tune, Optuna, PyCaret, and time-series libraries
Guidelines for integrating Beefree SDK email editor into web applications with authentication, configuration, and template management.