Repository-aware · Not template-based · Engineering-first

Generate AI-Native Repository Rules

Generate Cursor Project Rules (.mdc), AGENTS.md, CLAUDE.md and repository standards automatically.

Generate Rules on RepoRules.dev See Real Examples

package.json → standards

// Input
{
  "next": "^15.0",
  "react": "^19.0",
  "prisma": "^6.0",
  "zod": "^3.23"
}

// Detected
Next.js 15 → App Router
Prisma 6 → ORM

// Standards
Prefer Server Components
Use Prisma transactions
Validate with Zod

Cursor Now Uses Project Rules (.mdc)

Cursor has deprecated .cursorrules in favor of .cursor/rules/*.mdc files. Project Rules are now split by file type and stored in a rules directory.

Learn How to Migrate →

What Happens Without Repository Rules

Without Rules

AI generates inconsistent code across sessions
No shared architecture conventions
Validation and error handling vary per prompt
File structure drifts over time
Each developer invents their own patterns

With Rules

AI follows project-specific architecture standards
Shared conventions enforced across all sessions
Consistent validation and error handling patterns
Predictable file structure and naming
Team-wide coding standards, auto-enforced

How it works

Input

Your package.json

{
  "next": "^15.0",
  "react": "^19.0",
  "tailwindcss": "^4.0",
  "prisma": "^6.0",
  "zod": "^3.23"
}

Detected

Next.js 15 · React 19 · Tailwind v4 · Prisma · Zod

- App Router with Server Components
- ORM: Prisma with PostgreSQL
- Validation: Zod schemas
- Styling: Tailwind CSS v4

Generated Standards

Prefer Server Components by default. Only add 'use client' when using hooks or event handlers.
Never fetch in client components. Fetch data in Server Components, pass as props.
Wrap Server Actions in Prisma transactions. Use interactive transactions for multi-table writes.
Validate all external input with Zod. Define schemas in lib/schemas/, reuse across routes and actions.

Generate Repository Rules