Airsc is free for everyone. If it helps you, support it with $2–$20.

Support
VISign in
Cursor ruleSafeAgent workflow & memoryBeginner friendly

awesome-cursorrules

PatrickJS · PatrickJS/awesome-cursorrules

Offers a collection of Markdown-based project rules to customize and enhance the Cursor AI editor's behavior with project-specific guidance.

📄 Configuration files that enhance Cursor AI editor experience with custom rules and behaviors

41k stars3.5kLicense: CC0-1.0Updated 5 months ago0 opens

Preview

▍

What you can do with it

  • Implement project-specific coding standards in Cursor AI.
  • Guide Cursor to use preferred libraries or architectural patterns.
  • Define custom behaviors for different file types within your project.

Try asking your agent

  • “Implement the 'React best practices' rule from awesome-cursorrules for this TypeScript file.”
  • “Configure Cursor AI to follow the 'Python PEP 8' rule for all `.py` files in this project.”
  • “Show me the available rules for database schema design in awesome-cursorrules.”

Safety check

Safe

No risky patterns found in the files we scanned.

Automated scan of the repo files. Always review code you run.

From the README

Awesome Cursor Rules

Cursor Project Rules enhance Cursor AI editor behavior with project-specific guidance and reusable coding standards.

Cursor AI is an AI-powered code editor. Cursor Project Rules are Markdown-based .mdc files that live in .cursor/rules/ and tell Cursor how to behave for specific projects, file types, frameworks, and workflows.

Sponsorships

coderabbit.ai - Cut Code Review Time & Bugs in Half. Instantly.
  
	  
  
Unblocked MCP- Supercharge Cursor with your team’s knowledge 
  
	  
  
Warp - Built for coding with multiple AI agents

Contents

Why Cursor Rules

Cursor rules help developers define project-specific instructions for Cursor AI. This repository uses the modern .mdc Project Rules format.

Customized behavior means Cursor can respond to the specific needs of a project instead of relying only on general coding knowledge. Rules can describe local architecture, preferred libraries, common methods, domain constraints, and other context that makes generated code more relevant.

Consistency is the other big win. By defining coding standards and best practices in .mdc files, teams can guide Cursor toward code that matches the project's style, naming, structure, and review expectations.

Project rules also reduce repeated manual editing. Well-scoped rules give Cursor reusable project knowledge up front, so suggestions are more likely to fit the codebase on the first pass and less likely to need the same corrections again.

For teams, shared .cursor/rules/*.mdc files keep AI assistance aligned across contributors. Everyone can work from the same project-specific guidance, whether the rule covers framework usage, security requirements, testing conventions, or workflow details.

By adding selected .mdc files to .cursor/rules/, you can use these rules directly in your project.

Rules

Frontend Frameworks and Libraries

View source on GitHub