From d73fc0c007d4f0abca6e6a44e1e9fbb5cb47674c Mon Sep 17 00:00:00 2001
From: Haim Cohen <haim1979@gmail.com>
Date: Thu, 12 Jun 2025 10:21:57 +0300
Subject: [PATCH 01/11] =?UTF-8?q?add=20security-devsecops-ssdls-appsec.mdc?=
 =?UTF-8?q?.=20=20is=20a=20practical=20template=20for=20a=20Cursor=20rule?=
 =?UTF-8?q?=20that=20integrates=20DevSecOps,=20Secure=20Software=20Develop?=
 =?UTF-8?q?ment=20Lifecycle=20(SSDLC),=20and=20Application=20Security=20(A?=
 =?UTF-8?q?ppSec)=20best=20practices.=20This=20rule=20is=20intended=20for?=
 =?UTF-8?q?=20use=20in=20a=20.cursor/rules/security-devsecops-ssdls-appsec?=
 =?UTF-8?q?.mdc=20file=20and=20can=20be=20adapted=20to=20your=20project?=
 =?UTF-8?q?=E2=80=99s=20needs.?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 rules/security-devsecops-ssdls-appsec.mdc | 48 +++++++++++++++++++++++
 1 file changed, 48 insertions(+)
 create mode 100644 rules/security-devsecops-ssdls-appsec.mdc

diff --git a/rules/security-devsecops-ssdls-appsec.mdc b/rules/security-devsecops-ssdls-appsec.mdc
new file mode 100644
index 00000000..420458c3
--- /dev/null
+++ b/rules/security-devsecops-ssdls-appsec.mdc
@@ -0,0 +1,48 @@
+---
+description: Enforce DevSecOps, SSDLC, and AppSec best practices for all code generated in this project. 
+globs: ["**/*.py", "**/*.js", "**/*.ts", "**/*.go", "**/*.java", "**/*.rb", "**/*.php", "**/*.cs", "**/*.sh"]
+alwaysApply: true
+write by Haim Cohen [https://www.linkedin.com/in/haimc/]
+---
+
+# DevSecOps + SSDLC + AppSec Cursor Rule
+
+## General Security Principles
+- Never hardcode secrets, credentials, or API keys. Use environment variables or secure vaults for sensitive data.
+- Prohibit the inclusion of `.env`, secret config files, or unknown tokens in source control.
+- Never log sensitive data, secrets, or session tokens in application logs.
+- Validate and sanitize all user input. Escape output in HTML, JS, and SQL contexts.
+- Avoid unsafe functions such as `exec`, `eval`, or similar dynamic code execution.
+
+## Database Security
+- Use parameterized queries or ORM for all database access. Do not use string concatenation for query building.
+- Ensure database users have the least privilege required for their tasks.
+- Regularly review and update database access policies.
+
+## Dependency Management
+- Only use packages from verified sources.
+- Do not add new dependencies without explicit approval and security review.
+- Regularly update dependencies and scan for known vulnerabilities (SCA).
+
+## Authentication & Authorization
+- Use secure authentication frameworks; never implement custom authentication.
+- Store passwords using strong, salted hashes (e.g., Argon2, bcrypt).
+- Implement Role-Based Access Control (RBAC) for sensitive operations.
+- Enforce the principle of least privilege for APIs and UI actions.
+
+## Secure SDLC Practices
+- Integrate Static Application Security Testing (SAST) and Software Composition Analysis (SCA) into the CI pipeline.
+- Scan all code for secrets before merging (Secret Scanning).
+- Use Infrastructure as Code (IaC) scanning for all infrastructure code.
+- Integrate Dynamic Application Security Testing (DAST) in the CD pipeline for deployed applications.
+- Enforce Policy as Code (PaC) for automated, version-controlled security policies.
+
+## Monitoring & Feedback
+- Enable continuous vulnerability monitoring and alerting.
+- Integrate Runtime Application Self-Protection (RASP) and Web Application Firewall (WAF) as appropriate.
+- Encourage regular vulnerability assessments and penetration testing.
+- Maintain a feedback loop to update rules and prompts based on recurring vulnerabilities.
+
+## Compliance & Documentation
+- Align with industry standards (e.g., OWASP Top 10, NIST, ISO 27001).
+- Document all security controls and decisions for auditability.

From 7ba86bae72a06e40103c1cacf5b1c0c242d2bcf6 Mon Sep 17 00:00:00 2001
From: Haim Cohen <haim1979@gmail.com>
Date: Thu, 12 Jun 2025 19:57:23 +0300
Subject: [PATCH 02/11] Add DevOps and Admin rules for various roles and
 scripts

---
 README.md                                     | 33 ++++----
 .../network/network-engineer.cursorrules      | 72 +++++++++++++++++
 .../admin/system/system-engineer.cursorrules  | 72 +++++++++++++++++
 rules/admin/vmware/vmware-admin.cursorrules   | 72 +++++++++++++++++
 rules/devops/devops-engineer.cursorrules      | 79 ++++++++++++++++++
 rules/scripts/posix/bash-script.cursorrules   | 79 ++++++++++++++++++
 rules/scripts/posix/zsh-script.cursorrules    | 79 ++++++++++++++++++
 .../powercli/powercli-script.cursorrules      | 79 ++++++++++++++++++
 .../powershell/powershell-script.cursorrules  | 80 +++++++++++++++++++
 9 files changed, 630 insertions(+), 15 deletions(-)
 create mode 100644 rules/admin/network/network-engineer.cursorrules
 create mode 100644 rules/admin/system/system-engineer.cursorrules
 create mode 100644 rules/admin/vmware/vmware-admin.cursorrules
 create mode 100644 rules/devops/devops-engineer.cursorrules
 create mode 100644 rules/scripts/posix/bash-script.cursorrules
 create mode 100644 rules/scripts/posix/zsh-script.cursorrules
 create mode 100644 rules/scripts/powercli/powercli-script.cursorrules
 create mode 100644 rules/scripts/powershell/powershell-script.cursorrules

diff --git a/README.md b/README.md
index 6cd10212..4773a823 100644
--- a/README.md
+++ b/README.md
@@ -12,21 +12,7 @@ A curated list of awesome .cursorrules files for enhancing your Cursor AI experi
 
 ## Why .cursorrules?
 
-`.cursorrules` is a powerful feature in Cursor AI that allows developers to define project-specific instructions for the AI. Here's why you might want to use it:
-
-1. **Customized AI Behavior**: `.cursorrules` files help tailor the AI's responses to your project's specific needs, ensuring more relevant and accurate code suggestions.
-
-2. **Consistency**: By defining coding standards and best practices in your `.cursorrules` file, you can ensure that the AI generates code that aligns with your project's style guidelines.
-
-3. **Context Awareness**: You can provide the AI with important context about your project, such as commonly used methods, architectural decisions, or specific libraries, leading to more informed code generation.
-
-4. **Improved Productivity**: With well-defined rules, the AI can generate code that requires less manual editing, speeding up your development process.
-
-5. **Team Alignment**: For team projects, a shared `.cursorrules` file ensures that all team members receive consistent AI assistance, promoting cohesion in coding practices.
-
-6. **Project-Specific Knowledge**: You can include information about your project's structure, dependencies, or unique requirements, helping the AI to provide more accurate and relevant suggestions.
-
-By creating a `.cursorrules` file in your project's root directory, you can leverage these benefits and enhance your coding experience with Cursor AI.
+.cursorrules files are repository-specific "Rules for AI" that help Cursor AI understand your project's context, coding standards, and best practices. These rules are automatically appended to your global "Rules for AI" settings when working in a repository.
 
 ## Contents
 
@@ -44,6 +30,7 @@ By creating a `.cursorrules` file in your project's root directory, you can leve
     - [Hosting and Deployments](#hosting-and-deployments)
     - [Build Tools and Development](#build-tools-and-development)
     - [Language-Specific](#language-specific)
+    - [DevOps and Administration](#devops-and-administration)
     - [Other](#other)
     - [Utilities](#utilities)
   - [Directories](#directories)
@@ -211,6 +198,22 @@ By creating a `.cursorrules` file in your project's root directory, you can leve
 - [TypeScript (Clasp App Script)](./rules/typescript-clasp-cursorrules-prompt-file/.cursorrules)
 - [C++ Programming Guidelines](./rules/cpp-programming-guidelines-cursorrules-prompt-file/.cursorrules)
 
+### DevOps and Administration
+
+#### DevOps
+- [DevOps Engineer](./rules/devops/devops-engineer.cursorrules) - Best practices for DevOps engineering tasks
+
+#### Scripts
+- [PowerShell](./rules/scripts/powershell/powershell-script.cursorrules) - Best practices for PowerShell scripting
+- [PowerCLI](./rules/scripts/powercli/powercli-script.cursorrules) - Best practices for PowerCLI scripting
+- [POSIX (Bash)](./rules/scripts/posix/bash-script.cursorrules) - Best practices for POSIX bash scripting
+- [POSIX (Zsh)](./rules/scripts/posix/zsh-script.cursorrules) - Best practices for POSIX zsh scripting
+
+#### Administration
+- [VMware Admin](./rules/admin/vmware/vmware-admin.cursorrules) - Best practices for VMware administration
+- [Network Engineer](./rules/admin/network/network-engineer.cursorrules) - Best practices for Network Engineering
+- [System Engineer](./rules/admin/system/system-engineer.cursorrules) - Best practices for System Engineering
+
 ### Other
 
 - [ASCII Simulation Game](./rules/ascii-simulation-game-cursorrules-prompt-file/.cursorrules)
diff --git a/rules/admin/network/network-engineer.cursorrules b/rules/admin/network/network-engineer.cursorrules
new file mode 100644
index 00000000..a824e4b3
--- /dev/null
+++ b/rules/admin/network/network-engineer.cursorrules
@@ -0,0 +1,72 @@
+// Network Engineering Best Practices
+// This file contains rules and guidelines for Network Engineering
+
+// Network Design
+- Use proper network architecture
+- Implement proper network segmentation
+- Use proper network redundancy
+- Implement proper network security
+- Use proper network documentation
+
+// Security
+- Use proper access control
+- Implement proper firewall rules
+- Use proper encryption
+- Implement proper VPN configuration
+- Use proper security policies
+
+// Performance
+- Use proper bandwidth management
+- Implement proper QoS policies
+- Use proper traffic shaping
+- Implement proper load balancing
+- Use proper performance monitoring
+
+// Documentation
+- Document all network configurations
+- Document all network changes
+- Document all network policies
+- Document all network incidents
+- Document all network procedures
+
+// Monitoring
+- Use proper network monitoring
+- Implement proper alerting
+- Use proper logging
+- Implement proper reporting
+- Use proper analysis
+
+// Troubleshooting
+- Use proper diagnostic tools
+- Implement proper troubleshooting procedures
+- Use proper network analysis
+- Implement proper problem resolution
+- Use proper documentation
+
+// Configuration Management
+- Use proper version control
+- Implement proper change management
+- Use proper configuration backup
+- Implement proper configuration testing
+- Use proper configuration documentation
+
+// Network Services
+- Use proper DNS configuration
+- Implement proper DHCP configuration
+- Use proper routing configuration
+- Implement proper switching configuration
+- Use proper service documentation
+
+// Best Practices
+- Use proper naming conventions
+- Implement proper procedures
+- Use proper documentation
+- Implement proper training
+- Use proper communication
+
+// Disaster Recovery
+- Implement proper backup procedures
+- Use proper recovery procedures
+- Implement proper failover procedures
+- Use proper disaster recovery testing
+- Implement proper documentation 
\ No newline at end of file
diff --git a/rules/admin/system/system-engineer.cursorrules b/rules/admin/system/system-engineer.cursorrules
new file mode 100644
index 00000000..26ca27f9
--- /dev/null
+++ b/rules/admin/system/system-engineer.cursorrules
@@ -0,0 +1,72 @@
+// System Engineering Best Practices
+// This file contains rules and guidelines for System Engineering
+
+// System Design
+- Use proper system architecture
+- Implement proper system redundancy
+- Use proper system security
+- Implement proper system documentation
+- Use proper system monitoring
+
+// Security
+- Use proper access control
+- Implement proper authentication
+- Use proper encryption
+- Implement proper security policies
+- Use proper security monitoring
+
+// Performance
+- Use proper resource management
+- Implement proper performance monitoring
+- Use proper capacity planning
+- Implement proper load balancing
+- Use proper performance tuning
+
+// Documentation
+- Document all system configurations
+- Document all system changes
+- Document all system policies
+- Document all system incidents
+- Document all system procedures
+
+// Monitoring
+- Use proper system monitoring
+- Implement proper alerting
+- Use proper logging
+- Implement proper reporting
+- Use proper analysis
+
+// Troubleshooting
+- Use proper diagnostic tools
+- Implement proper troubleshooting procedures
+- Use proper system analysis
+- Implement proper problem resolution
+- Use proper documentation
+
+// Configuration Management
+- Use proper version control
+- Implement proper change management
+- Use proper configuration backup
+- Implement proper configuration testing
+- Use proper configuration documentation
+
+// System Services
+- Use proper service configuration
+- Implement proper service monitoring
+- Use proper service documentation
+- Implement proper service recovery
+- Use proper service optimization
+
+// Best Practices
+- Use proper naming conventions
+- Implement proper procedures
+- Use proper documentation
+- Implement proper training
+- Use proper communication
+
+// Disaster Recovery
+- Implement proper backup procedures
+- Use proper recovery procedures
+- Implement proper failover procedures
+- Use proper disaster recovery testing
+- Implement proper documentation 
\ No newline at end of file
diff --git a/rules/admin/vmware/vmware-admin.cursorrules b/rules/admin/vmware/vmware-admin.cursorrules
new file mode 100644
index 00000000..497f21d1
--- /dev/null
+++ b/rules/admin/vmware/vmware-admin.cursorrules
@@ -0,0 +1,72 @@
+// VMware Administration Best Practices
+// This file contains rules and guidelines for VMware administration
+
+// VM Management
+- Use proper VM naming conventions
+- Implement proper VM templates
+- Use proper resource allocation
+- Implement proper VM backups
+- Use proper VM monitoring
+
+// Resource Management
+- Use proper resource allocation
+- Implement proper resource limits
+- Use proper resource monitoring
+- Implement proper resource cleanup
+- Use proper resource optimization
+
+// Security
+- Use proper authentication
+- Implement proper access control
+- Use proper encryption
+- Implement proper audit logging
+- Use proper security policies
+
+// Performance
+- Use proper performance monitoring
+- Implement proper resource optimization
+- Use proper capacity planning
+- Implement proper load balancing
+- Use proper performance tuning
+
+// Backup and Recovery
+- Implement proper backup strategies
+- Use proper backup scheduling
+- Implement proper recovery procedures
+- Use proper backup verification
+- Implement proper disaster recovery
+
+// Networking
+- Use proper network configuration
+- Implement proper network security
+- Use proper network monitoring
+- Implement proper network optimization
+- Use proper network documentation
+
+// Storage
+- Use proper storage configuration
+- Implement proper storage security
+- Use proper storage monitoring
+- Implement proper storage optimization
+- Use proper storage documentation
+
+// Documentation
+- Document all configurations
+- Document all procedures
+- Document all policies
+- Document all changes
+- Document all incidents
+
+// Monitoring
+- Use proper monitoring tools
+- Implement proper alerting
+- Use proper logging
+- Implement proper reporting
+- Use proper analysis
+
+// Best Practices
+- Use proper naming conventions
+- Implement proper procedures
+- Use proper documentation
+- Implement proper training
+- Use proper communication 
\ No newline at end of file
diff --git a/rules/devops/devops-engineer.cursorrules b/rules/devops/devops-engineer.cursorrules
new file mode 100644
index 00000000..3114f064
--- /dev/null
+++ b/rules/devops/devops-engineer.cursorrules
@@ -0,0 +1,79 @@
+// DevOps Engineer Best Practices
+// This file contains rules and guidelines for DevOps engineering tasks
+
+// Infrastructure as Code (IaC)
+- Use declarative configuration management tools (Terraform, Ansible, etc.)
+- Version control all infrastructure code
+- Implement infrastructure testing
+- Use modules and reusable components
+- Document infrastructure architecture
+
+// CI/CD Pipeline
+- Implement automated testing in pipelines
+- Use version control for pipeline configurations
+- Implement security scanning in CI/CD
+- Use environment-specific configurations
+- Implement rollback procedures
+
+// Monitoring and Logging
+- Implement centralized logging
+- Set up monitoring and alerting
+- Use metrics for performance tracking
+- Implement log rotation and retention policies
+- Set up dashboards for key metrics
+
+// Security
+- Implement least privilege access
+- Use secrets management
+- Regular security audits
+- Implement network security policies
+- Use secure communication protocols
+
+// Containerization
+- Use multi-stage builds
+- Implement container security scanning
+- Use container orchestration
+- Implement resource limits
+- Use container health checks
+
+// Cloud Services
+- Use cloud-native services when appropriate
+- Implement cost optimization
+- Use region-specific configurations
+- Implement disaster recovery
+- Use cloud security best practices
+
+// Automation
+- Automate repetitive tasks
+- Use configuration management
+- Implement self-healing systems
+- Use automated testing
+- Implement automated deployment
+
+// Documentation
+- Document all infrastructure changes
+- Maintain runbooks
+- Document disaster recovery procedures
+- Keep architecture diagrams updated
+- Document security procedures
+
+// Collaboration
+- Use version control for all code
+- Implement code review processes
+- Use issue tracking
+- Maintain documentation
+- Regular team communication
+
+// Performance
+- Implement performance monitoring
+- Use caching strategies
+- Optimize resource usage
+- Implement load balancing
+- Regular performance testing
+
+// Disaster Recovery
+- Implement backup strategies
+- Document recovery procedures
+- Regular disaster recovery testing
+- Implement failover procedures
+- Maintain recovery documentation 
\ No newline at end of file
diff --git a/rules/scripts/posix/bash-script.cursorrules b/rules/scripts/posix/bash-script.cursorrules
new file mode 100644
index 00000000..2d9d3e75
--- /dev/null
+++ b/rules/scripts/posix/bash-script.cursorrules
@@ -0,0 +1,79 @@
+// POSIX Bash Script Best Practices
+// This file contains rules and guidelines for POSIX bash scripting
+
+// Script Structure
+- Use proper shebang line
+- Use proper script headers
+- Implement proper error handling
+- Use proper functions
+- Use proper indentation
+
+// Naming Conventions
+- Use lowercase for variables
+- Use UPPERCASE for constants
+- Use descriptive names
+- Use proper function names
+- Follow POSIX naming conventions
+
+// Error Handling
+- Use set -e for error handling
+- Use set -u for undefined variables
+- Use set -o pipefail for pipeline errors
+- Implement proper error messages
+- Use proper exit codes
+
+// Security
+- Use proper file permissions
+- Implement proper input validation
+- Use proper quoting
+- Implement proper path handling
+- Use proper command substitution
+
+// Performance
+- Use proper command selection
+- Implement proper loop optimization
+- Use proper variable usage
+- Implement proper process management
+- Use proper resource management
+
+// Documentation
+- Use proper comments
+- Document all functions
+- Document all parameters
+- Document all examples
+- Document all requirements
+
+// Testing
+- Test all functions
+- Test all parameters
+- Test all error conditions
+- Test all edge cases
+- Implement proper test cases
+
+// Functions
+- Use proper function structure
+- Implement proper return values
+- Use proper parameter handling
+- Document function usage
+- Use proper error handling
+
+// Variables
+- Use proper variable scope
+- Use proper variable types
+- Use proper variable naming
+- Use proper variable initialization
+- Use proper variable cleanup
+
+// Logging
+- Use proper logging levels
+- Implement proper log rotation
+- Use proper log formatting
+- Use proper log location
+- Use proper log security
+
+// Best Practices
+- Use proper command options
+- Implement proper error handling
+- Use proper quoting
+- Implement proper path handling
+- Use proper command substitution 
\ No newline at end of file
diff --git a/rules/scripts/posix/zsh-script.cursorrules b/rules/scripts/posix/zsh-script.cursorrules
new file mode 100644
index 00000000..656f91b4
--- /dev/null
+++ b/rules/scripts/posix/zsh-script.cursorrules
@@ -0,0 +1,79 @@
+// POSIX Zsh Script Best Practices
+// This file contains rules and guidelines for POSIX zsh scripting
+
+// Script Structure
+- Use proper shebang line
+- Use proper script headers
+- Implement proper error handling
+- Use proper functions
+- Use proper indentation
+
+// Naming Conventions
+- Use lowercase for variables
+- Use UPPERCASE for constants
+- Use descriptive names
+- Use proper function names
+- Follow POSIX naming conventions
+
+// Error Handling
+- Use set -e for error handling
+- Use set -u for undefined variables
+- Use set -o pipefail for pipeline errors
+- Implement proper error messages
+- Use proper exit codes
+
+// Security
+- Use proper file permissions
+- Implement proper input validation
+- Use proper quoting
+- Implement proper path handling
+- Use proper command substitution
+
+// Performance
+- Use proper command selection
+- Implement proper loop optimization
+- Use proper variable usage
+- Implement proper process management
+- Use proper resource management
+
+// Documentation
+- Use proper comments
+- Document all functions
+- Document all parameters
+- Document all examples
+- Document all requirements
+
+// Testing
+- Test all functions
+- Test all parameters
+- Test all error conditions
+- Test all edge cases
+- Implement proper test cases
+
+// Functions
+- Use proper function structure
+- Implement proper return values
+- Use proper parameter handling
+- Document function usage
+- Use proper error handling
+
+// Variables
+- Use proper variable scope
+- Use proper variable types
+- Use proper variable naming
+- Use proper variable initialization
+- Use proper variable cleanup
+
+// Logging
+- Use proper logging levels
+- Implement proper log rotation
+- Use proper log formatting
+- Use proper log location
+- Use proper log security
+
+// Best Practices
+- Use proper command options
+- Implement proper error handling
+- Use proper quoting
+- Implement proper path handling
+- Use proper command substitution 
\ No newline at end of file
diff --git a/rules/scripts/powercli/powercli-script.cursorrules b/rules/scripts/powercli/powercli-script.cursorrules
new file mode 100644
index 00000000..68036536
--- /dev/null
+++ b/rules/scripts/powercli/powercli-script.cursorrules
@@ -0,0 +1,79 @@
+// PowerCLI Script Best Practices
+// This file contains rules and guidelines for PowerCLI scripting
+
+// Connection Management
+- Use proper connection handling
+- Implement connection pooling
+- Use proper authentication
+- Implement proper disconnection
+- Use proper error handling
+
+// VM Management
+- Use proper VM naming conventions
+- Implement proper VM configuration
+- Use proper resource allocation
+- Implement proper VM templates
+- Use proper VM cloning
+
+// Resource Management
+- Use proper resource allocation
+- Implement proper resource limits
+- Use proper resource monitoring
+- Implement proper resource cleanup
+- Use proper resource optimization
+
+// Security
+- Use proper authentication
+- Implement proper access control
+- Use proper encryption
+- Implement proper audit logging
+- Use proper security policies
+
+// Performance
+- Use proper batch operations
+- Implement proper error handling
+- Use proper resource management
+- Implement proper monitoring
+- Use proper optimization
+
+// Automation
+- Use proper scripting patterns
+- Implement proper error handling
+- Use proper logging
+- Implement proper scheduling
+- Use proper reporting
+
+// Documentation
+- Document all scripts
+- Document all functions
+- Document all parameters
+- Document all examples
+- Document all requirements
+
+// Testing
+- Test all scripts
+- Test all functions
+- Test all parameters
+- Test all error conditions
+- Test all edge cases
+
+// Error Handling
+- Use proper error messages
+- Implement proper error logging
+- Use proper error recovery
+- Implement proper error reporting
+- Use proper error prevention
+
+// Logging
+- Use proper log levels
+- Implement proper log rotation
+- Use proper log formatting
+- Implement proper log security
+- Use proper log analysis
+
+// Best Practices
+- Use proper naming conventions
+- Implement proper code structure
+- Use proper comments
+- Implement proper versioning
+- Use proper documentation 
\ No newline at end of file
diff --git a/rules/scripts/powershell/powershell-script.cursorrules b/rules/scripts/powershell/powershell-script.cursorrules
new file mode 100644
index 00000000..8744e173
--- /dev/null
+++ b/rules/scripts/powershell/powershell-script.cursorrules
@@ -0,0 +1,80 @@
+// PowerShell Script Best Practices
+
+// This file contains rules and guidelines for PowerShell scripting
+
+// Script Structure
+- Use proper script headers with metadata
+- Implement error handling with try-catch blocks
+- Use functions for modular code
+- Implement logging
+- Use proper indentation and formatting
+
+// Naming Conventions
+- Use Verb-Noun format for cmdlets
+- Use PascalCase for function names
+- Use camelCase for variables
+- Use descriptive names
+- Follow PowerShell naming conventions
+
+// Error Handling
+- Use try-catch-finally blocks
+- Implement proper error messages
+- Use Write-Error for errors
+- Use Write-Warning for warnings
+- Implement proper exit codes
+
+// Security
+- Use secure string for passwords
+- Implement proper authentication
+- Use least privilege principle
+- Validate input parameters
+- Use secure communication protocols
+
+// Performance
+- Use proper pipeline usage
+- Implement proper memory management
+- Use efficient data structures
+- Implement proper error handling
+- Use proper logging
+
+// Documentation
+- Use proper comment-based help
+- Document parameters
+- Document return values
+- Document examples
+- Document requirements
+
+// Testing
+- Implement unit tests
+- Use Pester for testing
+- Test error conditions
+- Test edge cases
+- Implement integration tests
+
+// Modules
+- Use proper module structure
+- Implement proper versioning
+- Use proper manifest files
+- Document module usage
+- Implement proper exports
+
+// Functions
+- Use proper parameter validation
+- Implement proper return values
+- Use proper error handling
+- Document function usage
+- Use proper logging
+
+// Variables
+- Use proper variable scope
+- Use proper variable types
+- Use proper variable naming
+- Use proper variable initialization
+- Use proper variable cleanup
+
+// Logging
+- Use proper logging levels
+- Implement proper log rotation
+- Use proper log formatting
+- Use proper log location
+- Use proper log security 
\ No newline at end of file

From 5fd44b7453fa92dba83299cf7d10e7922422dab0 Mon Sep 17 00:00:00 2001
From: Haim Cohen <haim1979@gmail.com>
Date: Thu, 12 Jun 2025 19:59:34 +0300
Subject: [PATCH 03/11] Add SRE and DBA rules for various database types

---
 README.md                                     |  7 ++
 rules/admin/database/mongodb-dba.cursorrules  | 72 +++++++++++++++++++
 rules/admin/database/mysql-dba.cursorrules    | 72 +++++++++++++++++++
 .../admin/database/postgresql-dba.cursorrules | 72 +++++++++++++++++++
 rules/admin/database/redis-dba.cursorrules    | 72 +++++++++++++++++++
 rules/devops/sre-engineer.cursorrules         | 72 +++++++++++++++++++
 6 files changed, 367 insertions(+)
 create mode 100644 rules/admin/database/mongodb-dba.cursorrules
 create mode 100644 rules/admin/database/mysql-dba.cursorrules
 create mode 100644 rules/admin/database/postgresql-dba.cursorrules
 create mode 100644 rules/admin/database/redis-dba.cursorrules
 create mode 100644 rules/devops/sre-engineer.cursorrules

diff --git a/README.md b/README.md
index 4773a823..4dc0ac45 100644
--- a/README.md
+++ b/README.md
@@ -202,6 +202,13 @@ A curated list of awesome .cursorrules files for enhancing your Cursor AI experi
 
 #### DevOps
 - [DevOps Engineer](./rules/devops/devops-engineer.cursorrules) - Best practices for DevOps engineering tasks
+- [SRE Engineer](./rules/devops/sre-engineer.cursorrules) - Best practices for Site Reliability Engineering
+
+#### Database Administration
+- [PostgreSQL DBA](./rules/admin/database/postgresql-dba.cursorrules) - Best practices for PostgreSQL database administration
+- [MySQL DBA](./rules/admin/database/mysql-dba.cursorrules) - Best practices for MySQL database administration
+- [MongoDB DBA](./rules/admin/database/mongodb-dba.cursorrules) - Best practices for MongoDB database administration
+- [Redis DBA](./rules/admin/database/redis-dba.cursorrules) - Best practices for Redis database administration
 
 #### Scripts
 - [PowerShell](./rules/scripts/powershell/powershell-script.cursorrules) - Best practices for PowerShell scripting
diff --git a/rules/admin/database/mongodb-dba.cursorrules b/rules/admin/database/mongodb-dba.cursorrules
new file mode 100644
index 00000000..980b2efa
--- /dev/null
+++ b/rules/admin/database/mongodb-dba.cursorrules
@@ -0,0 +1,72 @@
+// MongoDB Database Administration Best Practices
+// This file contains rules and guidelines for MongoDB DBA tasks
+
+// Database Design
+- Use proper document structure
+- Implement proper indexing strategies
+- Use proper sharding
+- Implement proper validation
+- Use proper data types
+
+// Performance Tuning
+- Implement proper query optimization
+- Use proper index maintenance
+- Set up proper connection pooling
+- Implement proper caching
+- Use proper performance monitoring
+
+// Backup and Recovery
+- Implement proper backup strategies
+- Use proper point-in-time recovery
+- Set up proper replication
+- Implement proper failover
+- Use proper backup verification
+
+// Security
+- Implement proper access control
+- Use proper encryption
+- Set up proper SSL/TLS
+- Implement proper audit logging
+- Use proper security policies
+
+// Monitoring
+- Implement proper performance monitoring
+- Use proper resource monitoring
+- Set up proper alerting
+- Implement proper logging
+- Use proper monitoring tools
+
+// Maintenance
+- Implement proper index maintenance
+- Use proper compaction
+- Set up proper statistics updates
+- Implement proper optimization
+- Use proper maintenance scheduling
+
+// High Availability
+- Implement proper replication
+- Use proper failover
+- Set up proper load balancing
+- Implement proper sharding
+- Use proper HA documentation
+
+// Disaster Recovery
+- Implement proper backup procedures
+- Use proper recovery procedures
+- Set up proper failover procedures
+- Implement proper disaster recovery testing
+- Use proper recovery documentation
+
+// Documentation
+- Document all configurations
+- Document all procedures
+- Document all policies
+- Document all changes
+- Document all incidents
+
+// Best Practices
+- Use proper naming conventions
+- Implement proper procedures
+- Use proper documentation
+- Implement proper training
+- Use proper communication 
\ No newline at end of file
diff --git a/rules/admin/database/mysql-dba.cursorrules b/rules/admin/database/mysql-dba.cursorrules
new file mode 100644
index 00000000..592c34bb
--- /dev/null
+++ b/rules/admin/database/mysql-dba.cursorrules
@@ -0,0 +1,72 @@
+// MySQL Database Administration Best Practices
+// This file contains rules and guidelines for MySQL DBA tasks
+
+// Database Design
+- Use proper table normalization
+- Implement proper indexing strategies
+- Use proper partitioning
+- Implement proper constraints
+- Use proper data types
+
+// Performance Tuning
+- Implement proper query optimization
+- Use proper index maintenance
+- Set up proper buffer pool tuning
+- Implement proper query cache
+- Use proper performance monitoring
+
+// Backup and Recovery
+- Implement proper backup strategies
+- Use proper point-in-time recovery
+- Set up proper replication
+- Implement proper failover
+- Use proper backup verification
+
+// Security
+- Implement proper access control
+- Use proper encryption
+- Set up proper SSL/TLS
+- Implement proper audit logging
+- Use proper security policies
+
+// Monitoring
+- Implement proper performance monitoring
+- Use proper resource monitoring
+- Set up proper alerting
+- Implement proper logging
+- Use proper monitoring tools
+
+// Maintenance
+- Implement proper table maintenance
+- Use proper index maintenance
+- Set up proper statistics updates
+- Implement proper optimization
+- Use proper maintenance scheduling
+
+// High Availability
+- Implement proper replication
+- Use proper failover
+- Set up proper load balancing
+- Implement proper clustering
+- Use proper HA documentation
+
+// Disaster Recovery
+- Implement proper backup procedures
+- Use proper recovery procedures
+- Set up proper failover procedures
+- Implement proper disaster recovery testing
+- Use proper recovery documentation
+
+// Documentation
+- Document all configurations
+- Document all procedures
+- Document all policies
+- Document all changes
+- Document all incidents
+
+// Best Practices
+- Use proper naming conventions
+- Implement proper procedures
+- Use proper documentation
+- Implement proper training
+- Use proper communication 
\ No newline at end of file
diff --git a/rules/admin/database/postgresql-dba.cursorrules b/rules/admin/database/postgresql-dba.cursorrules
new file mode 100644
index 00000000..f118cb58
--- /dev/null
+++ b/rules/admin/database/postgresql-dba.cursorrules
@@ -0,0 +1,72 @@
+// PostgreSQL Database Administration Best Practices
+// This file contains rules and guidelines for PostgreSQL DBA tasks
+
+// Database Design
+- Use proper table normalization
+- Implement proper indexing strategies
+- Use proper partitioning
+- Implement proper constraints
+- Use proper data types
+
+// Performance Tuning
+- Implement proper query optimization
+- Use proper index maintenance
+- Set up proper vacuuming
+- Implement proper statistics collection
+- Use proper performance monitoring
+
+// Backup and Recovery
+- Implement proper backup strategies
+- Use proper point-in-time recovery
+- Set up proper replication
+- Implement proper failover
+- Use proper backup verification
+
+// Security
+- Implement proper access control
+- Use proper encryption
+- Set up proper SSL/TLS
+- Implement proper audit logging
+- Use proper security policies
+
+// Monitoring
+- Implement proper performance monitoring
+- Use proper resource monitoring
+- Set up proper alerting
+- Implement proper logging
+- Use proper monitoring tools
+
+// Maintenance
+- Implement proper vacuuming
+- Use proper index maintenance
+- Set up proper statistics updates
+- Implement proper table maintenance
+- Use proper maintenance scheduling
+
+// High Availability
+- Implement proper replication
+- Use proper failover
+- Set up proper load balancing
+- Implement proper clustering
+- Use proper HA documentation
+
+// Disaster Recovery
+- Implement proper backup procedures
+- Use proper recovery procedures
+- Set up proper failover procedures
+- Implement proper disaster recovery testing
+- Use proper recovery documentation
+
+// Documentation
+- Document all configurations
+- Document all procedures
+- Document all policies
+- Document all changes
+- Document all incidents
+
+// Best Practices
+- Use proper naming conventions
+- Implement proper procedures
+- Use proper documentation
+- Implement proper training
+- Use proper communication 
\ No newline at end of file
diff --git a/rules/admin/database/redis-dba.cursorrules b/rules/admin/database/redis-dba.cursorrules
new file mode 100644
index 00000000..d16639d6
--- /dev/null
+++ b/rules/admin/database/redis-dba.cursorrules
@@ -0,0 +1,72 @@
+// Redis Database Administration Best Practices
+// This file contains rules and guidelines for Redis DBA tasks
+
+// Database Design
+- Use proper data structures
+- Implement proper key naming
+- Use proper memory optimization
+- Implement proper persistence
+- Use proper data types
+
+// Performance Tuning
+- Implement proper memory management
+- Use proper connection pooling
+- Set up proper persistence
+- Implement proper caching
+- Use proper performance monitoring
+
+// Backup and Recovery
+- Implement proper backup strategies
+- Use proper point-in-time recovery
+- Set up proper replication
+- Implement proper failover
+- Use proper backup verification
+
+// Security
+- Implement proper access control
+- Use proper encryption
+- Set up proper SSL/TLS
+- Implement proper audit logging
+- Use proper security policies
+
+// Monitoring
+- Implement proper performance monitoring
+- Use proper memory monitoring
+- Set up proper alerting
+- Implement proper logging
+- Use proper monitoring tools
+
+// Maintenance
+- Implement proper key maintenance
+- Use proper memory optimization
+- Set up proper persistence
+- Implement proper optimization
+- Use proper maintenance scheduling
+
+// High Availability
+- Implement proper replication
+- Use proper failover
+- Set up proper load balancing
+- Implement proper clustering
+- Use proper HA documentation
+
+// Disaster Recovery
+- Implement proper backup procedures
+- Use proper recovery procedures
+- Set up proper failover procedures
+- Implement proper disaster recovery testing
+- Use proper recovery documentation
+
+// Documentation
+- Document all configurations
+- Document all procedures
+- Document all policies
+- Document all changes
+- Document all incidents
+
+// Best Practices
+- Use proper naming conventions
+- Implement proper procedures
+- Use proper documentation
+- Implement proper training
+- Use proper communication 
\ No newline at end of file
diff --git a/rules/devops/sre-engineer.cursorrules b/rules/devops/sre-engineer.cursorrules
new file mode 100644
index 00000000..759fb4d2
--- /dev/null
+++ b/rules/devops/sre-engineer.cursorrules
@@ -0,0 +1,72 @@
+// Site Reliability Engineering (SRE) Best Practices
+// This file contains rules and guidelines for SRE tasks
+
+// Service Level Objectives (SLOs)
+- Define clear service level objectives
+- Implement proper error budgets
+- Monitor SLO compliance
+- Set up proper alerting thresholds
+- Document SLO targets and measurements
+
+// Monitoring and Observability
+- Implement comprehensive monitoring
+- Use proper metrics collection
+- Set up proper logging
+- Implement proper tracing
+- Use proper dashboards
+
+// Incident Management
+- Implement proper incident response
+- Use proper incident documentation
+- Set up proper on-call rotations
+- Implement proper post-mortems
+- Use proper incident tracking
+
+// Capacity Planning
+- Implement proper capacity forecasting
+- Use proper resource scaling
+- Set up proper load testing
+- Implement proper performance testing
+- Use proper capacity documentation
+
+// Automation
+- Automate repetitive tasks
+- Implement proper deployment automation
+- Use proper configuration management
+- Implement proper testing automation
+- Use proper monitoring automation
+
+// Reliability
+- Implement proper redundancy
+- Use proper failover mechanisms
+- Set up proper disaster recovery
+- Implement proper backup strategies
+- Use proper reliability testing
+
+// Performance
+- Implement proper performance monitoring
+- Use proper performance optimization
+- Set up proper load balancing
+- Implement proper caching strategies
+- Use proper performance documentation
+
+// Security
+- Implement proper security monitoring
+- Use proper access control
+- Set up proper security scanning
+- Implement proper security testing
+- Use proper security documentation
+
+// Documentation
+- Document all procedures
+- Document all configurations
+- Document all incidents
+- Document all changes
+- Document all best practices
+
+// Best Practices
+- Use proper naming conventions
+- Implement proper procedures
+- Use proper documentation
+- Implement proper training
+- Use proper communication 
\ No newline at end of file

From 8e3ff6a9c9c8cf1ae18341392f3eaa99a1980c15 Mon Sep 17 00:00:00 2001
From: Haim Cohen <haim1979@gmail.com>
Date: Thu, 12 Jun 2025 20:32:06 +0300
Subject: [PATCH 04/11] Enhance README.md with modern design and improved
 content structure

---
 README.md | 119 +++++++++++++++++++++++++++++++++---------------------
 1 file changed, 74 insertions(+), 45 deletions(-)

diff --git a/README.md b/README.md
index 4dc0ac45..6d042497 100644
--- a/README.md
+++ b/README.md
@@ -2,24 +2,46 @@
 
 <p align="center">
   <a href="https://patrickjs.com" target="_blank">
-    <img src="/cursor-ai-logo.png" alt="Awesome CursorRules" />
+    <img src="/cursor-ai-logo.png" alt="Awesome CursorRules" width="200" height="200" />
   </a>
 </p>
 
-A curated list of awesome .cursorrules files for enhancing your Cursor AI experience.
+<p align="center">
+  <b>Supercharge Your Cursor AI Experience with Custom Rules</b>
+</p>
 
-[Cursor AI](https://cursor.sh/) is an AI-powered code editor. `.cursorrules` files define custom rules for Cursor AI to follow when generating code, allowing you to tailor its behavior to your specific needs and preferences.
+<p align="center">
+  <a href="#contents">Contents</a> •
+  <a href="#rules">Rules</a> •
+  <a href="#how-to-use">How to Use</a> •
+  <a href="#contributing">Contributing</a> •
+  <a href="#license">License</a>
+</p>
+
+<p align="center">
+  <img src="https://img.shields.io/github/stars/yourusername/awesome-cursorrules?style=social" alt="Stars" />
+  <img src="https://img.shields.io/github/forks/yourusername/awesome-cursorrules?style=social" alt="Forks" />
+  <img src="https://img.shields.io/github/issues/yourusername/awesome-cursorrules" alt="Issues" />
+  <img src="https://img.shields.io/github/license/yourusername/awesome-cursorrules" alt="License" />
+</p>
 
-## Why .cursorrules?
+## 🚀 Why .cursorrules?
 
-.cursorrules files are repository-specific "Rules for AI" that help Cursor AI understand your project's context, coding standards, and best practices. These rules are automatically appended to your global "Rules for AI" settings when working in a repository.
+.cursorrules files are your secret weapon for supercharging Cursor AI's capabilities. They act as repository-specific "Rules for AI" that help Cursor AI understand your project's context, coding standards, and best practices. These rules are automatically appended to your global "Rules for AI" settings when working in a repository.
 
-## Contents
+### Key Benefits:
+- 🎯 **Project-Specific Context**: Tailor AI behavior to your project's needs
+- 📚 **Best Practices**: Enforce coding standards and patterns
+- 🔄 **Consistency**: Maintain uniform code style across your team
+- 🚀 **Productivity**: Speed up development with AI-powered assistance
+- 🛠️ **Customization**: Fine-tune AI responses to match your workflow
 
-- [Awesome CursorRules ](#awesome-cursorrules-)
-  - [Why .cursorrules?](#why-cursorrules)
-  - [Contents](#contents)
-  - [Rules](#rules)
+## 📋 Contents
+
+- [Awesome CursorRules](#awesome-cursorrules-)
+  - [Why .cursorrules?](#-why-cursorrules)
+  - [Contents](#-contents)
+  - [Rules](#-rules)
     - [Frontend Frameworks and Libraries](#frontend-frameworks-and-libraries)
     - [Backend and Full-Stack](#backend-and-full-stack)
     - [Mobile Development](#mobile-development)
@@ -34,13 +56,11 @@ A curated list of awesome .cursorrules files for enhancing your Cursor AI experi
     - [Other](#other)
     - [Utilities](#utilities)
   - [Directories](#directories)
-  - [How to Use](#how-to-use)
-    - [Method One](#method-one)
-    - [Method Two](#method-two)
-  - [Contributing](#contributing)
-  - [License](#license)
+  - [How to Use](#-how-to-use)
+  - [Contributing](#-contributing)
+  - [License](#-license)
 
-## Rules
+## 🎯 Rules
 
 ### Frontend Frameworks and Libraries
 
@@ -236,46 +256,55 @@ A curated list of awesome .cursorrules files for enhancing your Cursor AI experi
 
 - [Cursor Watchful Headers](https://github.com/johnbenac/cursor-watchful-headers) - A Python-based file watching system that automatically manages headers in text files and maintains a clean, focused project tree structure. Perfect for maintaining consistent file headers and documentation across your project, with special features to help LLMs maintain better project awareness.
 
-## Directories
+## 📚 Directories
 
-- [CursorList](https://cursorlist.com)
-- [CursorDirectory](https://cursor.directory/)
+- [CursorList](https://cursorlist.com) - A curated list of Cursor AI resources
+- [CursorDirectory](https://cursor.directory/) - Directory of Cursor AI tools and plugins
 
-## How to Use
+## 🚀 How to Use
 
-### Method One
+### Method One: Manual Installation
 
-1. Install [Cursor AI](https://cursor.sh/) if you haven't already.
-2. Browse the rules above to find a `.cursorrules` file that suits your needs.
-3. Copy the chosen `.cursorrules` file to your project's root directory.
-4. Customize the rules as needed for your specific project requirements.
+1. Install [Cursor AI](https://cursor.sh/) if you haven't already
+2. Browse the rules above to find a `.cursorrules` file that suits your needs
+3. Copy the chosen `.cursorrules` file to your project's root directory
+4. Customize the rules as needed for your specific project requirements
 
-### Method Two
+### Method Two: VS Code Extension
 
-1. Install [Cursor AI](https://cursor.sh/) if you haven't already.
-2. Install [vscode-cursor-rules](https://marketplace.visualstudio.com/items?itemName=BeilunYang.cursor-rules) extension.
-3. Open the command palette (Cmd+Shift+P or Ctrl+Shift+P) and type `Cursor Rules: Add .cursorrules`.
-4. Select and download the `.cursorrules` file that suits your needs.
-5. Customize the rules as needed for your specific project requirements.
+1. Install [Cursor AI](https://cursor.sh/) if you haven't already
+2. Install [vscode-cursor-rules](https://marketplace.visualstudio.com/items?itemName=BeilunYang.cursor-rules) extension
+3. Open the command palette (Cmd+Shift+P or Ctrl+Shift+P) and type `Cursor Rules: Add .cursorrules`
+4. Select and download the `.cursorrules` file that suits your needs
+5. Customize the rules as needed for your specific project requirements
 
-## Contributing
+## 🤝 Contributing
 
-Contributions are welcome! If you have a great `.cursorrules` file to share:
+We welcome contributions! If you have a great `.cursorrules` file to share:
 
-1. Fork this repository.
-2. Create a new folder in the `rules` directory. The folder name should follow this pattern:
+1. Fork this repository
+2. Create a new folder in the `rules` directory following this pattern:
    `technology-focus-cursorrules-prompt-file`
-   For example: `react-typescript-cursorrules-prompt-file`
-3. Add your `.cursorrules` file to the new folder.
-4. Optionally, include a README.md in the folder to provide credit and a brief description.
-5. Update the main README.md file, adding your contribution to the appropriate category.
-6. Ensure your contribution follows the guidelines in the [`.cursorrules`](./.cursorrules) file at the root of this repository.
-7. Submit a pull request.
+   Example: `react-typescript-cursorrules-prompt-file`
+3. Add your `.cursorrules` file to the new folder
+4. Optionally, include a README.md in the folder to provide credit and a brief description
+5. Update the main README.md file, adding your contribution to the appropriate category
+6. Ensure your contribution follows the guidelines in the [`.cursorrules`](./.cursorrules) file
+7. Submit a pull request
+
+### Contribution Guidelines:
+- 🎯 Keep rules focused and specific
+- 📝 Include clear documentation
+- 🔄 Follow existing naming conventions
+- ✅ Test your rules thoroughly
+- 📚 Update the main README.md appropriately
+
+## 📄 License
 
-Please ensure your contribution is original or properly credited if based on existing work. Refer to the `.cursorrules` file in the root of this repository for detailed guidelines on formatting, naming conventions, and best practices for contributions.
+[![CC0](https://licensebuttons.net/p/zero/1.0/88x31.png)](https://creativecommons.org/publicdomain/zero/1.0/)
 
 ---
 
-## License
-
-[![CC0](https://licensebuttons.net/p/zero/1.0/88x31.png)](https://creativecommons.org/publicdomain/zero/1.0/)
+<p align="center">
+  Made with ❤️ by the Cursor AI Community
+</p>

From aa637b9d4078d39fd36bdbe7c00aa8a33395a69b Mon Sep 17 00:00:00 2001
From: Haim Cohen <haim1979@gmail.com>
Date: Thu, 12 Jun 2025 20:36:06 +0300
Subject: [PATCH 05/11] fix logo size

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 6d042497..bb8019dc 100644
--- a/README.md
+++ b/README.md
@@ -2,7 +2,7 @@
 
 <p align="center">
   <a href="https://patrickjs.com" target="_blank">
-    <img src="/cursor-ai-logo.png" alt="Awesome CursorRules" width="200" height="200" />
+    <img src="/cursor-ai-logo.png" alt="Awesome CursorRules"/>
   </a>
 </p>
 

From 5abb32a7544cdee0a9df2b5fcdf1b8b1b4f6ce89 Mon Sep 17 00:00:00 2001
From: Haim Cohen <haim1979@gmail.com>
Date: Thu, 12 Jun 2025 20:37:43 +0300
Subject: [PATCH 06/11] Update GitHub badges with correct repository username

---
 README.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/README.md b/README.md
index bb8019dc..7bec2c95 100644
--- a/README.md
+++ b/README.md
@@ -2,7 +2,7 @@
 
 <p align="center">
   <a href="https://patrickjs.com" target="_blank">
-    <img src="/cursor-ai-logo.png" alt="Awesome CursorRules"/>
+    <img src="/cursor-ai-logo.png" alt="Awesome CursorRules" width="200" height="200" />
   </a>
 </p>
 
@@ -19,10 +19,10 @@
 </p>
 
 <p align="center">
-  <img src="https://img.shields.io/github/stars/yourusername/awesome-cursorrules?style=social" alt="Stars" />
-  <img src="https://img.shields.io/github/forks/yourusername/awesome-cursorrules?style=social" alt="Forks" />
-  <img src="https://img.shields.io/github/issues/yourusername/awesome-cursorrules" alt="Issues" />
-  <img src="https://img.shields.io/github/license/yourusername/awesome-cursorrules" alt="License" />
+  <img src="https://img.shields.io/github/stars/sk3pp3r/awesome-cursorrules?style=social" alt="Stars" />
+  <img src="https://img.shields.io/github/forks/sk3pp3r/awesome-cursorrules?style=social" alt="Forks" />
+  <img src="https://img.shields.io/github/issues/sk3pp3r/awesome-cursorrules" alt="Issues" />
+  <img src="https://img.shields.io/github/license/sk3pp3r/awesome-cursorrules" alt="License" />
 </p>
 
 ## 🚀 Why .cursorrules?

From 78fc09578c6bf514493524b26808122e551d8193 Mon Sep 17 00:00:00 2001
From: Haim Cohen <haim1979@gmail.com>
Date: Thu, 12 Jun 2025 20:39:11 +0300
Subject: [PATCH 07/11] fix logo size

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 7bec2c95..9faaff39 100644
--- a/README.md
+++ b/README.md
@@ -2,7 +2,7 @@
 
 <p align="center">
   <a href="https://patrickjs.com" target="_blank">
-    <img src="/cursor-ai-logo.png" alt="Awesome CursorRules" width="200" height="200" />
+    <img src="/cursor-ai-logo.png" alt="Awesome CursorRules"/>
   </a>
 </p>
 

From c859d2b228f027e5c19dd7d5a5d0a928b23ad0bf Mon Sep 17 00:00:00 2001
From: Haim Cohen <haim1979@gmail.com>
Date: Thu, 12 Jun 2025 20:45:36 +0300
Subject: [PATCH 08/11] docs: add README.md files for admin subdirectories

---
 rules/admin/database/README.md | 42 ++++++++++++++++++++++++++++++++++
 rules/admin/network/README.md  | 38 ++++++++++++++++++++++++++++++
 rules/admin/system/README.md   | 38 ++++++++++++++++++++++++++++++
 rules/admin/vmware/README.md   | 39 +++++++++++++++++++++++++++++++
 4 files changed, 157 insertions(+)
 create mode 100644 rules/admin/database/README.md
 create mode 100644 rules/admin/network/README.md
 create mode 100644 rules/admin/system/README.md
 create mode 100644 rules/admin/vmware/README.md

diff --git a/rules/admin/database/README.md b/rules/admin/database/README.md
new file mode 100644
index 00000000..d831c75c
--- /dev/null
+++ b/rules/admin/database/README.md
@@ -0,0 +1,42 @@
+# Database Administration Rules
+
+This directory contains Cursor AI rules for database administration (DBA) tasks across different database management systems. These rules are designed to help Cursor AI provide better assistance when working with various database technologies.
+
+## Contents
+
+- `mysql-dba.cursorrules` - Rules for MySQL database administration
+- `postgresql-dba.cursorrules` - Rules for PostgreSQL database administration
+- `mongodb-dba.cursorrules` - Rules for MongoDB database administration
+- `redis-dba.cursorrules` - Rules for Redis database administration
+
+## Purpose
+
+These rules help Cursor AI understand:
+- Database administration best practices
+- Database security and access control
+- Performance optimization and tuning
+- Backup and recovery procedures
+- Database monitoring and maintenance
+- Query optimization
+- Database design principles
+- Database automation and scripting
+
+## Usage
+
+These rules are automatically loaded by Cursor AI when working in a database administration context. They provide guidance and best practices for:
+- Managing database configurations
+- Implementing security measures
+- Optimizing database performance
+- Handling backup and recovery
+- Monitoring database health
+- Writing efficient queries
+- Automating database tasks
+- Following database standards
+
+## Contributing
+
+Feel free to contribute to these rules by:
+1. Adding new database administration related rules
+2. Improving existing rules
+3. Adding more specific use cases
+4. Updating best practices 
\ No newline at end of file
diff --git a/rules/admin/network/README.md b/rules/admin/network/README.md
new file mode 100644
index 00000000..770168d7
--- /dev/null
+++ b/rules/admin/network/README.md
@@ -0,0 +1,38 @@
+# Network Administration Rules
+
+This directory contains Cursor AI rules for network administration and engineering tasks. These rules are designed to help Cursor AI provide better assistance when working with network infrastructure and configurations.
+
+## Contents
+
+- `network-engineer.cursorrules` - Rules for network engineering tasks and best practices
+
+## Purpose
+
+These rules help Cursor AI understand:
+- Network infrastructure design and implementation
+- Network security best practices
+- Routing and switching configurations
+- Network monitoring and troubleshooting
+- Network performance optimization
+- Network protocols and standards
+- Network automation and scripting
+- Network documentation practices
+
+## Usage
+
+These rules are automatically loaded by Cursor AI when working in a network administration context. They provide guidance and best practices for:
+- Configuring network devices
+- Implementing network security measures
+- Troubleshooting network issues
+- Optimizing network performance
+- Automating network tasks
+- Documenting network infrastructure
+- Following network standards and protocols
+
+## Contributing
+
+Feel free to contribute to these rules by:
+1. Adding new network administration related rules
+2. Improving existing rules
+3. Adding more specific use cases
+4. Updating best practices 
\ No newline at end of file
diff --git a/rules/admin/system/README.md b/rules/admin/system/README.md
new file mode 100644
index 00000000..2f82b47c
--- /dev/null
+++ b/rules/admin/system/README.md
@@ -0,0 +1,38 @@
+# System Engineering Rules
+
+This directory contains Cursor AI rules for system engineering and administration tasks. These rules are designed to help Cursor AI provide better assistance when working with system infrastructure and management.
+
+## Contents
+
+- `system-engineer.cursorrules` - Rules for system engineering tasks and best practices
+
+## Purpose
+
+These rules help Cursor AI understand:
+- System infrastructure design and implementation
+- Operating system administration
+- System security best practices
+- System monitoring and maintenance
+- Performance optimization
+- System automation and scripting
+- Backup and recovery procedures
+- System documentation practices
+
+## Usage
+
+These rules are automatically loaded by Cursor AI when working in a system administration context. They provide guidance and best practices for:
+- Managing system configurations
+- Implementing security measures
+- Troubleshooting system issues
+- Optimizing system performance
+- Automating system tasks
+- Documenting system infrastructure
+- Following system administration standards
+
+## Contributing
+
+Feel free to contribute to these rules by:
+1. Adding new system administration related rules
+2. Improving existing rules
+3. Adding more specific use cases
+4. Updating best practices 
\ No newline at end of file
diff --git a/rules/admin/vmware/README.md b/rules/admin/vmware/README.md
new file mode 100644
index 00000000..94ea0950
--- /dev/null
+++ b/rules/admin/vmware/README.md
@@ -0,0 +1,39 @@
+# VMware Administration Rules
+
+This directory contains Cursor AI rules for VMware virtualization administration tasks. These rules are designed to help Cursor AI provide better assistance when working with VMware infrastructure and management.
+
+## Contents
+
+- `vmware-admin.cursorrules` - Rules for VMware administration tasks and best practices
+
+## Purpose
+
+These rules help Cursor AI understand:
+- VMware infrastructure design and implementation
+- Virtual machine management
+- VMware security best practices
+- Resource optimization and allocation
+- High availability and disaster recovery
+- VMware automation and scripting
+- Performance monitoring and tuning
+- VMware documentation practices
+
+## Usage
+
+These rules are automatically loaded by Cursor AI when working in a VMware administration context. They provide guidance and best practices for:
+- Managing virtual infrastructure
+- Implementing security measures
+- Optimizing resource usage
+- Setting up high availability
+- Automating VMware tasks
+- Monitoring performance
+- Documenting virtual infrastructure
+- Following VMware best practices
+
+## Contributing
+
+Feel free to contribute to these rules by:
+1. Adding new VMware administration related rules
+2. Improving existing rules
+3. Adding more specific use cases
+4. Updating best practices 
\ No newline at end of file

From 073c91a9cd52316c54ab98806a50a6c512907afe Mon Sep 17 00:00:00 2001
From: Haim Cohen <haim1979@gmail.com>
Date: Thu, 26 Jun 2025 22:49:07 +0300
Subject: [PATCH 09/11] Create devops-engineer-enhanced.cursorrules

---
 .../devops-engineer-enhanced.cursorrules      | 255 ++++++++++++++++++
 1 file changed, 255 insertions(+)
 create mode 100644 rules/devops/devops-engineer-enhanced.cursorrules

diff --git a/rules/devops/devops-engineer-enhanced.cursorrules b/rules/devops/devops-engineer-enhanced.cursorrules
new file mode 100644
index 00000000..f076c12d
--- /dev/null
+++ b/rules/devops/devops-engineer-enhanced.cursorrules
@@ -0,0 +1,255 @@
+// DevOps Engineering Cursor Rules
+// Comprehensive guidelines for DevOps tasks with specific implementation patterns
+
+// =============================================================================
+// INFRASTRUCTURE AS CODE (IaC)
+// =============================================================================
+
+// Terraform Best Practices
+- Always use terraform state backends (S3 + DynamoDB for locking)
+- Structure code: /environments/dev|staging|prod/, /modules/, /shared/
+- Use .terraform-version files and version constraints
+- Implement data sources instead of hardcoded values
+- Use locals {} blocks for complex expressions
+- Always include provider version constraints
+- Use terraform fmt, validate, and plan before apply
+- Tag all resources consistently with environment, project, owner
+
+// Ansible Patterns
+- Use ansible-vault for sensitive data
+- Structure: group_vars/, host_vars/, roles/, playbooks/
+- Use handlers for service restarts
+- Implement idempotent tasks with proper conditionals
+- Use molecule for role testing
+- Pin collection and role versions in requirements.yml
+
+// =============================================================================
+// CI/CD PIPELINE PATTERNS
+// =============================================================================
+
+// Pipeline Structure (GitLab CI / GitHub Actions)
+- Use multi-stage pipelines: build -> test -> security -> deploy
+- Implement parallel job execution where possible
+- Use artifacts and caching strategically
+- Fail fast principle - run quick tests first
+- Use environment-specific variables and secrets
+- Implement approval gates for production deployments
+
+// Security Integration
+- Use SAST tools: SonarQube, CodeQL, Semgrep
+- Container scanning: Trivy, Snyk, Clair
+- Dependency scanning: OWASP Dependency Check
+- Infrastructure scanning: Checkov, tfsec
+- Implement license compliance checks
+
+// Deployment Patterns
+- Blue-green deployments for zero downtime
+- Canary releases with automated rollback triggers
+- Feature flags for gradual rollouts
+- Database migration strategies in pipelines
+- Environment promotion pipelines (dev -> staging -> prod)
+
+// =============================================================================
+// MONITORING & OBSERVABILITY
+// =============================================================================
+
+// The Three Pillars Implementation
+- Metrics: Prometheus + Grafana, CloudWatch, DataDog
+- Logs: ELK Stack, Loki, Fluentd, CloudWatch Logs
+- Traces: Jaeger, Zipkin, AWS X-Ray
+- Use OpenTelemetry for vendor-neutral instrumentation
+
+// Alert Management
+- Use alert runbooks with clear escalation paths
+- Implement alert fatigue prevention (proper thresholds)
+- Use labels and routing for team-specific alerts
+- Implement SLI/SLO/Error Budget monitoring
+- Create dashboards for different audiences (dev, ops, business)
+
+// Key Metrics to Track
+- Golden Signals: Latency, Traffic, Errors, Saturation
+- Infrastructure: CPU, Memory, Disk, Network
+- Application: Response times, throughput, error rates
+- Business: Conversion rates, user engagement
+
+// =============================================================================
+// SECURITY IMPLEMENTATION
+// =============================================================================
+
+// Identity & Access Management
+- Use IAM roles instead of access keys
+- Implement RBAC with principle of least privilege
+- Use service accounts for automation
+- Regular access reviews and cleanup
+- Multi-factor authentication enforcement
+
+// Secrets Management
+- Use HashiCorp Vault, AWS Secrets Manager, Azure Key Vault
+- Never commit secrets to version control
+- Rotate secrets regularly with automation
+- Use short-lived tokens where possible
+- Implement secret scanning in repositories
+
+// Network Security
+- Zero-trust network architecture
+- Use VPCs with proper subnet segmentation
+- Implement Web Application Firewalls (WAF)
+- Use encrypted communication (TLS 1.3+)
+- Regular penetration testing and vulnerability assessments
+
+// =============================================================================
+// CONTAINERIZATION & ORCHESTRATION
+// =============================================================================
+
+// Docker Best Practices
+- Use minimal base images (Alpine, Distroless)
+- Multi-stage builds to reduce image size
+- Run containers as non-root users
+- Use .dockerignore files
+- Scan images for vulnerabilities
+- Implement health checks and readiness probes
+
+// Kubernetes Patterns
+- Use namespaces for environment separation
+- Implement resource quotas and limits
+- Use ConfigMaps and Secrets appropriately
+- Implement Pod Security Standards
+- Use Helm charts for application packaging
+- Implement HPA and VPA for auto-scaling
+- Use network policies for micro-segmentation
+
+// =============================================================================
+// CLOUD-NATIVE PATTERNS
+// =============================================================================
+
+// AWS Best Practices
+- Use CloudFormation/CDK for infrastructure
+- Implement least privilege IAM policies
+- Use VPC endpoints for service communication
+- Implement cost allocation tags
+- Use CloudTrail for audit logging
+- Implement backup strategies with RTO/RPO requirements
+
+// Multi-Cloud Considerations
+- Use cloud-agnostic tools where possible
+- Implement vendor lock-in mitigation strategies
+- Use consistent naming conventions across clouds
+- Implement cross-cloud disaster recovery
+
+// =============================================================================
+// AUTOMATION PATTERNS
+// =============================================================================
+
+// GitOps Implementation
+- Use ArgoCD, Flux, or GitLab GitOps
+- Separate application and configuration repositories
+- Implement automated drift detection and correction
+- Use declarative configuration management
+
+// Self-Healing Systems
+- Implement circuit breakers and retry mechanisms
+- Use auto-scaling based on metrics
+- Implement automated failover procedures
+- Use chaos engineering for resilience testing
+
+// =============================================================================
+// DOCUMENTATION STANDARDS
+// =============================================================================
+
+// Required Documentation
+- README.md with setup and usage instructions
+- Architecture Decision Records (ADRs)
+- API documentation with OpenAPI/Swagger
+- Runbooks for incident response
+- Disaster recovery procedures with testing schedules
+
+// Diagram Requirements
+- Use tools like Draw.io, Lucidchart, or Mermaid
+- Maintain C4 model architecture diagrams
+- Network topology diagrams
+- Data flow diagrams
+- Incident response flowcharts
+
+// =============================================================================
+// PERFORMANCE & RELIABILITY
+// =============================================================================
+
+// Performance Optimization
+- Implement caching at multiple layers (CDN, application, database)
+- Use async processing for non-critical operations
+- Implement connection pooling
+- Use compression for data transfer
+- Regular performance testing with realistic load
+
+// Reliability Patterns
+- Implement circuit breakers and bulkhead patterns
+- Use timeouts and proper error handling
+- Implement graceful degradation
+- Use load balancing with health checks
+- Implement proper retry logic with exponential backoff
+
+// =============================================================================
+// DISASTER RECOVERY & BUSINESS CONTINUITY
+// =============================================================================
+
+// Backup Strategies
+- Follow 3-2-1 backup rule (3 copies, 2 different media, 1 offsite)
+- Test backup restoration regularly
+- Implement point-in-time recovery capabilities
+- Document backup retention policies
+- Use infrastructure backup tools (e.g., AWS Backup)
+
+// Recovery Procedures
+- Document RTO (Recovery Time Objective) and RPO (Recovery Point Objective)
+- Implement automated failover where possible
+- Regular disaster recovery drills
+- Cross-region replication for critical systems
+- Incident command structure and communication plans
+
+// =============================================================================
+// TEAM COLLABORATION & PROCESSES
+// =============================================================================
+
+// Code Review Standards
+- Use pull request templates
+- Require security and infrastructure review
+- Implement automated checks (linting, testing, security)
+- Document review criteria and standards
+- Use conventional commit messages
+
+// Incident Management
+- Use structured incident response (PagerDuty, OpsGenie)
+- Implement blameless post-mortems
+- Maintain incident timeline and communication
+- Use incident severity levels and escalation procedures
+- Track MTTR (Mean Time To Recovery) metrics
+
+// =============================================================================
+// COST OPTIMIZATION
+// =============================================================================
+
+// Cost Management
+- Implement resource tagging for cost allocation
+- Use rightsizing recommendations
+- Implement auto-shutdown for non-production environments
+- Use spot instances and reserved capacity where appropriate
+- Regular cost reviews and optimization recommendations
+- Implement cost alerts and budgets
+
+// =============================================================================
+// COMPLIANCE & GOVERNANCE
+// =============================================================================
+
+// Compliance Requirements
+- Implement audit logging for all changes
+- Use policy as code (Open Policy Agent, AWS Config)
+- Regular compliance scans and reporting
+- Data retention and deletion policies
+- Change management processes with approval workflows
+
+// Governance
+- Use resource naming conventions
+- Implement environment isolation
+- Use centralized logging and monitoring
+- Regular security and compliance assessments
+- Documentation of all architectural decisions

From 7ca1474759cc4796d5ae8bd32d6014a8f00f15ca Mon Sep 17 00:00:00 2001
From: Haim Cohen <haim1979@gmail.com>
Date: Thu, 26 Jun 2025 22:52:03 +0300
Subject: [PATCH 10/11] Update README.md

---
 README.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/README.md b/README.md
index 9faaff39..1c938eb2 100644
--- a/README.md
+++ b/README.md
@@ -222,6 +222,7 @@
 
 #### DevOps
 - [DevOps Engineer](./rules/devops/devops-engineer.cursorrules) - Best practices for DevOps engineering tasks
+- [DevOps Engineer - Enhanced](./rules/devops/devops-engineer-enhanced.cursorrules) - Best practices for DevOps engineering tasks - Enhanced
 - [SRE Engineer](./rules/devops/sre-engineer.cursorrules) - Best practices for Site Reliability Engineering
 
 #### Database Administration

From 27f9005da1132358e8dc101df5068860f311823f Mon Sep 17 00:00:00 2001
From: Haim Cohen <haim1979@gmail.com>
Date: Thu, 26 Jun 2025 22:53:03 +0300
Subject: [PATCH 11/11] Update devops-engineer-enhanced.cursorrules

---
 rules/devops/devops-engineer-enhanced.cursorrules | 1 +
 1 file changed, 1 insertion(+)

diff --git a/rules/devops/devops-engineer-enhanced.cursorrules b/rules/devops/devops-engineer-enhanced.cursorrules
index f076c12d..4cc031c9 100644
--- a/rules/devops/devops-engineer-enhanced.cursorrules
+++ b/rules/devops/devops-engineer-enhanced.cursorrules
@@ -1,5 +1,6 @@
 // DevOps Engineering Cursor Rules
 // Comprehensive guidelines for DevOps tasks with specific implementation patterns
+// Haim Cohen 2025 https://haimc.xyz | https://www.linkedin.com/in/haimc/
 
 // =============================================================================
 // INFRASTRUCTURE AS CODE (IaC)