svelte-code-writer

# Svelte 5 Code Writer ## CLI Tools Use the repo-installed `@sveltejs/mcp` CLI for Svelte-specific assistance: ```bash bun run svelte-mcp <command> ``` Run these commands from the repository root (`svelte-mcp` is a devDependency installed in `node_modules/.bin`). ### List Documentation Sections ```bash bun run svelte-mcp list-sections ``` Lists all available Svelte 5 and SvelteKit documentation sections with titles and paths. ### Get Documentation ```bash bun run svelte-mcp get-documentation "<section1>,<section2>,..." ``` Retrieves full documentation for specified sections. Use after `list-sections` to fetch relevant docs. **Example:** ```bash bun run svelte-mcp get-documentation '$state,$derived,$effect' ``` ### Svelte Autofixer ```bash bun run svelte-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:** ```bash # Analyze inline code bun run svelte-mcp svelte-autofixer '<script>let count = $state(0);</script>' # Analyze a file bun run svelte-mcp svelte-autofixer ./src/lib/components/Component.svelte # Target Svelte 4 bun run svelte-mcp svelte-autofixer ./Component.svelte --svelte-version 4 ``` **Important:** When passing code with runes (`$state`, `$derived`, etc.) via the terminal, wrap inline code in single quotes. If you use double quotes, escape `$` as `\$` to prevent shell variable substitution. ## Workflow 1. **Uncertain about syntax?** Run `list-sections` then `get-documentation` for relevant topics with `bun run svelte-mcp` 2. **Reviewing/debugging?** Run `svelte-autofixer` on the code with `bun run svelte-mcp` to detect issues 3. **Always validate** - Run `svelte-autofixer` before finalizing any Svelte component