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
• Rules
  • Frontend Frameworks and Libraries
  • Backend and Full-Stack
  • Mobile Development
  • Games and Graphics
  • CSS and Styling
  • State Management
  • Database and API
  • Testing
  • Hosting and Deployments
  • Build Tools and Development
  • Language-Specific
  • Security
  • Documentation
• Directories
• How to Use

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

• Angular (Novo Elements) - Angular development with Novo Elements UI library.
• Angular (TypeScript) - Angular development with TypeScript integration.
• Astro (TypeScript) - Astro development with TypeScript integration.
• Beefree SDK (TypeScript, JavaScript, CSS, HTML, React, Angular, Vue) - Embedding Beefree SDK's no-code content editors (for emails, pages, and popups) into a web application.
• Cursor AI (React, TypeScript, shadcn/ui) - Cursor AI development with React, TypeScript, and shadcn/ui integration.
• Next.js 15 (React 19, Vercel AI, Tailwind) - Next.js development with React 19, Vercel AI, and Tailwind CSS integration.
• Next.js 15 (Supabase, TypeScript, Security) - 27 architecture rules preventing AI hallucinations: insecure auth (getSession vs getUser), synchronous params, deprecated imports, missing RLS, and Stripe key exposure. Built for Cursor Agent and Claude Code.
• Next.js 14 (Tailwind, SEO) - Next.js development with Tailwind CSS and SEO optimization.
• Next.js (React, Tailwind) - Next.js development with React and Tailwind CSS integration.
• Next.js (React, TypeScript) - Next.js development with React and TypeScript integration.
• Next.js (SEO Development) - Next.js development with SEO optimization.
• Next.js (Supabase Todo App) - Next.js development with Supabase integration for a Todo app.
• Next.js (TanStack Query v5) - Next.js App Router with TanStack Query v5, covering the HydrationBoundary pattern, Server Actions as mutations, and optimistic updates.
• Next.js (Type LLM) - Next.js development with Type LLM integration.
• [Next.js (Tailwind, TypeScript)](https://github.com/PatrickJS/awesome-cursorrules/blob/main