Svelte Verification
Use this skill before claiming Svelte or SvelteKit work is complete. It also
applies when debugging framework diagnostics, deciding whether to use MCP or
CLI tooling, running migrations, or selecting final checks.
Verification contract
- Identify changed files and behavior.
- Use Svelte MCP documentation for current, version-sensitive guidance.
- Run
svelte-autofixer through the Svelte MCP for changed .svelte files
when remote source analysis is authorized and the tool is available.
- Run project-native gates before generic fallbacks.
- Exercise the actual user path when behavior is interactive, route-based,
form-based, auth-sensitive, adapter-sensitive, or visual.
- Report exact commands, relevant output, skipped checks, and residual risk.
Command selection
Prefer the project's package scripts:
npm run check
npm run typecheck
npm run test
npm run build
Use sv or @sveltejs/mcp only when the project or task calls for Svelte's
official tooling. Before relying on a command or flag, inspect the installed
or invoked help output:
npx sv --help
npx sv check --help
npx -y @sveltejs/mcp --help
Do not install dependencies, run migrations, or rewrite lockfiles unless the
user has authorized that mutation.
MCP routing
- Use MCP docs lookup before version-sensitive claims.
- Use MCP autofix only with source the user is allowed to send remotely.
- Never send secrets or real credential files to remote tools.
- If MCP is unavailable, state that explicitly and continue with local checks
and official docs.
Read the relevant reference
| Reference |
Read when |
| mcp-and-cli.md |
Choosing remote MCP, sv, @sveltejs/mcp, migrations, docs lookup, or autofix. |
| verification-gates.md |
Selecting checks, tests, builds, previews, browser proof, and failure recovery. |
Never summarize a failed gate as success. Preserve the failure output that
changes the next engineering decision.
1---2name: svelte-verification3description: Use when verifying Svelte or SvelteKit work before completion, including MCP docs, Svelte CLI commands, autofix, checks, tests, builds, preview servers, browser validation, diagnostics, or failure recovery.4---56# Svelte Verification78Use this skill before claiming Svelte or SvelteKit work is complete. It also9applies when debugging framework diagnostics, deciding whether to use MCP or10CLI tooling, running migrations, or selecting final checks.1112## Verification contract13141. Identify changed files and behavior.152. Use Svelte MCP documentation for current, version-sensitive guidance.163. Run `svelte-autofixer` through the Svelte MCP for changed `.svelte` files17 when remote source analysis is authorized and the tool is available.184. Run project-native gates before generic fallbacks.195. Exercise the actual user path when behavior is interactive, route-based,20 form-based, auth-sensitive, adapter-sensitive, or visual.216. Report exact commands, relevant output, skipped checks, and residual risk.2223## Command selection2425Prefer the project's package scripts:2627```bash28npm run check29npm run typecheck30npm run test31npm run build32```3334Use `sv` or `@sveltejs/mcp` only when the project or task calls for Svelte's35official tooling. Before relying on a command or flag, inspect the installed36or invoked help output:3738```bash39npx sv --help40npx sv check --help41npx -y @sveltejs/mcp --help42```4344Do not install dependencies, run migrations, or rewrite lockfiles unless the45user has authorized that mutation.4647## MCP routing4849- Use MCP docs lookup before version-sensitive claims.50- Use MCP autofix only with source the user is allowed to send remotely.51- Never send secrets or real credential files to remote tools.52- If MCP is unavailable, state that explicitly and continue with local checks53 and official docs.5455## Read the relevant reference5657| Reference | Read when |58| --------------------------------------------------------- | -------------------------------------------------------------------------------- |59| [mcp-and-cli.md](references/mcp-and-cli.md) | Choosing remote MCP, `sv`, `@sveltejs/mcp`, migrations, docs lookup, or autofix. |60| [verification-gates.md](references/verification-gates.md) | Selecting checks, tests, builds, previews, browser proof, and failure recovery. |6162Never summarize a failed gate as success. Preserve the failure output that63changes the next engineering decision.
nerymurillohnd