AcademyRules

Cursor rules, ready to install

Cursor rules files for each framework and language, so the AI writes code the way your project expects. What each file sets and how to add it.

See the listBook a free 20-min diagnostic call
  • 257in the catalogue
  • 257ready to install
  • 0official
  • 10 October 2026last updated

What is a Cursor rules file?

A Cursor rules file holds standing instructions for the AI in your editor: the stack you use, naming and style conventions, and things to avoid. Cursor adds them to every request, so suggestions follow your project instead of generic defaults.

How to choose one

Pick the file for your main framework and trim what does not apply. Short, specific rules work better than long generic ones. The same instructions also work in an AGENTS.md file for other coding agents.

Rules
by business area.

The 120 most used. Filter by area or search to reach all 257.

  1. 001AI Agent Specialist Cursor rulesDevelopment teams that want Cursor to follow one consistent TypeScript and React style across a project.RecommendedRules file
  2. 002Alpha Skills for quant factor researchQuantitative research and investment analysis teams that want to run factor research through natural language requests in Cursor.RecommendedRules file
  3. 003Android Jetpack Compose Cursor rulesMobile development teams building Android apps in Kotlin who want consistent Compose code from Cursor.RecommendedRules file
  4. 004Angular Novo Elements Cursor rulesDevelopment teams working on Angular projects who want Cursor to make small, careful and well documented changes.RecommendedRules file
  5. 005Angular TypeScript Cursor rulesFront-end teams building Angular applications who want readable, maintainable code suggestions from Cursor.RecommendedRules file
  6. 006Ankra CLI Cursor rulesPlatform and operations teams that manage Kubernetes clusters with Ankra and want Cursor to suggest correct CLI commands.RecommendedRules file
  7. 007Anti Over-Engineering Cursor rulesDevelopment teams that want smaller, focused diffs from Cursor and fewer unrequested changes to review.RecommendedRules file
  8. 008Anti-Sycophancy Code Discipline Cursor rulesDevelopment and code review teams who want Cursor to flag uncertainty instead of confirming code that may be wrong.RecommendedRules file
  9. 009ASCII Simulation Game Cursor rulesGame developers and hobby teams who want a clear brief for building an observer-style strategy simulation with Cursor.RecommendedRules file
  10. 010ASP.NET ABP Framework Cursor rulesBackend teams building .NET applications on the ABP Framework who want Cursor to follow its modular conventions.RecommendedRules file
  11. 011Astro, TypeScript and Tailwind rules for CursorWeb development teams building Astro sites who want Cursor to follow the same code and commit conventions every time.RecommendedRules file
  12. 012AutoML and hyperparameter optimization rulesData teams running model experiments who want Cursor to follow sound validation and run-tracking habits.RecommendedRules file
  13. 013Beefree SDK no-code content editor rulesProduct and marketing technology teams adding an email or page editor to their own application.RecommendedRules file
  14. 014Beefree SDK guidelines for CursorProduct and marketing technology teams who build email or landing page editing into their own tools.RecommendedRules file
  15. 015Blender Python add-on rules for CursorDesign and 3D production teams that build internal Blender tools and want consistent add-on code from Cursor.RecommendedRules file
  16. 016Chrome extension development rules for CursorDevelopment teams building browser extensions for internal workflows or customer-facing tools.RecommendedRules file
  17. 017Clean code guidelines for CursorAny development team that wants Cursor to write and refactor code to one shared readability standard.RecommendedRules file
  18. 018Cloudflare email to Telegram forwardingOperations or IT teams that want incoming domain email, such as a shared info address, to appear in a Telegram chat.RecommendedRules file
  19. 019Cloudflare Workers, Hono and Angular SaaS rulesProduct engineering teams building a SaaS application on Cloudflare who want consistent API and frontend conventions.RecommendedRules file
  20. 020Code guidelines for how Cursor makes changesDevelopment teams who want Cursor to make small, reviewable changes and avoid unrequested edits.RecommendedRules file
  21. 021Code pair interviewsEngineering and hiring teams who want AI-written code to stay readable and well structured during pair programming exercises.RecommendedRules file
  22. 022Code style consistencyDevelopment teams who want AI-generated code to match the conventions already used in their project.RecommendedRules file
  23. 023Code quality guidelinesDevelopment teams who want predictable, focused edits from their AI assistant that are easy to review.RecommendedRules file
  24. 024Convex guidelinesDevelopment teams building on Convex who want the AI to write backend functions in the expected syntax.RecommendedRules file
  25. 025C++ programming guidelinesC++ development teams who want AI-generated code to follow one set of naming and structure rules.RecommendedRules file
  26. 026C++ rules for CursorC++ development teams who want their AI assistant to follow clear style and naming conventions.RecommendedRules file
  27. 027React, TypeScript and shadcn/ui rulesFront-end teams building React and Next.js interfaces with Shadcn UI who want consistent AI-generated components.RecommendedRules file
  28. 028Cursor rules pack v2 (sample)Front-end development teams who want the AI to follow clear rules on dependencies, errors, comments and state management.RecommendedRules file
  29. 029Next.js 14 and Tailwind design-to-code rulesWeb and front-end teams who build pages from design mockups and want the AI to follow Next.js 14 conventions.RecommendedRules file
  30. 030PressThat WordPress draft app rulesDevelopers building a small desktop tool that lets content teams create WordPress drafts from the system tray.RecommendedRules file
  31. 031Cypress Accessibility Testing RulesQA and development teams that want accessibility checks written consistently in Cypress.RecommendedRules file
  32. 032Cypress API Testing RulesQA and backend teams that want API tests written consistently with Cypress.RecommendedRules file
  33. 033Cypress Defect Tracking RulesQA teams that want Cypress results tagged and structured so defects can be traced to teams and features.RecommendedRules file
  34. 034Cypress End-to-End Testing RulesQA and frontend teams that want consistent end-to-end tests for their main user flows.RecommendedRules file
  35. 035Cypress Integration Testing RulesQA and development teams that want integration tests between the interface and the API written consistently.RecommendedRules file
  36. 036Database Best Practices Rules (Prisma and Supabase)Development teams building on Prisma or Supabase that want consistent database code from the AI editor.RecommendedRules file
  37. 037Deno Integration Techniques RulesDevelopment teams maintaining automation scripts for the @findhow package ecosystem.RecommendedRules file
  38. 038Docker RulesDevelopment and operations teams that want consistent, secure Dockerfiles and compose files.RecommendedRules file
  39. 039DragonRuby Best Practices RulesDevelopment teams building games with the DragonRuby Game Toolkit who want consistent Ruby code from the AI editor.RecommendedRules file
  40. 040Drupal 11 Development RulesWeb development teams building Drupal 11 sites and modules who want standards-aligned code from the AI editor.RecommendedRules file
  41. 041Elixir Engineer GuidelinesDevelopment teams building Phoenix applications who want Cursor to follow one stack and one commit style.RecommendedRules file
  42. 042Elixir Phoenix Docker Setup RulesDevelopment teams working on Phoenix apps in Docker who want a consistent way of working with the AI assistant.RecommendedRules file
  43. 043Embedded STM32 HAL RulesEmbedded and hardware engineering teams writing STM32 firmware who want consistent AI help on drivers and interrupt code.RecommendedRules file
  44. 044Engineering Ticket TemplateProduct and engineering teams that want tickets written in one clear structure before work goes into a sprint.RecommendedRules file
  45. 045ES Module Node.js GuidelinesJavaScript development teams who want short, modular Node.js code from their AI assistant with consistent comments.RecommendedRules file
  46. 046FastAPI Production Architecture RulesBackend development teams building FastAPI services who want the AI to respect clear layer boundaries.RecommendedRules file
  47. 047FastAPI Best Practices RulesBackend development teams starting or maintaining FastAPI projects who want shared conventions for AI-assisted coding.RecommendedRules file
  48. 048Flutter App Expert RulesMobile development teams building Flutter apps who want the AI to follow a clean architecture with BLoC.RecommendedRules file
  49. 049Flutter Development GuidelinesMobile development teams who want one code style and folder layout for Flutter apps built with AI assistance.RecommendedRules file
  50. 050Flutter Riverpod RulesMobile development teams working in Flutter who want the AI to plan and avoid duplicate code before implementing.RecommendedRules file
  51. 051Fortran Programming GuidelinesEngineering and research teams that maintain Fortran code and want the AI editor to follow one consistent style.RecommendedRules file
  52. 052GameMaker GML RulesGame development teams working in GameMaker who want the AI editor to follow clear structure and performance habits.RecommendedRules file
  53. 053Gherkin Style TestingQA and product teams that need test scenarios written in plain language so non-technical colleagues can review them.RecommendedRules file
  54. 054Git Conventional Commit MessagesDevelopment teams that want commit messages written in one consistent format, which helps with release notes and versioning.RecommendedRules file
  55. 055Gitflow Workflow RulesDevelopment teams that follow Gitflow and want the AI editor to respect branch rules and naming when it helps with Git tasks.RecommendedRules file
  56. 056GitHub Code Quality RulesDevelopment teams that want the AI editor to stay focused, make small reviewable changes and avoid unrequested edits.RecommendedRules file
  57. 057Clean Code InstructionsDevelopment teams that want the AI editor to write code that colleagues can read and maintain easily.RecommendedRules file
  58. 058Go Backend ScalabilityBackend engineering teams that want an AI pair programmer for architecture and performance questions.RecommendedRules file
  59. 059Go ServeMux REST APIBackend teams building Go APIs on the standard library who want complete, consistent code from the AI editor.RecommendedRules file
  60. 060Go Temporal DSL Prompt FileBackend teams working with Go and Temporal who want to check whether this rules file fits their project.RecommendedRules file
  61. 061Go Rules for CursorDevelopment teams writing Go services who want Cursor to follow the same conventions on every suggestion.RecommendedRules file
  62. 062Google ADK Rules for CursorDevelopment teams building AI agents with Google ADK who want consistent structure for agents, tools and state.RecommendedRules file
  63. 063Graphical LLM Apps with Pyllments RulesDevelopment teams building LLM applications in Python with Pyllments who want Cursor to understand its component model.RecommendedRules file
  64. 064HarmonyOS ArkTS Rules for CursorMobile development teams building HarmonyOS apps who want Cursor to generate ArkTS components in a consistent style.RecommendedRules file
  65. 065Helium MCP Rules for CursorAnalysts and finance teams who want Cursor to pull news and market data from a tool instead of inventing it.RecommendedRules file
  66. 066Hashgraph Online TypeScript Rules for CursorDevelopment teams building AI agents and decentralized apps on Hedera who want Cursor to follow a strict TypeScript style.RecommendedRules file
  67. 067How-To Documentation Writer RulesSupport and product teams who turn feature notes, test scripts or screenshots into user-friendly guides.RecommendedRules file
  68. 068HTML, Tailwind CSS and JavaScript RulesFront-end and web teams building pages with plain HTML, Tailwind and JavaScript who want short, complete answers from Cursor.RecommendedRules file
  69. 069HTMX Basic Setup Rules for CursorWeb development teams building server-rendered pages with HTMX who want Cursor to use its attributes correctly.RecommendedRules file
  70. 070HTMX with Django Rules for CursorPython web teams building Django applications with HTMX who want Cursor to follow Django conventions.RecommendedRules file
  71. 071HTMX with Flask rules for CursorDevelopment teams building server-rendered web apps with Flask and HTMX who want Cursor to follow one consistent structure.RecommendedRules file
  72. 072HTMX with Go (basic setup) rules for CursorDevelopment teams building lightweight server-rendered web apps in Go with HTMX who want Cursor to write idiomatic code.RecommendedRules file
  73. 073HTMX with Go and Fiber rules for CursorDevelopment teams building HTMX web apps on Go and Fiber who want Cursor to follow Fiber conventions.RecommendedRules file
  74. 074Java general purpose rules for CursorJava development teams that want Cursor to write code following a shared set of design principles and a defined library stack.RecommendedRules file
  75. 075Java Spring Boot JPA rules for CursorBackend teams building Spring Boot services with JPA who want Cursor to respect a clear controller, service and repository layering.RecommendedRules file
  76. 076Astro with Tailwind CSS rules for CursorWeb development teams building content-focused sites with Astro who want Cursor to follow Astro conventions.RecommendedRules file
  77. 077Chrome extension development rules for CursorDevelopment teams building internal or public Chrome extensions who want Cursor to follow Chrome extension practices.RecommendedRules file
  78. 078JavaScript and TypeScript code quality rules for CursorDevelopment teams that want Cursor to produce consistent, readable JavaScript and TypeScript across a shared codebase.RecommendedRules file
  79. 079Jest unit testing rules for CursorDevelopment and QA teams that want Cursor to write focused, maintainable Jest unit tests.RecommendedRules file
  80. 080Knative, Istio, Typesense and GPU rules for CursorPlatform and development teams building serverless search applications on Knative and Istio who want Cursor to assist across the whole stack.RecommendedRules file
  81. 081Kotlin Ktor Development RulesDevelopment teams building Ktor backends who want the AI editor to follow one consistent project structure.RecommendedRules file
  82. 082Kotlin Spring Boot Best PracticesDevelopment teams working on Spring Boot services in Kotlin who want the AI editor to follow shared conventions.RecommendedRules file
  83. 083Kubernetes MkDocs Documentation RulesPlatform and operations teams who write and maintain Kubernetes documentation with MkDocs.RecommendedRules file
  84. 084KubeStellar Console Development RulesDevelopers contributing to the KubeStellar Console who want the AI editor to follow the project's conventions.RecommendedRules file
  85. 085Landing Page Image Quality RulesWeb and marketing teams building landing pages who want the AI editor to avoid placeholder and low-quality images.RecommendedRules file
  86. 086Laravel PHP 8.3 Package Development RulesPHP development teams who build reusable Laravel packages and want the AI editor to plan and structure them consistently.RecommendedRules file
  87. 087Laravel TALL Stack Best PracticesDevelopment teams building web applications on the TALL stack who want the AI editor to follow Laravel conventions.RecommendedRules file
  88. 088Linux NVIDIA CUDA Python RulesData and machine learning teams who maintain model quantization pipelines on Linux servers.RecommendedRules file
  89. 089Manifest Backend YAML RulesDevelopment and product teams who want to prototype a demo backend quickly with Manifest.RecommendedRules file
  90. 090Medusa Development RulesE-commerce development teams building on Medusa who want the AI editor to follow its workflow and data model conventions.RecommendedRules file
  91. 091Medusa rules for CursorDevelopment teams building commerce backends with Medusa who want Cursor to follow the framework's conventions.RecommendedRules file
  92. 092Momen.app frontend rules for CursorDevelopment teams that use Momen.app as their backend and build a custom frontend on top of it.RecommendedRules file
  93. 093NativeScript rules for CursorMobile development teams building NativeScript apps who want consistent AI-generated code.RecommendedRules file
  94. 094NativeScript best practices for CursorMobile development teams working on NativeScript apps for both iOS and Android.RecommendedRules file
  95. 095NestJS anti-hallucination rules for CursorBackend teams building NestJS services who want AI-generated code to use real, current packages.RecommendedRules file
  96. 096Netlify official rules for CursorWeb development teams deploying sites and functions on Netlify.RecommendedRules file
  97. 097Network troubleshoot rules for CursorDevelopers and IT support teams who need safe, step-by-step diagnosis of connection errors in package managers, Git or APIs.RecommendedRules file
  98. 098Next.js TypeScript LLM app rules for CursorDevelopment teams building a Next.js web app that connects to an LLM through a Python backend.RecommendedRules file
  99. 099Next.js App Router rules for CursorWeb development teams building Next.js sites with the App Router.RecommendedRules file
  100. 100Next.js, Material UI and Tailwind project rulesWeb development teams who want Cursor to know the stack and setup choices of a Next.js portfolio project.RecommendedRules file
  101. 101Next.js, React and Tailwind rules for CursorDevelopment teams that want Cursor to write consistent Next.js and Tailwind code that follows one house style.RecommendedRules file
  102. 102Next.js, React and TypeScript rules with Web3 stackDevelopment teams building web3 front ends with Next.js who want Cursor to follow one set of coding and error handling conventions.RecommendedRules file
  103. 103Next.js SEO dev rules for CursorDevelopment teams that want Cursor to comment its changes clearly and protect specific lines in a Next.js codebase.RecommendedRules file
  104. 104Next.js, Supabase, Shadcn and PWA rules for CursorDevelopment teams that want Cursor to keep small modular files and a written trail of decisions while building a Next.js app.RecommendedRules file
  105. 105Next.js and Supabase todo app rules for CursorDevelopment teams or learners who want a starting rules file for a small todo app built with Next.js and Supabase.RecommendedRules file
  106. 106Next.js, Tailwind and TypeScript assistant rulesDevelopment teams that want Cursor to plan before coding and deliver finished, readable Next.js code.RecommendedRules file
  107. 107Next.js App Router and TanStack Query v5 rulesDevelopment teams that want Cursor to split data fetching correctly between server and client components in a Next.js app.RecommendedRules file
  108. 108Next.js and TanStack Query rules, compact versionDevelopment teams that want Cursor to apply server prefetching and client-side queries consistently in a Next.js app.RecommendedRules file
  109. 109Next.js and TypeScript app rules for Astral explorerDevelopment teams that want a model for giving Cursor a brief project description for a Next.js and TypeScript application.RecommendedRules file
  110. 110Next.js and TypeScript rules with LLM backendDevelopment teams building a Next.js front end that talks to a Python LLM backend and want Cursor to follow one working process.RecommendedRules file
  111. 111Next.js, TypeScript and Tailwind Cursor rulesDevelopment teams that want Cursor to write consistent Next.js and TypeScript code that follows their project conventions.RecommendedRules file
  112. 112Next.js, Vercel and Supabase Cursor rules (BA Copilot)Product and development teams building an AI chat tool for business analysts that works with process diagrams.RecommendedRules file
  113. 113Next.js, Vercel and TypeScript Cursor rulesDevelopment teams building AI-driven Next.js interfaces on Vercel who want Cursor to follow consistent code conventions.RecommendedRules file
  114. 114Next.js best practices Cursor rulesDevelopment teams that want Cursor to follow common Next.js App Router practices in any project.RecommendedRules file
  115. 115Next.js 15, React 19 and Vercel AI SDK Cursor rulesDevelopment teams building modern Next.js apps with AI features who want Cursor to plan before it writes code.RecommendedRules file
  116. 116Next.js 15 and Supabase architecture Cursor rulesDevelopment teams building Next.js 15 apps on Supabase who want Cursor to avoid common auth and routing mistakes.RecommendedRules file
  117. 117Node.js and Express best practices Cursor rulesBack-end development teams that want Cursor to follow common Node.js and Express practices when building APIs.RecommendedRules file
  118. 118Node.js and MongoDB Cursor rules tutorialDevelopment teams building a Node.js and MongoDB application who want Cursor to plan with pseudocode before writing code.RecommendedRules file
  119. 119Node.js, MongoDB, JWT, Express and React Cursor rulesFull stack development teams building a MERN-style application who want Cursor to follow a defined stack and workflow.RecommendedRules file
  120. 120DRY and SOLID principles Cursor rulesDevelopment teams that want Cursor to apply DRY and SOLID principles and keep changes clear and easy to place.RecommendedRules file

Questions
people ask.

Where do Cursor rules go?

Project rules live in the .cursor/rules folder as .mdc files. Older projects use a single .cursorrules file in the root, which Cursor still reads.

Is it safe to install what I find here?

Every listed item passed an automatic scan for credential theft, hidden instructions to the AI and risky install commands, and comes from a licensed, active project. That lowers the risk but does not remove it. Read the code and check the permissions before you connect anything to company data.

Know a resource that belongs here?

Send us the link. We run the same checks and add it if it passes.

Submit a resource ↗