About Cursor Rules Hub

An independent community platform for sharing and discovering Cursor rules. Built by developers, for developers - not affiliated with Cursor but passionate about helping the community.

What are Cursor Rules?

Cursor rules are system-level instructions that control how the Agent model behaves. They provide persistent, reusable context at the prompt level, giving the AI consistent guidance for generating code, interpreting edits, or helping with workflows.

Think of them as persistent context, preferences, or workflows for your projects - they're included at the start of the model context to provide consistent guidance.

🤖

System-Level Instructions

Control how the Agent model behaves with reusable, scoped instructions that apply to Chat and Inline Edit.

Why Use Cursor Rules?

🚀

Boost Productivity

Generate code that matches your team's patterns instantly. No more rewriting AI suggestions to match your coding standards.

🎯

Maintain Consistency

Keep your codebase consistent across all developers and projects. Rules ensure everyone on your team follows the same patterns.

🧠

Learn Best Practices

Share and discover proven patterns from experienced developers. Learn from the community's collective knowledge.

Faster Onboarding

New team members can instantly adopt your project's conventions by using the same rules. Reduce ramp-up time significantly.

Types of Cursor Rules

Project Rules

Stored in .cursor/rules, version-controlled and scoped to your codebase.

  • • Encode domain-specific knowledge
  • • Automate project-specific workflows
  • • Standardize style decisions

User Rules

Global preferences defined in Cursor Settings → Rules that apply across all projects.

  • • Plain text format
  • • Communication style preferences
  • • Coding conventions

.cursorrules (Legacy)

Still supported but deprecated. Use Project Rules instead for more control and flexibility.

  • • File in project root
  • • Limited functionality
  • • Migration recommended

How Do Cursor Rules Work?

1

Rule Types & Application

Rules can be Always (always included), Auto Attached (applied to matching glob patterns),Agent Requested (AI decides when to include), or Manual (explicitly mentioned with @ruleName).

2

Project Rules Location

Project rules live in .cursor/rules directory, are version-controlled, and can be scoped using path patterns, invoked manually, or included based on relevance.

3

Rule Anatomy

Rules are written in MDC format with metadata (description, globs, alwaysApply) and content. They can reference other files using @file syntax for additional context.

Example Rules

RPC Service Boilerplate

Use our internal RPC pattern when defining services. Always use snake_case for service names.

description: RPC Service boilerplate
globs: ["**/*.ts"]
alwaysApply: false
Referenced: @service-template.ts

User Rule Example

Global preferences defined in Cursor Settings → Rules that apply across all projects.

Please reply in a concise style. Avoid unnecessary repetition or filler language.

Getting Started

🎯

Ready to Create Your First Rule?

Start by creating a rule for your most common coding patterns. Think about the conventions your team follows and the patterns you want to enforce.

Why Share Rules with the Community?

🤝

Help Others

Share your expertise and help other developers learn from your experience and best practices.

💡

Discover New Patterns

Learn from the community and discover new coding patterns and best practices you might not have considered.

🚀

Build Together

Contribute to a growing library of proven patterns and coding standards that benefit everyone.

Built with expertise by Luis Lozoya

Senior Full Stack Engineer with extensive experience in building secure, high-performance web applications for businesses of all sizes

👨‍💻

Senior Full Stack Engineer

Building secure, high-performance web applications for businesses

🚀

Modern Technologies

React, Angular, Next.js, AWS, and cloud-native solutions

🎨

Security & DevOps

Cybersecurity, cloud security, and infrastructure expertise

About Me

I'm a Senior Full Stack Engineer with extensive experience in building secure, high-performance web applications for businesses of all sizes. Leveraging modern frameworks like React, Next.js, and AWS, I focus on creating user-friendly solutions that help companies thrive in today's digital landscape.

With a passion for full-stack development, I strive to implement impactful, transformative technologies and best practices that drive real-world results.

Tech Stack

React
Angular
Next.js
AWS
TypeScript
Supabase

This Project

  • • Community-driven platform
  • • Real-time notifications
  • • User authentication & profiles
  • • Social features (follows, likes)
  • • Admin dashboard
  • • Modern UI/UX design

Ready to Join the Community?

Start sharing your knowledge and help build the best Cursor rules community!