Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From all-commands
Migrates Svelte/SvelteKit projects between versions like Svelte 3→5 and Kit 1→2, adopts runes and TypeScript, runs codemods, fixes breaking changes, and generates checklists.
npx claudepluginhub davepoon/buildwithclaude --plugin all-commandsHow this command is triggered — by the user, by Claude, or both
Slash command
/all-commands:svelte-migrateThe summary Claude sees in its command listing — used to decide when to auto-load this command
# /svelte-migrate Migrate Svelte/SvelteKit projects between versions, adopt new features like runes, and handle breaking changes. ## Instructions You are acting as the Svelte Development Agent focused on migrations. When migrating projects: 1. **Migration Types**: **Version Migrations**: - Svelte 3 → Svelte 4 - Svelte 4 → Svelte 5 (Runes) - SvelteKit 1.x → SvelteKit 2.x - Legacy app → Modern SvelteKit **Feature Migrations**: - Stores → Runes ($state, $derived) - Class components → Function syntax - Imperative → Declarative patterns - JavaScript → Ty...
/svelte-migrateMigrates Svelte/SvelteKit projects between versions like Svelte 3→5 and Kit 1→2, adopts runes and TypeScript, runs codemods, fixes breaking changes, and generates checklists.
/svelteAssesses and scaffolds Svelte/SvelteKit projects with Svelte 5 runes reactivity, stores, routing, load functions, form actions, SSR, adapters, hooks, and Vitest tests. Supports flags like --audit, --migrate, --component.
/auditAudits the current codebase for SvelteKit and Svelte 5 best practice violations, reporting file/line locations, explanations, correct patterns, and severity ratings (critical/warning/info).
/migration-helperAutomates framework migrations, version upgrades, library replacements, and codemod generation using AST analysis, producing plans, transformation scripts, diffs, tests, and rollbacks.
/migrateMigrates code between frameworks/technologies (e.g., React→Vue, Express→Fastify) via analysis, planning, execution, validation, with strategy/backup options.
/mui-migrateMigrates MUI from v4 to v5 or v5 to v6: assesses codebase state, generates plan, applies codemods, and guides manual transforms.
Share bugs, ideas, or general feedback.
Migrate Svelte/SvelteKit projects between versions, adopt new features like runes, and handle breaking changes.
You are acting as the Svelte Development Agent focused on migrations. When migrating projects:
Migration Types:
Version Migrations:
Feature Migrations:
Migration Process:
# Automated migrations
npx sv migrate [migration-name]
# Manual migration steps
1. Backup current code
2. Update dependencies
3. Run codemods
4. Fix breaking changes
5. Update configurations
6. Test thoroughly
Runes Migration:
// Before (Svelte 4)
let count = 0;
$: doubled = count * 2;
// After (Svelte 5)
let count = $state(0);
let doubled = $derived(count * 2);
Breaking Changes:
Migration Checklist:
User: "Migrate my Svelte 4 app to Svelte 5 with runes"
Assistant will:
npx sv migrate svelte-5