sveltekit-best-practices
SvelteKit and Svelte 5 done right. Runes, load functions, form actions, SSR patterns, and modern Svelte.
How do I install this agent skill?
npx skills add https://github.com/ofershap/sveltekit-best-practices --skill sveltekit-best-practicesIs this agent skill safe to install?
- Gen Agent Trust Hubpass
This skill provides architectural guidelines and code examples for Svelte 5 and SvelteKit development. It focuses on modern Svelte patterns like runes and server-side operations. No malicious patterns, hidden commands, or security risks were identified during the analysis.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
- Runlayerpass
1 file scanned · No issues
- ZeroLeakspass
Score: 93/100 · 2 sections analyzed
What does this agent skill do?
When to use
Use this skill when working with SvelteKit or Svelte 5 code. AI agents are trained on Svelte 4 patterns and frequently generate outdated code using stores, reactive declarations, and export let. This skill enforces Svelte 5 runes, load functions, and form actions.
Critical Rules
1. Use Svelte 5 runes - never Svelte 4 stores or reactive declarations
Wrong (agents do this):
<script>
import { writable, derived } from 'svelte/store';
let count = writable(0);
$: doubled = $count * 2;
$: if (count > 5) alert('too high');
</script>
<p>{$count}</p>
Correct:
<script>
let count = $state(0);
let doubled = $derived(count * 2);
$effect(() => {
if (count > 5) alert('too high');
});
</script>
<p>{count}</p>
Why: Svelte 5 runes ($state, $derived, $effect) replace stores and $: syntax. Agents default to Svelte 4 patterns.
2. Use $state for reactive state - not let with reactive assignments
Wrong:
<script>
let count = 0;
count = count + 1;
</script>
Correct:
<script>
let count = $state(0);
count = count + 1;
</script>
Why: In Svelte 5, reactivity is opt-in via $state. Plain let is not reactive.
3. Use $derived for computed values - not $: reactive declarations
Wrong:
<script>
let firstName = $state('John');
let lastName = $state('Doe');
$: fullName = `${firstName} ${lastName}`;
</script>
Correct:
<script>
let firstName = $state('John');
let lastName = $state('Doe');
let fullName = $derived(`${firstName} ${lastName}`);
</script>
Why: $: is Svelte 4. Svelte 5 uses $derived for derivations.
4. Use $effect for side effects - not $: reactive statements
Wrong:
<script>
let count = $state(0);
$: if (count > 5) console.log('count is high');
</script>
Correct:
<script>
let count = $state(0);
$effect(() => {
if (count > 5) console.log('count is high');
});
</script>
Why: $effect runs when dependencies change. $: for side effects is deprecated.
5. Use $props() for component props - not export let
Wrong:
<script>
export let title = 'Default';
export let count;
</script>
<h1>{title}</h1>
Correct:
<script>
let { title = 'Default', count } = $props();
</script>
<h1>{title}</h1>
Why: export let is Svelte 4. Svelte 5 uses $props().
6. Use $bindable() for two-way binding props
Wrong:
<script>
let { value } = $props();
</script>
<input bind:value={value} />
Correct:
<script>
let { value = $bindable() } = $props();
</script>
<input bind:value={value} />
Why: Props are one-way by default. $bindable() enables bind:value from parent.
7. Use load functions (+page.server.ts) for data fetching - not onMount fetch
Wrong:
<script>
import { onMount } from 'svelte';
let data = $state(null);
onMount(async () => {
data = await fetch('/api/users').then(r => r.json());
});
</script>
{#if data}{data.name}{/if}
Correct:
// +page.server.ts
import type { PageServerLoad } from "./$types";
export const load: PageServerLoad = async ({ fetch }) => ({
data: await fetch("/api/users").then((r) => r.json()),
});
<!-- +page.svelte -->
<script>
let { data } = $props();
</script>
{#if data}{data.name}{/if}
Why: Load runs on server for SSR, avoids loading flicker, and integrates with SvelteKit routing.
8. Use form actions for mutations - not API routes for form submissions
Wrong:
<form on:submit={async (e) => {
e.preventDefault();
await fetch('/api/login', { method: 'POST', body: new FormData(e.target) });
goto('/dashboard');
}}>
Correct:
// +page.server.ts
import type { Actions } from "./$types";
export const actions = {
default: async ({ request, cookies }) => {
const data = await request.formData();
// validate, authenticate, set cookie
return { type: "redirect", location: "/dashboard" };
},
};
<form method="POST" use:enhance>
Why: Form actions enable progressive enhancement, work without JS, and avoid client-side fetch boilerplate.
9. Use +layout.server.ts for shared layout data
Wrong:
<!-- Multiple pages each fetch user -->
<script>
let user = $state(null);
onMount(() => fetchUser().then(u => user = u));
</script>
Correct:
// +layout.server.ts
export const load = async ({ locals }) => ({
user: locals.user,
});
Why: Layout load runs once, data is available to all child pages. No duplicate fetches.
10. Use +error.svelte for error pages
Correct:
<!-- +error.svelte -->
<script>
let { status, message } = $props();
</script>
<h1>{status}</h1>
<p>{message}</p>
Why: SvelteKit uses +error.svelte to render load/action errors. Use it instead of try/catch in every page.
11. Use +page.ts for universal load (server and client)
When data is needed on both server and client (e.g. from $app/stores or browser APIs), put logic in +page.ts. Use +page.server.ts when data is server-only.
12. Use hooks.server.ts for middleware (auth, redirects)
Correct:
// hooks.server.ts
export const handle = async ({ event, resolve }) => {
event.locals.user = await getUser(event);
if (!event.locals.user && event.url.pathname.startsWith("/dashboard")) {
return redirect(302, "/login");
}
return resolve(event);
};
Why: Handle runs before every request. Use for auth, redirects, and setting locals.
13. Use $app/stores sparingly - prefer load function data
Prefer passing data via load props. Use $page, $navigating, etc. only when you need client-side routing state.
14. Use snippet blocks for reusable template chunks (Svelte 5)
Wrong:
<script>
export let slots;
</script>
{#if slots.header}<slot name="header" />{/if}
Correct:
<script>
let { header = @render(() => {}) } = $props();
</script>
{@render header()}
Why: Svelte 5 snippets replace slot-based composition with @render and snippet props.
Patterns
- Page data: +page.server.ts load returns object, +page.svelte receives via $props() with
data - Form with enhance:
method="POST"anduse:enhancefrom$app/forms - Streaming: Return promises from load without await; use
{#await data.promise}in template - TypeScript: Use
import type { PageServerLoad, PageProps } from './$types'
Anti-Patterns
- Do not use writable, readable, derived, get from svelte/store
- Do not use $: for derivations or side effects
- Do not use export let for props
- Do not fetch in onMount when data is needed for SSR
- Do not create +server.ts API routes just for form POST handling
- Do not use bind:value with a prop unless the prop is $bindable()
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/ofershap/sveltekit-best-practices/sveltekit-best-practices">View sveltekit-best-practices on skillZs</a>