
Svelte Code Writer
A straightforward CLI wrapper around Svelte's official MCP tools that handles the three things you actually need when working with Svelte 5 components: looking up current documentation sections, fetching specific docs for runes like $state and $derived, and running the autofixer to catch common migration issues from v4. The autofixer is the real workhorse here, analyzing .svelte files for outdated patterns and suggesting fixes. Works best when you're migrating existing components or debugging why your reactive statements aren't working as expected. Just remember to escape dollar signs when passing rune code directly through the terminal.
- skills.sh installs
- 14K
- GitHub stars
- 337
- last updated
- Aug 21, 2026
Install
$ npx -y skills add sveltejs/ai-tools --skill svelte-code-writer --agent claude-codeInstalls into .claude/skills of the current project.
Files
CLI tools
You have access to @sveltejs/mcp CLI for Svelte-specific assistance. Use these commands via npx:
List documentation sections
npx @sveltejs/mcp list-sections
Lists all available Svelte 5 and SvelteKit documentation sections with titles and paths.
Get documentation
npx @sveltejs/mcp get-documentation "<section1>,<section2>,..."
Retrieves full documentation for specified sections. Use after list-sections to fetch relevant docs.
Example:
npx @sveltejs/mcp get-documentation "$state,$derived,$effect"
Svelte autofixer
npx @sveltejs/mcp svelte-autofixer "<code_or_path>" [options]
Analyzes Svelte code and suggests fixes for common issues.
Options:
--async- Enable async Svelte mode (default: false)--svelte-version- Target version, ideally the full version frompackage.json(e.g.5.16.0) so version-specific suggestions are enabled. The major must be 4 or 5 (default: 5)
Examples:
# Analyze inline code (escape $ as \$)
npx @sveltejs/mcp svelte-autofixer '<script>let count = \$state(0);</script>'
Sponsors
Details
- Repository
- github.com/sveltejs/ai-tools
- Categories
- Frontend Development, Documentation, AI & Agent Building, CLI & Terminal