Free tool

Rules file converter

Write a rule once and use it in every coding agent your team runs. Paste a rule in any agent's format and get the file path and frontmatter for 11 targets, keeping when the rule applies. Formats checked against each vendor's docs on 2026-10-19. Nothing leaves your browser.

Your rule (any agent's format, frontmatter included)

---
description: Prisma schema and client conventions
globs: **/*.prisma, prisma.config.ts
alwaysApply: false
---

- Use the prisma-client generator with an explicit output path, and import the client from that path, not from @prisma/client in node_modules.
- Put the database URL and migration settings in prisma.config.ts; it does not load .env automatically, so load it yourself.
- Create the client with the driver adapter for your database (for example @prisma/adapter-pg).
- Run prisma generate after every schema change; migrate dev does not run it for you.
- Use prisma migrate dev to create migrations and prisma migrate deploy in production. Use db push only for throwaway prototypes.
- Never edit a migration that has already been applied; create a new one.
- Create one shared PrismaClient instance and reuse it; never create a client per request.
- Select only the fields you need with select, and use include deliberately to avoid huge payloads.
- Group dependent writes in prisma.$transaction, and add @@index on foreign key fields you filter or join on.

Rule name (used for the file name)

Scope: Only for matching files (**/*.prisma, prisma.config.ts)

Detected from: globs

Convert to

Save as: .cursor/rules/prisma.mdc

---
globs: **/*.prisma, prisma.config.ts
alwaysApply: false
---

- Use the prisma-client generator with an explicit output path, and import the client from that path, not from @prisma/client in node_modules.
- Put the database URL and migration settings in prisma.config.ts; it does not load .env automatically, so load it yourself.
- Create the client with the driver adapter for your database (for example @prisma/adapter-pg).
- Run prisma generate after every schema change; migrate dev does not run it for you.
- Use prisma migrate dev to create migrations and prisma migrate deploy in production. Use db push only for throwaway prototypes.
- Never edit a migration that has already been applied; create a new one.
- Create one shared PrismaClient instance and reuse it; never create a client per request.
- Select only the fields you need with select, and use include deliberately to avoid huge payloads.
- Group dependent writes in prisma.$transaction, and add @@index on foreign key fields you filter or join on.

Format source: Cursor docs.

How scope maps between agents

When it applies	Cursor .mdc	Claude Code	GitHub Copilot	Kiro	Antigravity / Devin
Always on	alwaysApply: true	no paths	applyTo: "**"	inclusion: always	trigger: always_on
Matching files	globs	paths	applyTo	inclusion: fileMatch	trigger: glob
Agent decides	description	(use a Skill)	description (VS Code)	inclusion: auto	trigger: model_decision
Manual	no description, no globs	(use a Skill)	neither (VS Code)	inclusion: manual	trigger: manual

AGENTS.md, GEMINI.md and Codex have no frontmatter: put the file in the folder it applies to. Zed reads only the first instruction file it finds, so a .cursorrules file wins over AGENTS.md there.

Rules formats keep changing

Get one email a week when a coding agent changes where it reads rules or how it scopes them.

How scope maps between agents

Related