A curated showcase of modern Cursor Rules configurations for development teams
🎯 Evolution Notice: This repository demonstrates the transition from legacy
.cursorrulesfiles to the powerful new Cursor Rules system with MDC format, rule types, and advanced organizational features.
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 |
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
# 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
# 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
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 patternsAutomatically 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.tsAI 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 performanceExplicitly 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-ciAlongside .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 guidanceHow it works:
- ✅ Plain Markdown — just write instructions, no YAML frontmatter
- ✅ Nested directories: an
AGENTS.mddeeper 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.mdcextension — a plain.mdplaced there is ignored, except when it's namedAGENTS.md.
# 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
---
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---
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.jsenterprise-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
- 🎯 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
# 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)# 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# Add file references and templates
# Implement different rule types
# Create project-specific examples
# Test rule activation patterns# Share with team members
# Gather feedback and iterate
# Create team-specific customizations
# Monitor effectiveness and improve# 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/# 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/.cursor/rules/* e2e-tests/.cursor/rules/# Large-scale monorepo setup - use enterprise patterns from README examples
mkdir -p .cursor/rules
# Copy relevant rules based on your tech stack
# Customize global standards for your organization
# Set up team-specific rules in subdirectories
# Integrate with CI/CD pipelines for consistency- 🏆 React + TypeScript + Testing Library: Complete frontend development stack
- 🚀 Python + Selenium + pytest: Comprehensive test automation framework
- 🏢 Enterprise Monorepo: Multi-team, multi-project organization
- 🎓 Educational: Learning-focused development with guided examples
"We reduced our code review cycle time by 40% after implementing shared Cursor Rules across our engineering teams. The AI now understands our patterns and generates code that follows our standards automatically."
— Sarah Chen, Engineering Manager at TechCorp
"New team members are productive on day one instead of week three. The rules provide immediate context about our coding patterns, testing strategies, and architectural decisions."
— Marcus Rodriguez, Senior Developer at StartupXYZ
- Research: Study framework best practices and common patterns
- Structure: Create organized rule directory with proper MDC format
- Examples: Include comprehensive template files and examples
- Documentation: Provide clear setup and usage instructions
- Testing: Validate rules with real-world projects
- Document Journey: Show before/after migration experience
- Measure Impact: Include metrics on productivity improvements
- Share Learnings: Explain what worked and what didn't
- Provide Templates: Create reusable configurations for similar teams
- Real-World Testing: Use rules in actual development projects
- Community Feedback: Gather input from diverse development teams
- Performance Optimization: Ensure rules don't slow down AI responses
- Regular Updates: Keep rules current with evolving best practices
- 📖 Official Documentation: Cursor Rules Comprehensive Guide
- 🎥 Video Tutorials: Migration Walkthrough Series
- 💬 Community Hub: Cursor Community Forum
- 🔧 Migration Tools: Automated Migration Scripts
- 📊 Analytics: Rule Effectiveness Dashboard
The evolution from .cursorrules to Cursor Rules represents more than just a technical upgrade—it's a fundamental transformation in how AI understands and enhances the development process:
AI that truly understands your project structure, coding patterns, and team preferences
Faster feature development with AI that knows your exact requirements and standards
Shared knowledge base that ensures consistency across team members and projects
Rules that evolve and improve based on team feedback and project growth
Infrastructure that grows from individual projects to enterprise-scale monorepos
Start your journey from legacy .cursorrules to modern Cursor Rules:
- 📊 Assess: Evaluate your current
.cursorrulessetup - 🏗️ Plan: Choose the appropriate migration strategy
- ⚡ Implement: Set up organized rule structure
- 🎯 Optimize: Fine-tune rules based on team feedback
- 🌟 Scale: Expand to enterprise-level organization
💡 Remember: The transition from
.cursorrulesto Cursor Rules isn't just about new syntax—it's about unlocking the full potential of AI-assisted development for your team.
- 📋 Structure Overview - Complete guide to modern flat structure organization
- 🔄 Before & After Migration - Real-world transformation examples
- 🐍 Selenium Python - Advanced test automation patterns
- 🌐 Cypress Testing - E2E testing excellence
- ⚛️ React TypeScript - Modern component development
- ▲ Next.js App Router - Server Components, Route Handlers, Server Actions, and metadata API
- 📖 Official Documentation - Cursor Rules comprehensive guide
- 🎥 Video Tutorials - Step-by-step migration walkthrough
- 💬 Community Forum - Connect with other developers
- 🏢 Enterprise Patterns - Large-scale monorepo organization
- 📈 Migration Strategy - Four-phase transformation approach
- 🌟 Community Showcase - Success stories and best practices
Begin with one framework example, then expand to your full tech stack
Collaborative rule creation ensures buy-in and better adoption
Track code review time, onboarding speed, and quality metrics
Regular rule updates keep pace with evolving best practices
Ready to revolutionize your development experience? Pick a framework above and start your transformation today! 🚀