PlugWiki

svelte5-best-practices Skill (ejirocodes): Svelte 5

Makes Claude write, review and migrate Svelte 5 and SvelteKit code using runes, snippets and current patterns.

Installs
17.8K
on skills.sh
Stars
6
on GitHub
Files
7
besides SKILL.md
Updated
Jun 2026
last repo commit

svelte5-best-practices gives Claude a quick-reference table and seven reference files for Svelte 5. It covers runes, snippets, events, TypeScript props, migration, SvelteKit and performance. SKILL.md also lists eight common mistakes, such as using on:click instead of onclick or setting module-level state in SSR.

It triggers when you write, review or refactor Svelte 5 components or SvelteKit apps. It bundles no scripts. In Claude Code the README says it is available as the /svelte5-best-practices slash command, and that prefixing a prompt with "use svelte skill" triggers it explicitly.

Good for

  • Svelte developers writing new components
  • Teams migrating from Svelte 4 to Svelte 5
  • Reviewers checking SvelteKit data loading and SSR state

Install svelte5-best-practices

Claude Code

  1. 1

    Copy this prompt.

    Install the svelte5-best-practices skill in Claude Code. Run this command:
    
    /plugin marketplace add ejirocodes/agent-skills
    /plugin install svelte5-best-practices@ejirocodes-skills
    
    Then check that it loaded and tell me how to use it.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

The plugin route installs the svelte5-best-practices plugin, whose folder (svelte/) holds only this skill, with no hooks, agents or MCP config in the git tree. The README's skills CLI command targets the same svelte folder. This skill is guidance for writing, reviewing and refactoring Svelte code in a project, so there is no Claude app upload route.

From the project README. Source.

What's in the skill

When it loads

Svelte 5 runes, snippets, SvelteKit patterns, and modern best practices for TypeScript and component development. Use when writing, reviewing, or refactoring Svelte 5 components and SvelteKit applications. Triggers on: Svelte components, runes ($state, $derived, $effect, $props, $bindable, $inspect), snippets ({#snippet}, {@render}), event handling, SvelteKit data loading, form actions, Svelte 4 to Svelte 5 migration, store to rune migration, slots to snippets migration, TypeScript props typing, generic components, SSR state isolation, performance optimization, or component testing.

Sections in SKILL.md

  1. Quick Reference
  2. Essential Patterns
  3. Reactive State
  4. Component Props
  5. Snippets (replacing slots)
  6. Event Handlers
  7. Callback Props (replacing createEventDispatcher)
  8. Common Mistakes

Key facts

Installs on skills.sh
17,847 (Nov 2, 2026)
GitHub stars
6 (Nov 2, 2026)
Last repo commit
Jun 25, 2026

What it includes

  • $state, $derived, $effect, $props, $bindable and $inspect

    Details are in references/runes.md.

    Read · Runes

  • Replacing slots with {#snippet} and {@render}

    Read · Snippets

  • onclick handlers, callback props and the context API

    Read · Events

  • Props typing and generic components

    Read · TypeScript

  • Svelte 4 to 5, stores to runes, slots to snippets

    Write · Migration

  • Load functions, form actions, SSR and page typing

    Read · SvelteKit

  • Universal reactivity, avoiding over-reactivity and streaming

    Read · Performance

  • Eight mistakes to avoid, such as let without $state or sequential awaits in load functions

    Read · Common mistakes

From the official docs

Permissions

Low risk

svelte5-best-practices bundles no scripts, but it has Claude edit your Svelte code. Our advice: use a branch and read the diff.

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • It edits your code, including migrations

    The skill triggers on writing, reviewing and refactoring Svelte 5 code and on Svelte 4 to 5 migrations. Use a branch and review the diff. github.com

  • The plugin holds one skill

    The svelte5-best-practices plugin lives in the svelte folder of the repo. The git tree shows no hooks, agents or MCP config there. github.com

Technical details
Turning on read-onlyNo read-only switch.
Sign-in and keysSKILL.md names no account, key or token.
Scopes
  • Claude reads and edits Svelte components and SvelteKit files in your project

Questions

What does svelte5-best-practices do?

It gives Claude patterns for writing Svelte 5 and SvelteKit code. It covers runes, snippets, events, TypeScript, migration from Svelte 4, SvelteKit and performance.

How do I install it?

Use the install box at the top. The README gives a Claude Code plugin route and a skills CLI command for the svelte folder.

How do I trigger it?

The README says Claude Code exposes it as the /svelte5-best-practices slash command. For skills.sh installs it suggests starting a prompt with "use svelte skill" for best results.

Can it migrate Svelte 4 code?

It has a migration reference for Svelte 4 to 5, stores to runes and slots to snippets. SKILL.md lists these among its triggers.

Does it need Svelte tooling or an API key?

SKILL.md names none. It bundles no scripts and its reference files are Markdown.

Does it work in the Claude app?

There is no upload route here, because the skill is for editing Svelte code in a project. The install box covers Claude Code, Codex and the skills CLI.

Is it safe?

The skill bundles no scripts, but it has Claude edit your Svelte components. Our advice: work on a branch and review the diff, especially for migrations that touch many files.

Information

updated Nov 2, 2026

Folder
svelte/skills/svelte5-best-practices

ejirocodes/agent-skillsskills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 6
  1. svelte5-best-practices SKILL.md · github.com
  2. agent-skills README · github.com
  3. marketplace.json · github.com
  4. svelte plugin.json · github.com
  5. LICENSE · github.com
  6. skills.sh listing · skills.sh

Updated Nov 2, 2026.