Awesome Cursor Rules Curated Resource and Installation Guide CookApps CookApps Marketplace

CookApps

Fine Software Cuisine

CookApps Fine Software Cuisine

awesome-cursorrules is the definitive open-source catalog of production-tested prompt engineering rules, architectural context definitions, and coding constraints designed specifically for Cursor IDE, Windsurf, and modern AI coding assistants.

As AI coding models grow in reasoning capability, the primary bottleneck in software delivery is context drift: models inventing deprecated syntax, mixing incompatible design paradigms, omitting strict TypeScript checks, or violating project-specific directory structures. awesome-cursorrules solves this by establishing deterministic project rules that keep agentic workflows grounded, strict, and aligned with your team's engineering standards.

The Evolution: Monolithic .cursorrules to Modular .mdc Rules

Modern Cursor releases support two distinct rule architectures:

Root .cursorrules: A single markdown file positioned at the repository root. Best for general repository policies, global tech stack definitions, package manager declarations, and universal coding ethics.

Modular .cursor/rules/*.mdc: Specialized, frontmatter-driven rules with glob targeting (globs: "**/*.tsx" or "src/api/**/*.ts"). These rules load on demand only when the AI edits or generates code matching the specified file patterns, drastically reducing token consumption and preventing context overflow.

Curated Rule Categories & Best Practices

Modern Frontend Architecture

Next.js App Router: Enforces React Server Components (RSC) by default, strict boundary placement for 'use client', atomic Server Actions, and dynamic metadata configuration.

React 19 & State Management: Mandates hook guidelines, prevents unnecessary useEffect patterns, and guides integration with Zustand or TanStack Query.

Tailwind CSS & Design Systems: Prohibits arbitrary hex values, enforces semantic color tokens, and ensures responsive, mobile-first class ordering.

Type Safety & API Design

TypeScript Strict Mode: Forbids the use of any and unconstrained unknown. Requires discriminated unions, exhaustive switch checking, and precise function return signatures.

Schema Validation: Mandates runtime validation using Zod or Valibot at all system boundaries (API endpoints, environment variables, and form inputs).

Error Handling: Requires typed Result objects or domain-specific custom error hierarchies rather than generic untyped rejections.

Backend & Data Persistence

Database ORMs: Best-practice patterns for Prisma ORM, Drizzle, and Kysely. Enforces atomic transactions (prisma.$transaction), indexing awareness, and prevention of N+1 query loops.

Server Frameworks: Clean architecture templates for Fastify, NestJS, Go (Gin/Chi), Rust (Axum), and Python (FastAPI).

Testing & Code Quality

Automated Testing: Test-driven development (TDD) rules for Vitest, Jest, and Playwright. Requires arrange-act-assert structure and mocks only at network boundaries.

Clean Code Standards: Single Responsibility Principle, small focused files (<250 lines), descriptive naming conventions, and self-documenting code.

# ================================================================ # CookApps Guide: Implementing Production Cursor Rules # ================================================================ # Approach A: Modular .mdc Rules (Recommended for Modern Cursor) # ---------------------------------------------------------------- # Create a dedicated rules directory in your project root: mkdir -p .cursor/rules # 1. Create a Frontend Rule: .cursor/rules/react-nextjs.mdc cat << 'EOF' > .cursor/rules/react-nextjs.mdc --- description: Next.js App Router and React 19 architecture rules globs: apps/web/**/*.{ts,tsx} alwaysApply: false --- # Next.js & React 19 Standards - Server Components by default. Use 'use client' only for leaf components requiring state or event handlers. - Data Fetching: Fetch database records directly in Server Components via Prisma; do not create internal API routes for server-side page loads. - Styling: Use semantic Tailwind utility classes matching the design system. Never use inline style tags. - Images: Always specify explicit width, height, and priority loading for Above-the-Fold images. EOF # 2. Create a TypeScript Rule: .cursor/rules/typescript-strict.mdc cat << 'EOF' > .cursor/rules/typescript-strict.mdc --- description: Strict TypeScript typing and error handling globs: **/*.{ts,tsx} alwaysApply: true --- # TypeScript Standards - Never use 'any'. Use 'unknown' with type narrowing or generic constraints. - Explicit return types are required on all exported functions and API routes. - Use discriminated unions for complex state representations. - All external API inputs must be validated with Zod schemas. EOF # Approach B: Root .cursorrules (Universal Stack Guide) # ---------------------------------------------------------------- # For projects preferring a single root configuration, place in repo root: cat << 'EOF' > .cursorrules # Project: CookApps Production Standards Stack: Next.js 14 App Router, TypeScript 5, Tailwind CSS, Prisma, PostgreSQL ## Core Behavioral Guidelines 1. Read Before Write: Always view existing component and type definitions before editing. 2. Verification Pipeline: Run 'node apps/web/node_modules/typescript/bin/tsc --noEmit' after every modification. 3. Clean Architecture: Keep business logic separated from presentation components. 4. Security: Never expose private API keys in client components. Ensure all sensitive mutations require server-side authentication. EOF # Verification: # In Cursor Composer (Cmd+I / Ctrl+I), notice the active rules tag at the top of the chat bar. # Prompt your assistant: "Create a new checkout button component following our design standards."

Awesome Cursor Rules

The Evolution: Monolithic .cursorrules to Modular .mdc Rules

Curated Rule Categories & Best Practices

How to Use & Getting Started

Ready to explore Awesome Cursor Rules?

More in code

Frontend Design

Awesome Shell

Code Reviewer