// 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.
Use when Go test wall time is too high, CI test duration regresses, a package needs trace-driven test performance analysis, or tests should be made safely parallel with t.Parallel, package splitting, subprocess isolation, semaphores, or Go built-in tracing.
Use when working on middleman local development sessions that need backend and frontend on ephemeral/free ports, isolated generated config, copied SQLite state, or dev-ephemeral status JSON/PIDs.
Use when making small or localized changes that could still affect user-visible behavior, API contracts, database queries, test runtime, CI, generated artifacts, or cross-layer data flow.
Use when creating, editing, fixing, or reviewing tests; when adding mocks, assertions, smoke tests, unit tests, integration tests, e2e tests, or changing tests after failures.
Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.
Use when a screenshot or short video needs to be captured with Playwright and saved to local disk, with optional upload through `gh image` (upload requires explicit user approval and must target a PR or issue).
| 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. |
This repo currently uses Svelte 5.55.0.
You have access to pinned @sveltejs/mcp@0.1.22 CLI for Svelte-specific assistance. Use these commands via npx:
npx @sveltejs/mcp@0.1.22 list-sections
Lists all available Svelte 5 and SvelteKit documentation sections with titles and paths.
npx @sveltejs/mcp@0.1.22 get-documentation "<section1>,<section2>,..."
Retrieves full documentation for specified sections. Use after list-sections to fetch relevant docs.
Example:
npx @sveltejs/mcp@0.1.22 get-documentation "$state,$derived,$effect"
npx @sveltejs/mcp@0.1.22 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). For this repo, use 5 because project Svelte version is 5.55.0.Examples:
# Analyze inline code (escape $ as \$)
npx @sveltejs/mcp@0.1.22 svelte-autofixer '<script>let count = \$state(0);</script>' --svelte-version 5
# Analyze a file
npx @sveltejs/mcp@0.1.22 svelte-autofixer ./src/lib/Component.svelte --svelte-version 5
# Target Svelte 4
npx @sveltejs/mcp@0.1.22 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.
list-sections then get-documentation for relevant topicssvelte-autofixer on the code to detect issuessvelte-autofixer with --svelte-version 5 before finalizing any Svelte component in this repo