svelte-migrate
Skill447 starsChanged 3 months agoMITView on GitHub
Migrate a Svelte 4 component to Svelte 5 runes syntax. Use when asked to migrate, convert, or upgrade a .svelte file to Svelte 5.
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 4 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
When the user provides a file path, migrate that specific file following the patterns below.
- Very specific: line 48
Only reactive variables that are reassigned or mutated need $state().
- Very specific: line 388
Use onMount for initialization logic that should only run once when the component first mounts
- Very specific: line 389
Use $effect for reactive side effects that should re-run when dependencies change
- Very specific: line 390
Never convert onMount to $effect unless the logic genuinely needs to be reactive
- Distinctive: line 470
Read the file to understand its current structure
- Distinctive: line 480
Update imports (add Snippet type if needed, remove createEventDispatcher if no longer used)
- Distinctive: line 481
Ensure TypeScript types are correct
- Very specific: line 482
Run pnpm check to verify no type errors
- Very specific: line 486
Keep onMount and onDestroy - they're still valid
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Svelte 4 to 5 Migration
Migrate individual Svelte files from v4 to v5 runes syntax.
Usage
When the user provides a file path, migrate that specific file following the patterns below.
Migration Patterns
1. Props: export let → $props()
Before:
<script lang="ts">
export let name: string;
export let count = 0;
export let optional: string | undefined = undefined;
let className = '';
export { className as class };
</script>After:
<script lang="ts">
interface Props {
name: string;
count?: number;
optional?: string;
class?: string;
}
let { name, count = 0, optional, class: className = '' }: Props = $props();
</script>2. State: let → $state()
Only reactive variables that are reassigned or mutated need $state().
Before:
<script lang="ts">
let count = 0;
let items = [];
</script>After:
<script lang="ts">
let count = $state(0);
let items = $state<string[]>([]);
</script>3. Derived Values: $: → $derived()
Before:
<script lang="ts">
$: doubled = count * 2;
$: filtered = items.filter((i) => i.active);
</script>After:
<script lang="ts">
const doubled = $derived(count * 2);
const filtered = $derived(items.filter((i) => i.active));
</script>For complex derivations use $derived.by():
Before:
<script lang="ts">
$: {
let total = 0;
for (const item of items) total += item.value;
sum = total;
}
</script>After:
<script lang="ts">
const sum = $derived.by(() => {
let total = 0;
for (const item of items) total += item.value;
return total;
});
</script>4. Side Effects: $: statements → $effect()
Before:
<script lang="ts">
$: console.log('count changed:', count);
$: if (count > 10) alert('High count!');
$: document.title = `Count: ${count}`;
</script>After:
<script lang="ts">
$effect(() => {
console.log('count changed:', count);
});
$effect(() => {
if (count > 10) alert('High count!');
});
$effect(() => {
document.title = `Count: ${count}`;
});
</script>5. Event Handlers: on:event → onevent
Before:
<button on:click={handleClick}>Click</button>
<button on:click={() => count++}>Increment</button>
<button on:click|preventDefault={submit}>Submit</button>
<input on:input={handleInput} on:focus={handleFocus} />After:
<button onclick={handleClick}>Click</button>
<button onclick={() => count++}>Increment</button>
<button
onclick={(e) => {
e.preventDefault();
submit(e);
}}>Submit</button
>
<input oninput={handleInput} onfocus={handleFocus} />Event modifiers like |preventDefault, |stopPropagation must be handled manually in the handler.
6. Component Events: createEventDispatcher → callback props
Before:
<script lang="ts">
import { createEventDispatcher } from 'svelte';
const dispatch = createEventDispatcher<{
change: string;
submit: { data: FormData };
}>();
function handleChange(value: string) {
dispatch('change', value);
}
</script>After:
<script lang="ts">
interface Props {
onchange?: (value: string) => void;
onsubmit?: (data: { data: FormData }) => void;
}
let { onchange, onsubmit }: Props = $props();
function handleChange(value: string) {
onchange?.(value);
}
</script>Parent component changes:
Before: <Child on:change={handler} />
After: <Child onchange={handler} />
7. Forwarding Events: on:event → explicit handler
Before:
<button on:click>Click me</button>After:
<script lang="ts">
interface Props {
onclick?: (e: MouseEvent) => void;
}
let { onclick }: Props = $props();
</script>
<button {onclick}>Click me</button>8. Slots → Snippets
Default slot:
Before:
<slot />After:
<script lang="ts">
import type { Snippet } from 'svelte';
interface Props {
children?: Snippet;
}
let { children }: Props = $props();
</script>
{@render children?.()}Named slots:
Before:
<slot name="header" />
<slot />
<slot name="footer" />After:
<script lang="ts">
import type { Snippet } from 'svelte';
interface Props {
header?: Snippet;
children?: Snippet;
footer?: Snippet;
}
let { header, children, footer }: Props = $props();
</script>
{@render header?.()}
{@render children?.()}
{@render footer?.()}Slots with props (let:):
Before:
<slot item={currentItem} index={i} />
<!-- Usage -->
<List {items} let:item let:index>
<span>{index}: {item.name}</span>
</List>After:
<script lang="ts">
import type { Snippet } from 'svelte';
interface Props {
children?: Snippet<[{ item: Item; index: number }]>;
}
let { children }: Props = $props();
</script>
{@render children?.({ item: currentItem, index: i })}
<!-- Usage -->
<List {items}>
{#snippet children({ item, index })}
<span>{index}: {item.name}</span>
{/snippet}
</List>9. Bindable Props: bind: → $bindable()
Before:
<script lang="ts">
export let value = '';
</script>
<!-- Parent -->
<Input bind:value={name} />After:
<script lang="ts">
interface Props {
value?: string;
}
let { value = $bindable('') }: Props = $props();
</script>
<!-- Parent stays the same -->
<Input bind:value={name} />10. Lifecycle: beforeUpdate/afterUpdate → $effect
Before:
<script lang="ts">
import { beforeUpdate, afterUpdate } from 'svelte';
beforeUpdate(() => {
console.log('before update');
});
afterUpdate(() => {
console.log('after update');
});
</script>After:
<script lang="ts">
$effect.pre(() => {
console.log('before update');
});
$effect(() => {
console.log('after update');
});
</script>IMPORTANT: onMount and onDestroy remain valid and should be preserved!
- Use
onMountfor initialization logic that should only run once when the component first mounts - Use
$effectfor reactive side effects that should re-run when dependencies change - Never convert
onMountto$effectunless the logic genuinely needs to be reactive
Examples:
Keep as onMount:
// ✅ One-time initialization - keep as onMount
onMount(() => {
if (query) {
$filters = toListWorkflowFilters(query, $searchAttributes);
}
});Convert to $effect:
// ✅ Reactive side effect - convert to $effect
$effect(() => {
document.title = `Count: ${count}`; // re-runs when count changes
});11. Dynamic Components: <svelte:component> → direct usage
Before:
<svelte:component this={DynamicComponent} {prop} />After:
<DynamicComponent {prop} />Or with conditional:
{#if Component}
<Component {prop} />
{/if}12. class: Directive → Conditional Classes
The class: directive still works but consider using conditional expressions:
Before:
<div class:active={isActive} class:disabled>After (either works):
<div class:active={isActive} class:disabled>
<!-- or -->
<div class={`${isActive ? 'active' : ''} ${disabled ? 'disabled' : ''}`}>13. App State
Before:
import {page} from '$app/stores'After:
import {page} from '$app/state'Workflow
- Read the file to understand its current structure
- Identify all Svelte 4 patterns that need migration
- Apply transformations systematically:
- Props first (export let → $props)
- State variables (let → $state where needed)
- Derived values ($: assignments → $derived)
- Side effects ($: statements → $effect)
- Event handlers (on: → on)
- Component events (dispatch → callback props)
- Slots (slot → snippets)
- Update imports (add Snippet type if needed, remove createEventDispatcher if no longer used)
- Ensure TypeScript types are correct
- Run
pnpm checkto verify no type errors
Important Notes
- Keep
onMountandonDestroy- they're still valid context="module"scripts are now<script module>- CSS/styles don't change
{#if},{#each},{#await}blocks remain unchangedbind:directives on elements remain unchangeduse:action directives remain unchangedtransition:,in:,out:,animate:directives remain unchanged
In this repository7 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- auth-testingSkill
- local-temporalSkill
- proto-codegenSkill
- serverless-worker-awsSkill
- setup-worktreeSkill
- system-nexus-operationSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

