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: ASP.NET Core conventions
globs: **/*.cs, **/appsettings*.json
alwaysApply: false
---

- Follow the project's existing style: minimal APIs or controllers. Do not mix both in one feature.
- Register services in Program.cs and inject them through constructors; never new up services or use a static service locator.
- Use async all the way down and accept a CancellationToken; never call .Result or .Wait().
- Bind settings with the options pattern (IOptions<T>) and keep secrets in user secrets or environment variables, not appsettings.json.
- Return TypedResults or ActionResult<T>, and use AddProblemDetails for error responses.
- Use IHttpClientFactory or typed clients; never create a new HttpClient per request.
- Log with ILogger<T> and message templates ("Order {OrderId} failed"), not string interpolation.
- With EF Core, use AsNoTracking for read-only queries and change the schema only through dotnet ef migrations.
- Keep nullable reference types enabled and fix new warnings; run dotnet build and dotnet test before finishing.

Rule name (used for the file name)

Scope: Only for matching files (**/*.cs, **/appsettings*.json)

Detected from: globs

Convert to

Save as: .cursor/rules/dotnet.mdc

---
globs: **/*.cs, **/appsettings*.json
alwaysApply: false
---

- Follow the project's existing style: minimal APIs or controllers. Do not mix both in one feature.
- Register services in Program.cs and inject them through constructors; never new up services or use a static service locator.
- Use async all the way down and accept a CancellationToken; never call .Result or .Wait().
- Bind settings with the options pattern (IOptions<T>) and keep secrets in user secrets or environment variables, not appsettings.json.
- Return TypedResults or ActionResult<T>, and use AddProblemDetails for error responses.
- Use IHttpClientFactory or typed clients; never create a new HttpClient per request.
- Log with ILogger<T> and message templates ("Order {OrderId} failed"), not string interpolation.
- With EF Core, use AsNoTracking for read-only queries and change the schema only through dotnet ef migrations.
- Keep nullable reference types enabled and fix new warnings; run dotnet build and dotnet test before finishing.

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