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…

npx skills add https://github.com/sveltejs/ai-tools --skill svelte-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

  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

Lebih banyak skill dari sveltejs

performance-investigation
sveltejs
Menyelidiki regresi performa dan menemukan peluang untuk optimasi
official
svelte-code-writer
sveltejs
We need to translate the given text from English to Bahasa Indonesia. The text describes a CLI tool for Svelte 5 documentation lookup and code analysis with autofixer. We must preserve the name "svelte-code-writer" but it's not in the text, so we don't include it. Also preserve technical terms like "CLI", "Svelte 5", "autofixer", "list-sections", "get-documentation", "svelte-autofixer", "--svelte-version", "--async", "Svelte 4", etc. No extra commentary. Just translate the text inside <text>. The text ends with "within the..." so we keep that. Translation: "Alat CLI untuk pencarian dokumentasi Svelte 5 dan analisis kode dengan perbaikan otomatis bawaan. Tiga perintah inti: list-sections untuk menjelajahi dokumen yang tersedia, get-documentation untuk mengambil dokumentasi lengkap untuk topik tertentu, dan svelte-autofixer
official
svelte-core-bestpractices
sveltejs
Panduan untuk menulis kode Svelte yang cepat, kokoh, dan modern. Muat keterampilan ini setiap kali berada dalam proyek Svelte dan diminta untuk menulis/mengedit atau menganalisis komponen Svelte atau…
official
svelte-core-bestpractices
sveltejs
Guidance on writing fast, robust, modern Svelte code. Load this skill whenever in a Svelte project and asked to write/edit or analyze a Svelte component or…
official
scenario-writer
sveltejs
Picks a new scenario to create based on the description of the user, delegates the writing of it to the ai-scenario-writer subagent and verify the correctness.
official
performance-investigation
sveltejs
Investigate performance regressions and find opportunities for optimization
official
writing-opencode-plugins
sveltejs
Plugin OpenCode, @opencode-ai/plugin, @opencode-ai/plugin/tui, kait plugin, alat kustom, rute TUI, slot, keymap, dan pengemasan. Gunakan saat membuat,…
official
scenario-writer
sveltejs
Memilih skenario baru untuk dibuat berdasarkan deskripsi pengguna, mendelegasikan penulisannya ke subagen ai-scenario-writer dan memverifikasi kebenarannya.
official