awesome-cursorrules

Awesome Cursor Rules collects Markdown-based rule files that tell the Cursor AI editor how to behave for specific projects, file types, frameworks, and workflows. The README explains the format and the payoff.

Cursor AI is an AI-powered code editor, and Cursor Project Rules are Markdown-based .mdc files that live in a .cursor/rules/ directory. They tell Cursor how to behave for specific projects, file types, frameworks, and workflows. The repository collects these files so developers can add selected ones to their own projects. Sponsors appear at the top: coderabbit.ai, an MCP tool, and Warp.

Rules let developers define project-specific instructions, so Cursor responds to a project's actual needs instead of relying only on general coding knowledge. A rule file can describe local architecture, preferred libraries, common methods, and domain constraints. Consistency is the second argument: coding standards defined in .mdc files steer generated code toward the project's style, naming, structure, and review expectations.

Well-scoped rules give Cursor reusable project knowledge up front. The README argues the result is that suggestions fit the codebase on the first pass, so developers spend less time applying the same corrections again and again. For teams, shared rule files keep AI assistance aligned across contributors, covering framework usage, security requirements, testing conventions, and workflow details.

Rules are organized by category. Frontend frameworks cover Angular, Astro, Cursor AI with React and TypeScript, and Next.js variants for React 19, Tailwind, Supabase, and SEO. Backend and full-stack entries span Cloudflare Workers, Deno, Drupal, Elixir, Go, and Laravel. Mobile development covers Android Native with Jetpack Compose, Flutter, HarmonyOS, React Native Expo, and SwiftUI. JavaScript is the primary language and the license is CC0-1.0.

• Source 1 · Project repository
• Source 2 · README