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: Nuxt app conventions
globs: **/*.vue, app/**/*.ts, server/**/*.ts, nuxt.config.ts
alwaysApply: false
---

- Rely on auto-imports for Vue APIs, Nuxt composables, components and files in composables/ and utils/. Do not add manual imports for them.
- Fetch data for rendering with useFetch or useAsyncData so it runs once on the server and hydrates on the client. Use $fetch only in event handlers and server code.
- useFetch and useAsyncData return refs: handle status and error, and do not assume data is set on first render.
- Put API endpoints in server/api using defineEventHandler. Validate input with readValidatedBody or getValidatedQuery.
- Share state with useState or a Pinia store, never a module-level ref; module state leaks between requests on the server.
- Read config with useRuntimeConfig(). Only runtimeConfig.public reaches the browser, so keep secrets out of it.
- Use <NuxtLink> for internal links and navigateTo() for programmatic navigation.
- Set head tags with useSeoMeta or useHead, and layout or middleware with definePageMeta.
- Keep browser-only code in onMounted, <ClientOnly> or .client.vue files.

Rule name (used for the file name)

Scope: Only for matching files (**/*.vue, app/**/*.ts, server/**/*.ts, nuxt.config.ts)

Detected from: globs

Convert to

Save as: .cursor/rules/nuxt.mdc

---
globs: **/*.vue, app/**/*.ts, server/**/*.ts, nuxt.config.ts
alwaysApply: false
---

- Rely on auto-imports for Vue APIs, Nuxt composables, components and files in composables/ and utils/. Do not add manual imports for them.
- Fetch data for rendering with useFetch or useAsyncData so it runs once on the server and hydrates on the client. Use $fetch only in event handlers and server code.
- useFetch and useAsyncData return refs: handle status and error, and do not assume data is set on first render.
- Put API endpoints in server/api using defineEventHandler. Validate input with readValidatedBody or getValidatedQuery.
- Share state with useState or a Pinia store, never a module-level ref; module state leaks between requests on the server.
- Read config with useRuntimeConfig(). Only runtimeConfig.public reaches the browser, so keep secrets out of it.
- Use <NuxtLink> for internal links and navigateTo() for programmatic navigation.
- Set head tags with useSeoMeta or useHead, and layout or middleware with definePageMeta.
- Keep browser-only code in onMounted, <ClientOnly> or .client.vue files.

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