Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From svelte-lsp
This skill should be used when working on Svelte or SvelteKit projects that have the Svelte language server available. Use when the user asks to "check Svelte errors", "fix Svelte component", "find references in Svelte", "rename symbol", "go to definition", "format Svelte file", "understand this Svelte component", or when investigating errors, performing code navigation, or refactoring across a Svelte codebase. Also use when the user mentions "svelteserver", "Svelte LSP", or "SvelteKit".
npx claudepluginhub rcamf/claude-plugins --plugin svelte-lspHow this skill is triggered — by the user, by Claude, or both
Slash command
/svelte-lsp:svelte-lspThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The Svelte language server runs natively via Claude Code's `lspServers` integration,
Svelte runes-first reactivity and SvelteKit fullstack conventions. Invoke whenever task involves any interaction with Svelte code — writing, reviewing, refactoring, debugging, or understanding .svelte, .svelte.js, .svelte.ts files and SvelteKit projects.
Provides CLI tools to list/fetch Svelte 5 documentation sections and autofix .svelte code issues. Use when creating, editing, or analyzing Svelte components/modules.
Enforces Svelte 5 best practices in SvelteKit: runes ($state, $derived, $effect), $props(), $bindable(), load functions, form actions, and SSR patterns to fix outdated Svelte 4 code.
Share bugs, ideas, or general feedback.
The Svelte language server runs natively via Claude Code's lspServers integration,
providing real-time analysis for .svelte files through the Language Server Protocol.
The server launches automatically when working with Svelte components.
The Svelte LSP provides these capabilities through Claude Code's native LSP integration:
Svelte components combine <script>, markup, and <style> in a single .svelte file.
The language server understands all three sections and provides diagnostics across them.
The LSP understands Svelte's reactivity model:
$: reactive declarations$state, $derived, $effect runes (Svelte 5)$ prefix (Svelte 4)Use hover and completions to inspect component props, events, and slots. Find references works across component boundaries — trace where a prop is passed from parent components.
.svelte file.svelte, .ts, and .js files/check-svelte [file] — Run diagnostics on a Svelte file or the whole project/svelte-overview — Get a summary of the Svelte project structuresvelteserver available in PATH (install via npm install -g svelte-language-server)svelte.config.js