
svelte-code-writer
β 284by sveltejs Β· part of sveltejs/ai-tools
CLI tools for Svelte 5 documentation lookup and code analysis with built-in autofixer. Three core commands: list-sections to browse available docs, get-documentation to fetch full documentation for specific topics, and svelte-autofixer to analyze code and suggest fixes Autofixer supports Svelte 4 and 5 targeting via --svelte-version flag and async mode via --async option Accepts both inline code (with escaped $ characters) and file paths for analysis Designed for use within the...
CLI tools for Svelte 5 documentation lookup and code analysis with built-in autofixer. Three core commands: list-sections to browse available docs, get-documentation to fetch full documentation for specific topics, and svelte-autofixer to analyze code and suggest fixes Autofixer supports Svelte 4 and 5 targeting via --svelte-version flag and async mode via --async option Accepts both inline code (with escaped $ characters) and file paths for analysis Designed for use within the...
Inspect the full instructions your agent will receiveExpandCollapse
This is the exact playbook injected into your agent when the skill activates β shown here so you can audit it before installing. You don't need to read it to use the skill.
name: svelte-code-writer description: CLI tools for Svelte 5 documentation lookup and code analysis. MUST be used whenever creating, editing or analyzing 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-sectionsLists 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 4Important: 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
npx skills add https://github.com/sveltejs/ai-tools --skill svelte-code-writerRun this in your project β your agent picks the skill up automatically.
No common issues documented yet. If you hit a problem, the repository's GitHub Issues page is the best place to look.