optimize dry solid principles cursorrules prompt f
via PatrickJS/awesome-cursorrules
DRY and SOLID principles integration for optimization development in Cursor.
What is optimize dry solid principles cursorrules prompt f?
This rule guides code generation and refactoring with emphasis on DRY (Don't Repeat Yourself) and SOLID principles. Use it when you want the AI assistant to prioritize code quality, maintainability, and semantic clarity while respecting existing architecture choices defined in pyproject.toml.
- Enforces DRY and SOLID principles in code generation and refactoring
- Requires semantic naming and clear abstractions
- Includes file context in code blocks with surrounding lines for clarity
- Respects existing architecture choices from pyproject.toml
- Prompts for clarification before implementation when needed
- Provides structured guidance across communication, code quality, paradigms, and naming
Applies to
File patterns this rule matches.
Rule definition (reference)
Source of truth, from the repository.
Communication and Problem-Solving:
Code Quality and Best Practices:
Paradigms and Principles:
Semantic Naming and Abstractions:
Platform Thinking:
Response Format:
Handling Uncertainty and Limitations:
When outputting code blocks, include a # or // file name comment prior to the block, with a few lines before and after the modification. This helps the user identify where to make changes.
Stick to the current architecture choices located in pyproject.toml unless the user suggests a new method or module.
If you need clarification on any part of the task, ask for more information before proceeding with the implementation.
Related rules
Expert guidance for writing clear, optimized Rell blockchain code on Chromia.
Expert guidance for pandas, scikit-learn, and Jupyter-based data analysis workflows.
PHP and Telegram Bot API development with Plasticode framework guidance.
Playwright accessibility testing with axe-core for WCAG 2.1 AA compliance
Playwright API testing with TypeScript support and pw-api-plugin integration.
Playwright testing with defect tracking, case ID tagging, and qa-shadow-report integration.