svelte5-migration-analystlisted

# Svelte 5 migration analyst Two deliverables: an evidence-based assessment, and — only if the assessment supports it — a migration roadmap. The failure mode this skill exists to prevent is a confident report full of invented numbers. Framework migrations get sold on "3× faster, 60% smaller" figures nobody measured, and the team finds out in month two. Measure what can be measured, bound what cannot, and be willing to conclude *don't migrate*. ## Ground rules 1. **Never state a performance or size number you did not measure or bound.** Tag every figure `[measured]`, `[bounded]`, or `[projected]` with its basis. See `references/measurement.md`. 2. **`node_modules` gets bigger, not smaller.** SvelteKit ships a compiler and Vite toolchain as devDependencies (measured: 57 packages, 67 MB, **0 runtime dependencies**). The win is shipped bytes and production dependency surface. Report the increase openly. 3. **A swap is not a saving.** react-window → svelte-virtual removes zero dependencies and costs a rewrite. Keep those in their own column. 4. **"Do not migrate" is a valid verdict.** If the bottleneck is a slow API or 4 MB of images, a framework swap changes nothing the user can feel. Say so first, not in a footnote. 5. **Write current Svelte 5, verified.** Svelte 4 idioms in Svelte 5 files compile fine and throw away the entire point of the migration. Verify against the MCP server, not memory. ## Setup: the official Svelte MCP server Check for `mcp__svelt