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: SvelteKit and Svelte 5 runes conventions
globs: src/**/*.svelte, src/**/*.svelte.ts, src/routes/**/*.ts
alwaysApply: false
---

- Use runes: $state for reactive state, $derived for computed values, $props() for props and $bindable() for two-way props. Do not use export let or $: statements.
- Use $effect only for side effects such as DOM or third-party calls; never use it to sync one piece of state into another.
- Use event attributes (onclick, oninput), not on:click directives. Pass callback props instead of createEventDispatcher.
- Use snippets and {@render ...} instead of slots.
- Put shared reactive state in .svelte.ts modules, not writable stores.
- Load page data in +page.ts or +page.server.ts load functions, not in onMount.
- Keep secrets, database clients and private env vars in server-only files (+page.server.ts, +server.ts, hooks.server.ts).
- Handle form submissions with form actions in +page.server.ts and progressive enhancement via use:enhance.
- Read the current page, params and URL from page in $app/state, not $app/stores.

Rule name (used for the file name)

Scope: Only for matching files (src/**/*.svelte, src/**/*.svelte.ts, src/routes/**/*.ts)

Detected from: globs

Convert to

Save as: .cursor/rules/sveltekit.mdc

---
globs: src/**/*.svelte, src/**/*.svelte.ts, src/routes/**/*.ts
alwaysApply: false
---

- Use runes: $state for reactive state, $derived for computed values, $props() for props and $bindable() for two-way props. Do not use export let or $: statements.
- Use $effect only for side effects such as DOM or third-party calls; never use it to sync one piece of state into another.
- Use event attributes (onclick, oninput), not on:click directives. Pass callback props instead of createEventDispatcher.
- Use snippets and {@render ...} instead of slots.
- Put shared reactive state in .svelte.ts modules, not writable stores.
- Load page data in +page.ts or +page.server.ts load functions, not in onMount.
- Keep secrets, database clients and private env vars in server-only files (+page.server.ts, +server.ts, hooks.server.ts).
- Handle form submissions with form actions in +page.server.ts and progressive enhancement via use:enhance.
- Read the current page, params and URL from page in $app/state, not $app/stores.

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