Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From godmode
Assesses 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.
npx claudepluginhub arbazkhan971/godmodeHow this command is triggered — by the user, by Claude, or both
Slash command
/godmode:sveltegodmode/Files this command reads when invoked
The summary Claude sees in its command listing — used to decide when to auto-load this command
# /godmode:svelte Svelte and SvelteKit mastery — Svelte 5 runes reactivity, stores, SvelteKit routing with load functions and form actions, server-side rendering, prerendering, adapter configuration for different deployment platforms, and testing. Build production-grade Svelte applications with best practices. ## Usage ## What It Does 1. Assesses project (Svelte version, SvelteKit, reactivity model, adapter, TypeScript) 2. Guides Svelte 5 runes vs legacy reactivity decision 3. Establishes component patterns with $state, $derived, $effect, $props 4. Designs state management (reactive c...
/svelte-scaffoldScaffolds new SvelteKit projects, features, or modules with best practices, optimal structure, TypeScript, Tailwind, auth, database, and deployment configs.
/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.
/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).
Share bugs, ideas, or general feedback.
Svelte and SvelteKit mastery — Svelte 5 runes reactivity, stores, SvelteKit routing with load functions and form actions, server-side rendering, prerendering, adapter configuration for different deployment platforms, and testing. Build production-grade Svelte applications with best practices.
/godmode:svelte # Full Svelte/SvelteKit project assessment
/godmode:svelte --audit # Audit existing Svelte project
/godmode:svelte --migrate # Migrate Svelte 4 to Svelte 5 runes
/godmode:svelte --sveltekit # Set up or configure SvelteKit
/godmode:svelte --stores # Design and implement state management
/godmode:svelte --routing # Design SvelteKit routing with load functions
/godmode:svelte --actions # Implement form actions for mutations
/godmode:svelte --adapter vercel # Configure deployment adapter
/godmode:svelte --ssr # Configure rendering strategy per route
/godmode:svelte --test # Set up Vitest and write tests
/godmode:svelte --component Card # Generate a new component with tests
/godmode:svelte --hooks # Set up server/client hooks
"svelte: <project> — <N> routes, <N> components, <adapter>"After setup: /godmode:tailwind for styling, /godmode:a11y for accessibility.
After building: /godmode:e2e for end-to-end testing with Playwright.
When ready: /godmode:ship to deploy.
/godmode:svelte # Full assessment and scaffolding
/godmode:svelte --sveltekit # Configure SvelteKit with routing
/godmode:svelte --migrate # Migrate Svelte 4 to Svelte 5 runes
/godmode:svelte --adapter cloudflare # Configure Cloudflare adapter
/godmode:svelte --actions # Implement form actions