Awesome Cursor Rules 🚀

A curated showcase of modern Cursor Rules configurations for development teams

🎯 Evolution Notice: This repository demonstrates the transition from legacy .cursorrules files to the powerful new Cursor Rules system with MDC format, rule types, and advanced organizational features.

🌟 What Changed: From .cursorrules to Cursor Rules

Cursor has revolutionized AI-assisted development by moving beyond the limitations of single-file .cursorrules:

| Legacy .cursorrules | New Cursor Rules | |----------------------|------------------| | ❌ Single file approach | ✅ Organized rule directories | | ❌ Plain text only | ✅ MDC format with metadata | | ❌ Always active | ✅ Smart rule types (Always, Auto, Manual, Agent) | | ❌ No file organization | ✅ Nested rules for complex projects | | ❌ Limited context | ✅ File references and templates | | ❌ Hard to maintain | ✅ Modular and scalable |

🎪 Repository Overview

This repository serves as a living showcase of modern Cursor Rules implementations across various development scenarios:

awesome-cursorrules/
├── 📚 rules/                       # Legacy .cursorrules files (migration source)
│   ├── appium-mobile-test-automation-framework/
│   ├── cypress-javascript-test-automation-framework/
│   ├── k6-performance-test-framework/
│   ├── playwright-javascript-test-automation-framework/
│   ├── restassured-java-framework/
│   ├── selenium-net-test-automation-framework/
│   ├── selenium-python-test-automation-framework/
│   └── vitest-javascript-unit-test-framework/
├── 🏗️ frameworks/                  # Framework .cursor/rules examples (with nested rules)
│   ├── cypress/                    # .cursor/rules/{core,patterns}/*.mdc
│   └── selenium-python/            # .cursor/rules/patterns/*.mdc
├── 🎯 example-structures/          # Flat, focused .mdc structure examples
│   ├── cypress/                    # testing-fundamentals, api-testing
│   ├── next-js/                    # app-router-patterns
│   ├── react-typescript/           # component-development
│   └── selenium-python/            # architecture, page-objects, test-patterns
└── 📖 legacy-migration/            # Before/after migration guides

🔄 The Great Migration: Before & After

Legacy .cursorrules Approach

# Old way - Everything in one file
project/
├── .cursorrules    # 200+ lines of mixed rules
├── src/
└── tests/

Problems with legacy approach:

• ❌ Difficult to maintain as projects grow
• ❌ No context awareness for different file types
• ❌ All rules active all the time
• ❌ Hard to share and collaborate on rules
• ❌ No template or example integration

Modern Cursor Rules System

# New way - Organized, contextual, powerful
project/
├── .cursor/rules/
│   ├── core-standards.mdc         # Always applied
│   ├── testing-patterns.mdc       # Auto-attached to test files
│   ├── framework-specific.mdc     # Context-aware activation
│   ├── advanced-optimizations.mdc # Agent-requested when relevant
│   └── templates/
│       ├── component-template.tsx
│       ├── test-template.spec.js
│       └── api-endpoint.js
├── src/
└── tests/

Benefits of modern approach:

• ✅ Context-aware rule activation
• ✅ Organized and maintainable structure
• ✅ Template integration and file references
• ✅ Team collaboration and version control friendly
• ✅ Scalable for enterprise projects

🎨 Understanding Rule Types

🔄 Always Rules

Core standards that apply to every AI interaction:

---
description: Universal coding standards for all projects
alwaysApply: true
---

# Core Development Standards
- Use TypeScript for type safety across all projects
- Implement comprehensive error handling and logging
- Write self-documenting code with clear naming
- Follow established architectural patterns

🎯 Auto Attached Rules

Automatically activated based on file patterns:

---
description: React component development patterns
globs: **/*.tsx,**/components/**/*.js,**/hooks/**/*.ts
alwaysApply: false
---

# React Development Excellence
- Use functional components with React hooks
- Implement proper prop validation with TypeScript
- Follow component composition patterns
- Optimize performance with useMemo and useCallback

@react-component-template.tsx
@custom-hook-template.ts

🤖 Agent Requested Rules

AI intelligently applies based on context:

---
description: Advanced performance optimization techniques
globs: **/*.js,**/*.ts,**/*.tsx
alwaysApply: false
---

# Performance Optimization Strategies
- Implement code splitting and lazy loading
- Use efficient algorithms and data structures
- Optimize bundle size and loading times
- Monitor and profile application performance

📝 Manual Rules

Explicitly invoked with @ruleName:

---
description: Complete test automation setup generator
alwaysApply: false
---

# Test Automation Project Generator
Creates a complete test automation project structure:

@selenium-project-structure
@cypress-configuration  
@playwright-setup
@github-actions-ci

📄 AGENTS.md: The Simpler Alternative

Alongside .mdc rules, Cursor now supports AGENTS.md — a plain Markdown file (no frontmatter, no metadata) that Cursor reads as project guidance. It's the lowest-friction way to give the agent context, and it's portable across other AI coding tools that adopt the same convention.

project/
├── AGENTS.md                # Project-wide guidance (always read)
├── frontend/
│   └── AGENTS.md            # Frontend-specific guidance
└── backend/
    └── AGENTS.md            # Backend-specific guidance

How it works:

• ✅ Plain Markdown — just write instructions, no YAML frontmatter
• ✅ Nested directories: an AGENTS.md deeper in the tree takes precedence over a parent one for files in that subtree
• ✅ Great for tech-stack notes, conventions, and "how to run things" that should always be in context

AGENTS.md vs .mdc rules — when to use which:

| Use AGENTS.md | Use .cursor/rules/*.mdc | |-----------------|---------------------------| | Always-on project context | Context-aware, file-scoped activation | | Simple, portable, no metadata | globs, description, alwaysApply control | | One file per directory | Multiple focused rules per project |

💡 Note: .cursor/rules/ only loads files with the .mdc extension — a plain .md placed there is ignored, except when it's named AGENTS.md.

🚀 Featured Framework Transformations

Python Test Automation Evolution

Legacy .cursorrules (Old Way):

# Selenium Python Test Automation Framework
- Use pytest as testing framework
- Implement Page Object Model pattern
- Follow PEP 8 style guide
- Use webdriver_manager for browser setup
- Implement proper logging

Modern Cursor Rules (New Way):

---
description: Advanced Selenium Python automation patterns
globs: **/*.py,**/test_*.py,**/pages/**/*.py,**/conftest.py
alwaysApply: false
---

# Selenium Python Excellence

## Architecture Patterns
- Implement advanced Page Object Model with base classes
- Use pytest fixtures for robust test data management
- Create reusable utility functions and custom assertions
- Implement proper WebDriver lifecycle management

## Code Quality Standards
- Follow PEP 8 with Black formatter integration
- Use type hints for better code maintainability
- Implement comprehensive error handling and logging
- Create detailed docstrings for all classes and methods

## Example Implementations:
@advanced-page-object.py
@pytest-configuration.py
@custom-assertions.py
@webdriver-factory.py

JavaScript E2E Testing Revolution

Modern Cypress Rules:

---
description: Advanced Cypress testing patterns and best practices
globs: **/*.cy.js,**/*.cy.ts,**/cypress/**/*.js
alwaysApply: false
---

# Cypress Testing Excellence

## Smart Element Selection
- Use `data-cy` attributes for reliable, maintainable selectors
- Implement custom commands for complex user interactions
- Create reusable page object patterns for large applications
- Handle dynamic content with proper wait strategies

## API Testing Integration
- Use `cy.intercept()` for comprehensive network testing
- Mock external services for reliable test execution
- Implement request/response validation patterns
- Create data-driven test scenarios

@cypress-page-object.js
@custom-commands.js
@api-testing-helpers.js

🏢 Enterprise-Scale Examples

Monorepo Organization Strategy

enterprise-monorepo/
├── .cursor/rules/                    # Global company standards
│   ├── security-compliance.mdc      # Security guidelines for all teams
│   ├── code-quality-standards.mdc   # Universal quality requirements
│   ├── documentation-rules.mdc      # Documentation standards
│   └── performance-guidelines.mdc   # Performance best practices
├── backend/
│   └── .cursor/rules/                # Backend-specific rules
│       ├── api-design-patterns.mdc   # RESTful API standards
│       ├── database-interactions.mdc # Database best practices
│       └── microservices-patterns.mdc # Service architecture
├── frontend/
│   └── .cursor/rules/                # Frontend-specific rules
│       ├── react-architecture.mdc    # Component architecture
│       ├── state-management.mdc      # Redux/Context patterns
│       └── ui-accessibility.mdc      # Accessibility standards
├── mobile/
│   └── .cursor/rules/                # Mobile-specific rules
│       ├── react-native-patterns.mdc # Mobile development
│       └── performance-mobile.mdc    # Mobile optimization
└── testing/
    └── .cursor/rules/                # Testing-specific rules
        ├── e2e-strategies.mdc         # End-to-end testing
        ├── unit-testing-patterns.mdc  # Unit test standards
        └── performance-testing.mdc    # Load testing guidelines

Team Collaboration Benefits

• 🎯 Consistent Standards: Shared rules ensure code consistency across teams
• ⚡ Faster Onboarding: New developers get immediate context and guidance
• 📚 Knowledge Sharing: Best practices are encoded and automatically shared
• 🛡️ Quality Assurance: Automated compliance with company standards
• 🔄 Continuous Improvement: Rules evolve with team learnings

📈 Migration Strategy

Phase 1: Assessment

# Analyze your current .cursorrules
echo "Current .cursorrules content:"
cat .cursorrules

# Identify different rule categories
# - Core standards (always apply)
# - Framework-specific patterns (auto-attach)
# - Advanced techniques (agent-requested)
# - Templates and examples (manual)

Phase 2: Organization

# Create modern structure
mkdir -p .cursor/rules/{core,frameworks,templates,advanced}

# Categorize existing rules
# Move content to appropriate MDC files
# Add metadata and glob patterns

Phase 3: Enhancement

# Add file references and templates
# Implement different rule types
# Create project-specific examples
# Test rule activation patterns

Phase 4: Team Adoption

# Share with team members
# Gather feedback and iterate
# Create team-specific customizations
# Monitor effectiveness and improve

🎯 Quick Start Scenarios

For Test Automation Teams

# Clone the showcase repository
git clone https://github.com/your-org/awesome-cursor-rules

# Set up Selenium Python automation
cp -r example-structures/selenium-python/.cursor/rules/* .cursor/rules/

# Add Cypress for E2E testing
cp -r example-structures/cypress/.cursor/rules/* e2e/.cursor/rules/

# Include React TypeScript patterns
cp -r example-structures/react-typescript/.cursor/rules/* frontend/.cursor/rules/

For Web Development Teams

# Full-stack development setup
cp -r example-structures/react-typescript/.cursor/rules/* frontend/.cursor/rules/
cp -r example-structures/selenium-python/.cursor/rules/* backend-tests/.cursor/rules/
cp -r example-structures/cypress/.c