svelte-docs
Look up official Svelte, SvelteKit, and Svelte CLI documentation.
- License 许可
- AGPL-3.0
- 最近更新
- 2026-11-13
- Stars
- ★ 3.0k
- Forks
- 152
01 前言 Front Matter
- name
- svelte-docs
- description
- Look up official Svelte, SvelteKit, and Svelte CLI documentation.
03 SKILL.md 正文
Svelte Documentation
Use the documentation CLI to find and read relevant sections:
mise x -- npx @sveltejs/mcp list-sections
mise x -- npx @sveltejs/mcp get-documentation '$state,$derived,$effect'
Use single quotes for section names that contain $.
For web lookup, start with the relevant official index:
- Svelte:
https://svelte.dev/docs/svelte/llms-small.txt - SvelteKit:
https://svelte.dev/docs/kit/llms-small.txt - CLI:
https://svelte.dev/docs/cli/llms.txt
Use an available web tool. Read full documentation only if the short version
cannot answer the question. Use https://svelte.dev/llms-small.txt when the
package is unknown; llms-medium.txt and llms-full.txt provide more detail.
Treat supplied text as the search topic. Honor explicit svelte, kit, or
cli scope and medium or full detail requests.
04 同仓库更多 Skills
writing-tests
Instructions and hints for writing tests.
update-project-dependencies
Update Chatto Go and frontend dependencies within their compatible version ranges, then run tests.
svelte-core-bestpractices
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 module. Covers reactivity, event handling, styling, integration with libraries and more.
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.
session-wrap-up
Review a completed, paused, or blocked coding-agent session to identify friction, mistakes, near misses, missing context, and opportunities to improve future work. Use when the user asks to wrap up, run a retrospective, explain what issues the agent faced, capture lessons learned, or recommend improvements to repository instructions, documentation, skills, tooling, tests, or workflows. Produce an evidence-based, propose-only report; do not apply follow-up changes unless the user asks.
pr-tour
A skill that provides a guided tour of a pull request, highlighting key changes, walking the developer through the code, and explaining the purpose of each modification.