Our review

Migrates an entire module to the target architecture through six phases with approval gates.

Structured phase-based process with intermediate validation
Covers full migration scope: analysis, structure, types, services, state, and components
Automatically validates build, svelte-check, and tests after each phase

When to use it

Use this skill when you need to migrate an existing module to a new Svelte/SvelteKit architecture.

When not to use it

Do not use it for one-off changes or modules that don't require a full migration.

name: migration-migrate-module description: "Use when a complete module needs migration to the target architecture — runs 6 phases with approval gates." user-invocable: true argument-hint: "[module-path]" allowed-tools: Read, Write, Edit, Bash, Glob, Grep

Migrate an entire module to the target architecture from docs/ARCHITECTURE.md.

Module/Path: $ARGUMENTS

Steps

Use @migrator to coordinate the full migration in phases:

Phase 0 -- Analysis: Map the module (files, Svelte 4 vs 5 patterns, JS vs TS, SvelteKit 1 vs 2 patterns, dependencies)
Phase 1 -- Structure: Create src/lib/modules/[name]/ and route files, move existing files
Phase 2 -- Types: Create .types.ts + .contracts.ts + adapter
Phase 3 -- Services: Migrate to pure service (no try/catch, native fetch)
Phase 4 -- State: Server state -> SvelteKit load functions, Client state -> Svelte stores
Phase 5 -- Components: Svelte 4 -> 5 runes + composition (see conversion table)
Phase 6 -- Review: Validate conformance, check for remaining legacy patterns

Validate build/svelte-check/tests after each phase. Ask for approval before each phase.