How do I install the Svelte Code Writer skill?

Run npx skillmds@latest add kenn-io/svelte-code-writer in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Svelte Code Writer safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Svelte Code Writer?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Svelte Code Writer free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Svelte Code Writer?

kenn-io (@kenn-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Svelte Code Writer by kenn-io — Agent Skill

Name: Svelte Code Writer
Author: kenn-io

Svelte Code Writer

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.

kenn-io e06d65d 2.3 KB Updated Sep 17, 2026

File contents

Svelte 5 Code Writer

CLI Tools

Use the repo-installed @sveltejs/mcp@0.1.24 CLI for Svelte-specific assistance:

vp exec -- svelte-mcp <command>

Run these commands from the repository root. Always include the -- separator after vp exec; without it, Vite+ exits before running svelte-mcp. Do not use npx, npm, or bun x for this tool.

List Documentation Sections

vp exec -- svelte-mcp list-sections

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

Get Documentation

vp exec -- svelte-mcp get-documentation "<section1>,<section2>,..."

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

Example:

vp exec -- svelte-mcp get-documentation '$state,$derived,$effect'

Svelte Autofixer

vp exec -- 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:

# Analyze inline code
vp exec -- svelte-mcp svelte-autofixer '<script>let count = $state(0);</script>'

# Analyze a file
vp exec -- svelte-mcp svelte-autofixer ./frontend/src/lib/Component.svelte

# Target Svelte 4
vp exec -- 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

Uncertain about syntax? Run list-sections then get-documentation for relevant topics with vp exec -- svelte-mcp
Reviewing/debugging? Run svelte-autofixer on the code with vp exec -- svelte-mcp to detect issues
Always validate - Run svelte-autofixer before finalizing any Svelte component

---name: svelte-code-writerdescription: 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 ToolsUse the repo-installed `@sveltejs/mcp@0.1.24` CLI for Svelte-specific assistance:```bashvp exec -- svelte-mcp <command>```Run these commands from the repository root. Always include the `--` separator after `vp exec`; without it, Vite+ exits before running `svelte-mcp`. Do not use `npx`, `npm`, or `bun x` for this tool.### List Documentation Sections```bashvp exec -- svelte-mcp list-sections```Lists all available Svelte 5 and SvelteKit documentation sections with titles and paths.### Get Documentation```bashvp exec -- svelte-mcp get-documentation "<section1>,<section2>,..."```Retrieves full documentation for specified sections. Use after `list-sections` to fetch relevant docs.**Example:**```bashvp exec -- svelte-mcp get-documentation '$state,$derived,$effect'```### Svelte Autofixer```bashvp exec -- 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 codevp exec -- svelte-mcp svelte-autofixer '<script>let count = $state(0);</script>'# Analyze a filevp exec -- svelte-mcp svelte-autofixer ./frontend/src/lib/Component.svelte# Target Svelte 4vp exec -- 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.## Workflow1. **Uncertain about syntax?** Run `list-sections` then `get-documentation` for relevant topics with `vp exec -- svelte-mcp`2. **Reviewing/debugging?** Run `svelte-autofixer` on the code with `vp exec -- svelte-mcp` to detect issues3. **Always validate** - Run `svelte-autofixer` before finalizing any Svelte component

Frequently asked questions