svelte-knowledge-patch

Explain Svelte 5 runes, snippets, and migration patterns from Svelte 4.

22|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/Nevaberry/nevaberry-plugins --skill svelte-knowledge-patch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: svelte-knowledge-patch
Source: https://github.com/Nevaberry/nevaberry-plugins/tree/main/plugins/svelte-knowledge-patch/skills/svelte-knowledge-patch
Command: npx skills add https://github.com/Nevaberry/nevaberry-plugins --skill svelte-knowledge-patch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Svelte Knowledge Patch bridges gaps in Svelte 5 understanding for developers who rely on older training data, focusing on runes, snippets, events, and migration patterns.

Core Features & Use Cases

  • Runes and reactivity: $state, $derived, $effect, $props and the migration notes for Svelte 5.
  • Snippets and events: replacing slots with {#snippet} and using callback props instead of createEventDispatcher.
  • Shared reactive logic: building reusable logic with .svelte.js/.svelte.ts outside components and references for guidance.

Quick Start

Ask it to walk through a concrete Svelte 4 to 5 upgrade example, showing how to implement new runes and snippet-based rendering.

Frequently Asked Questions about svelte-knowledge-patch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate Svelte 4 components to Svelte 5 runes?

Svelte 5 migration replaces reactive declarations with $state, $derived, and $effect runes. This Skill provides concrete migration patterns to restructure component APIs and update reactivity models for Svelte 5 upgrades.

What is the Svelte 5 replacement for slots and createEventDispatcher?

Svelte 5 replaces slots with {#snippet} directives and substitutes createEventDispatcher with callback props. This Skill guides these transitions to modernize component composition and event handling.

How do I share reactive logic outside of Svelte components?

You share reactive logic outside Svelte components by extracting it into .svelte.js or .svelte.ts files. This Skill explains building reusable reactive state and effects within these shared modules.

Do I need to rewrite all my Svelte 4 event dispatchers for Svelte 5?

Svelte 5 requires rewriting Svelte 4 event dispatchers by replacing createEventDispatcher with callback props. This Skill covers transitioning event handling by passing functions as props during migration.

What are the limitations when upgrading to Svelte 5 runes?

Upgrading to Svelte 5 runes presents limitations when mixing legacy reactivity with new runes in the same component. This Skill provides migration guidance to navigate these constraints during upgrades.