cursor-rules

⚡ Cursor Rules Pack — Community Edition

Production-quality Cursor AI rules for modern TypeScript projects. Drop in a single file. Ship better code instantly.

🚀 Quick Start · 📦 Included Rules · 💎 Premium Pack · 🤝 Contributing

What is this?

This is a curated set of .cursorrules files that teach Cursor AI how to write idiomatic, production-ready code for the most popular TypeScript frameworks and tools. Stop wrestling with AI that doesn't understand your stack — these rules encode real-world best practices so Cursor writes code that actually belongs in your codebase.

Each rule file is self-contained, framework-specific, and immediately usable. Copy one file into your project root and your AI coding experience upgrades instantly.

Quick Start

Option 1 — Copy a single file (30 seconds)

# Next.js project
curl -o .cursorrules https://raw.githubusercontent.com/GoodEpochHQ/cursor-rules/main/rules/nextjs.mdc

# React project
curl -o .cursorrules https://raw.githubusercontent.com/GoodEpochHQ/cursor-rules/main/rules/react.mdc

# Node/Express API
curl -o .cursorrules https://raw.githubusercontent.com/GoodEpochHQ/cursor-rules/main/rules/nodejs.mdc

Option 2 — Clone and use the combine script

git clone https://github.com/GoodEpochHQ/cursor-rules.git
cd cursor-rules

# Combine multiple rules into one custom .cursorrules file
./scripts/combine.sh nextjs react typescript > /your/project/.cursorrules

Option 3 — Browse and copy manually

Browse the /rules directory, find your framework, copy the contents into your project's .cursorrules file.

That's it. Restart Cursor and your AI assistant now understands your stack at a deeper level.

Included Rules

All files in this repo are MIT licensed and free forever.

Quick Picks by Project Type

💎 Want More? The Premium Pack

The Community Edition covers the most popular individual frameworks. The GoodEpoch Cursor Rules Premium Pack goes much deeper:

What's in the Premium Pack

Why Pay?

• Stack rules = 10x the value — instead of mixing rules yourself, get pre-tuned combinations that don't conflict
• Concern rules = features you ship correctly the first time — auth, payments, and file uploads done right
• Style profiles = team alignment — everyone's AI outputs the same style before code review
• One-time purchase, lifetime updates — every rule update ships to you automatically

→ Get the Premium Pack on Gumroad — Pay once, use forever.

How Cursor Rules Work

Cursor reads a .cursorrules file (or .cursor/rules/*.mdc files) in your project root and uses the contents as persistent instructions for every AI interaction in that project.

Without rules: Cursor uses generic coding knowledge. With rules: Cursor knows your exact patterns, conventions, and preferences — and applies them consistently.

your-project/
├── .cursorrules          ← Cursor reads this automatically
├── src/
├── package.json
└── ...

Or with the newer MDC format (recommended for Cursor 0.40+):

your-project/
├── .cursor/
│   └── rules/
│       ├── global.mdc    ← Always applied
│       ├── nextjs.mdc    ← Applied to matching files
│       └── ...
├── src/
└── ...

Contributing

Community contributions for framework rules are very welcome. The goal is to have the best free cursor rules for every major TypeScript framework.

What we'd love to see

• Rules for frameworks not yet covered (SvelteKit, Astro, Hono, Fastify, tRPC, Drizzle ORM, etc.)
• Improvements to existing rules based on framework updates
• Bug fixes for rules that generate bad patterns

How to contribute

1. Fork the repo
2. Create a branch: git checkout -b rules/sveltekit
3. Add your rule file to /rules/ following the rule format guide
4. Test it against real Cursor prompts and document what it improves
5. Open a PR with examples of before/after AI output

Rule quality bar

We maintain a quality bar to keep rules genuinely useful:

• ✅ Based on official framework docs and real-world patterns
• ✅ Tested in Cursor against common prompts
• ✅ Includes brief inline comments explaining non-obvious guidance
• ❌ No vendor-specific opinions without community backing
• ❌ No rules that conflict with framework best practices

See CONTRIBUTING.md for the full guide.

Rule Format

Rules use Cursor's MDC format. Each file follows this structure:

---
description: Brief description of what this rule covers
globs: ["**/*.ts", "**/*.tsx"]   # Files this rule applies to
alwaysApply: false                # true for global rules
---

# Rule Name

Brief explanation of why this rule exists.

## Core Principles

- Principle 1
- Principle 2

## Patterns

### Do this
\`\`\`typescript
// good example
\`\`\`

### Not this
\`\`\`typescript
// bad example
\`\`\`

Changelog

License

MIT © GoodEpoch

Free to use, modify, and distribute. Attribution appreciated but not required.

Built with ❤️ by GoodEpoch

⭐ Star this repo if it saved you time · 💎 Upgrade to Premium · 🐛 Report an Issue