Our review
Migrates a complete module to a target architecture following a 6-phase process with validation and approval gates in between.
Strengths
- Structured and repeatable process with clear phases
- Validation after each phase (build, svelte-check, tests)
- Comprehensive coverage from analysis to final review
Limitations
- Requires the target architecture to be defined in docs/ARCHITECTURE.md
- Does not handle external dependencies or complex integrations
- Approval phases can slow down automated execution
Use this skill when you need to migrate an entire module (files, types, services, state, components) to a new architecture.
Do not use it for small changes or partial refactors, as the process is designed for a complete and systematic migration.
Security analysis
CautionThe skill uses Bash for standard development validation steps. There is no instruction to run destructive or exfiltrating commands, and each phase requires user approval, mitigating risk. However, the presence of Bash execution warrants caution.
- •Uses Bash tool, which could execute arbitrary commands, though here it is limited to running build/lint/test commands like svelte-check, npm run build, npm test.
- •The skill is user-invocable and takes an external argument (module path) without validation, but the commands are predefined.
Examples
Migrate the user module at src/lib/modules/user to the target architecture defined in docs/ARCHITECTURE.md.Run the migration skill for the payment module located in src/lib/modules/payment.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.
Next.js App Router Expert
Development
A skill that turns Claude into a Next.js App Router expert.
README Generator
Development
Creates professional and comprehensive README.md files for your projects.
API Documentation Writer
Development
Generates comprehensive API documentation in OpenAPI/Swagger format.