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: Expo and React Native conventions
globs: app/**/*.tsx, app/**/*.ts, src/**/*.tsx, src/**/*.ts, components/**/*.tsx, app.json, app.config.ts
alwaysApply: false
---

- Use Expo Router file-based routes in the app directory, with _layout.tsx for stacks and tabs. Do not set up a separate navigation container.
- Import navigation APIs (Link, Stack, Tabs, useRouter, useLocalSearchParams) from expo-router, not @react-navigation/*.
- Install packages with npx expo install so versions match the SDK.
- Change native configuration in app.json or app.config.ts and config plugins, not by editing generated ios/ and android/ folders.
- Use components from react-native, not web elements like div or span; all text goes inside <Text>.
- Use Pressable for touch targets and FlatList (or the project's list library) for long lists, not ScrollView with map.
- Handle safe areas with react-native-safe-area-context.
- EXPO_PUBLIC_ variables are bundled into the app; never put secrets in them. Store tokens with expo-secure-store, not AsyncStorage.
- Run npx expo-doctor and the type checker before finishing.

Rule name (used for the file name)

Scope: Only for matching files (app/**/*.tsx, app/**/*.ts, src/**/*.tsx, src/**/*.ts, components/**/*.tsx, app.json, app.config.ts)

Detected from: globs

Convert to

Save as: .cursor/rules/react-native-expo.mdc

---
globs: app/**/*.tsx, app/**/*.ts, src/**/*.tsx, src/**/*.ts, components/**/*.tsx, app.json, app.config.ts
alwaysApply: false
---

- Use Expo Router file-based routes in the app directory, with _layout.tsx for stacks and tabs. Do not set up a separate navigation container.
- Import navigation APIs (Link, Stack, Tabs, useRouter, useLocalSearchParams) from expo-router, not @react-navigation/*.
- Install packages with npx expo install so versions match the SDK.
- Change native configuration in app.json or app.config.ts and config plugins, not by editing generated ios/ and android/ folders.
- Use components from react-native, not web elements like div or span; all text goes inside <Text>.
- Use Pressable for touch targets and FlatList (or the project's list library) for long lists, not ScrollView with map.
- Handle safe areas with react-native-safe-area-context.
- EXPO_PUBLIC_ variables are bundled into the app; never put secrets in them. Store tokens with expo-secure-store, not AsyncStorage.
- Run npx expo-doctor and the type checker 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