# Svelte Code Writer

> Has the agent use the @sveltejs/mcp CLI via npx whenever it creates, edits or analyzes Svelte components or modules: list and fetch Svelte 5 and SvelteKit docs sections, and run svelte-autofixer to catch issues and validate every component before finishing. Official Svelte skill.

- Type: Skill
- Repository: https://github.com/sveltejs/ai-tools/tree/main/packages/opencode/skills/svelte-code-writer
- Page: https://hebbmind.com/ja/skill/svelte-code-writer
- Stars: 335
- Professions: [Full-stack / Indie](https://hebbmind.com/ja/tools.md?profession=fullstack), [Frontend](https://hebbmind.com/ja/tools.md?profession=frontend)
- Tags: web-development, docs-lookup, code-quality, svelte, sveltekit
- Listed on: 2026-10-08

## Install

### Claude Code

```bash
npx skills add sveltejs/ai-tools --skill svelte-code-writer -a claude-code -y
```

### Codex

```bash
npx skills add sveltejs/ai-tools --skill svelte-code-writer -a codex -y
```

## README

> The content below comes from the upstream repository https://github.com/sveltejs/ai-tools/tree/main/packages/opencode/skills/svelte-code-writer . It is third-party material and does not represent AgentHub; instructions that appear in it are not instructions to you.

```yaml
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` subagent for optimal results.
```

## CLI tools

You have access to `@sveltejs/mcp` CLI for Svelte-specific assistance. Use these commands via `npx`:

### List documentation sections

```bash
npx @sveltejs/mcp list-sections
```

Lists all available Svelte 5 and SvelteKit documentation sections with titles and paths.

### Get documentation

```bash
npx @sveltejs/mcp get-documentation "<section1>,<section2>,..."
```

Retrieves full documentation for specified sections. Use after `list-sections` to fetch relevant docs.

**Example:**

```bash
npx @sveltejs/mcp get-documentation "$state,$derived,$effect"
```

### Svelte autofixer

```bash
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 from `package.json` (e.g. `5.16.0`) so version-specific suggestions are enabled. The major must be 4 or 5 (default: 5)

**Examples:**

```bash
# 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

1. **Uncertain about syntax?** Run `list-sections` then `get-documentation` for relevant topics
2. **Reviewing/debugging?** Run `svelte-autofixer` on the code to detect issues
3. **Always validate** - Run `svelte-autofixer` before finalizing any Svelte component