How do I install the Svelte Code Writer skill?

Run npx skillmds@latest add stolinski/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?

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

Svelte Code Writer by stolinski — Agent Skill

Name: Svelte Code Writer
Author: stolinski

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.

stolinski 06410cd 2 files · 3.9 KB Updated Sep 17, 2026

File contents

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-sections

Lists 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 4

Important: 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-sections then get-documentation for relevant topics
Reviewing/debugging? Run svelte-autofixer on the code to detect issues
Always validate - Run svelte-autofixer before finalizing any Svelte component
Content-model work: when prose/metadata should live outside TypeScript but UI-driving data must stay typed, use the raw Markdown + typed registry pattern in references/raw-markdown-typed-registry-content-model.md.

---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 ToolsYou have access to `@sveltejs/mcp` CLI for Svelte-specific assistance. Use these commands via `npx`:### List Documentation Sections```bashnpx @sveltejs/mcp list-sections```Lists all available Svelte 5 and SvelteKit documentation sections with titles and paths.### Get Documentation```bashnpx @sveltejs/mcp get-documentation "<section1>,<section2>,..."```Retrieves full documentation for specified sections. Use after `list-sections` to fetch relevant docs.**Example:**```bashnpx @sveltejs/mcp get-documentation "$state,$derived,$effect"```### Svelte Autofixer```bashnpx @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:**```bash# Analyze inline code (escape $ as \$)npx @sveltejs/mcp svelte-autofixer '<script>let count = \$state(0);</script>'# Analyze a filenpx @sveltejs/mcp svelte-autofixer ./src/lib/Component.svelte# Target Svelte 4npx @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.## Workflow1. **Uncertain about syntax?** Run `list-sections` then `get-documentation` for relevant topics2. **Reviewing/debugging?** Run `svelte-autofixer` on the code to detect issues3. **Always validate** - Run `svelte-autofixer` before finalizing any Svelte component4. **Content-model work:** when prose/metadata should live outside TypeScript but UI-driving data must stay typed, use the raw Markdown + typed registry pattern in `references/raw-markdown-typed-registry-content-model.md`.

Frequently asked questions