svelte-code-writer
CLI tools for Svelte 5 documentation lookup and code analysis. MUST be used whenever creating or editing any Svelte component (.svelte) or Svelte module (.svelte.ts/.svelte.js). If possible, this skill should be executed within the svelte-file-editor agent for optimal results.
When & Why to Use This Skill
The Svelte 5 Code Writer is a specialized Claude skill designed to optimize the development workflow for Svelte 5 and SvelteKit. It provides real-time access to official documentation, performs deep code analysis, and includes an automated fixer to ensure components adhere to the latest Svelte 5 runes and best practices. By integrating documentation lookup and syntax validation directly into the coding process, it helps developers eliminate syntax errors and accelerate the adoption of Svelte 5 features.
Use Cases
- Syntax Reference: Quickly retrieving documentation for Svelte 5 runes like $state, $derived, and $effect to ensure correct implementation during component creation.
- Code Quality Assurance: Using the svelte-autofixer to analyze .svelte and .svelte.ts files for common logic errors and anti-patterns before finalizing code.
- Version Migration: Leveraging the tool's version-specific analysis to identify and upgrade deprecated Svelte 4 patterns to Svelte 5 standards.
- Documentation-Driven Debugging: Listing and fetching specific SvelteKit documentation sections to resolve complex routing or lifecycle issues without leaving the development environment.
| name | svelte-code-writer |
|---|---|
| description | CLI tools for Svelte 5 documentation lookup and code analysis. MUST be used whenever creating or editing any Svelte component (.svelte) or Svelte module (.svelte.ts/.svelte.js). If possible, this skill should be executed within the svelte-file-editor agent for optimal results. |
Svelte 5 Code Writer
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: 4 or 5 (default: 5)
Examples:
# Analyze inline code (escape $ as \$)
npx @sveltejs/mcp svelte-autofixer '<script>let count = \$state(0);</script>'
# Analyze a file
npx @sveltejs/mcp svelte-autofixer ./src/lib/Component.svelte
# Target Svelte 4
npx @sveltejs/mcp svelte-autofixer ./Component.svelte --svelte-version 4
Important: When passing code with runes ($state, $derived, etc.) via the terminal, escape the $ character as \$ to prevent shell variable substitution.
Workflow
- Uncertain about syntax? Run
list-sectionsthenget-documentationfor relevant topics - Reviewing/debugging? Run
svelte-autofixeron the code to detect issues - Always validate - Run
svelte-autofixerbefore finalizing any Svelte component