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/forge
- 최근 소스 활동
- 2026년 7월 17일 22:27
- 감지된 SKILL.md 언어
- 영어
- 스타
- 192
- 포크
- 28
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- 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 agent for optimal results.
# Svelte 5 Code Writer
## CLI Tools
Use the repo-installed `@sveltejs/mcp@0.1.24` CLI for Svelte-specific assistance:
```bash
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
```bash
vp exec -- svelte-mcp list-sections
```
Lists all available Svelte 5 and SvelteKit documentation sections with titles and paths.
### Get Documentation
```bash
vp exec -- svelte-mcp get-documentation "<section1>,<section2>,..."
```
Retrieves full documentation for specified sections. Use after `list-sections` to fetch relevant docs.
**Example:**
```bash
vp exec -- svelte-mcp get-documentation '$state,$derived,$effect'
```
### Svelte Autofixer
```bash
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:**
```bash
# 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
1. **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 issues
3. **Always validate** - Run `svelte-autofixer` before finalizing any Svelte component
GitHub에서 보기