Svelte 5 runes, SvelteKit data flow, routing, and structure patterns

version
1.3.0
GitHub stars
96

Install

/plugin install svelte-skills@svelte-skills-kit

Run it inside Claude Code after adding the marketplace with /plugin marketplace add spences10/svelte-skills-kit.

Contents

Discovered from source

Skills 10

Claude Code Ecosystem Guide

A curated set of tools for enhanced Claude Code workflows.

The Stack

ToolTypePurpose
toolkit-skillsPluginForced-eval hook + core skills (pair with any skills plugin)
svelte-skills-kitPluginSvelte/SvelteKit skills (pair with toolkit-skills)
ccrecallCLISync transcripts → SQLite for analytics
mcp-omnisearchMCPUnified search (Tavily, Kagi, GitHub, etc.)
mcp-sqlite-toolsMCPSafe SQLite operations
mcpickCLIManage MCP servers, plugins, cache, and profiles
researchSkillVerified source research patterns
skill-creatorSkillCreate Claude skills with best practices

Decision Tree

"I want skills to activate reliably"

→ toolkit-skills - Forced-eval hook evaluates every prompt against available skills. Install alongside any skills plugin.

"I need to search the web"

→ mcp-omnisearch - Web search, GitHub code search, AI answers

"I need to query a database"

→ mcp-sqlite-tools - Read/write SQLite with safety guards

"I have too many MCPs eating context"

→ mcpick - Enable/disable servers per-project

"I need to install or update plugins"

→ mcpick - mcpick plugins install|update|list

"My plugin cache is stale after a version bump"

→ mcpick - mcpick cache clear or mcpick cache clean-orphaned

"I want to track my Claude Code usage"

→ ccrecall - Sync transcripts, query with mcp-sqlite-tools

"I'm building with Svelte/SvelteKit"

→ svelte-skills-kit - Runes, routing, data flow patterns

"I need to research a topic or verify sources"

→ research skill - Verified source research, repo cloning patterns

"I want to create a new Claude skill"

→ skill-creator skill - Progressive disclosure, writing guide, CLI reference

Typical Workflows

Recommended Setup (Skills)

# Core: forced-eval hook + ecosystem skills
npx mcpick plugins install toolkit-skills@claude-code-toolkit

# Domain skills (optional, based on your stack)
npx mcpick plugins install svelte-skills@svelte-skills-kit

# Keep plugins up to date
npx mcpick plugins update toolkit-skills

toolkit-skills hook ensures skills from any plugin activate on relevant prompts.

Add an MCP Server

npx mcpick add omnisearch -- npx -y mcp-omnisearch

Research Mode

npx mcpick enable omnisearch
# Now Claude has web search, GitHub search, AI answers

Data Analysis Mode

npx mcpick enable sqlite-tools
# Query databases, analyze CSVs, manage data

Minimal Context Mode

npx mcpick disable omnisearch sqlite-tools
# Just Claude Code core tools

Fix Stale Plugin Cache

npx mcpick cache status          # Check what's stale
npx mcpick cache clear           # Clear and refresh
npx mcpick cache clean-orphaned  # Remove old versions

Save/Load Profiles

npx mcpick profile save research-mode
npx mcpick profile load research-mode

Analytics Review

bun x ccrecall sync  # Update database
# Then query ~/.claude/ccrecall.db with mcp-sqlite-tools

Links

ToolGitHub
claude-code-toolkithttps://github.com/spences10/claude-code-toolkit
svelte-skills-kithttps://github.com/spences10/svelte-skills-kit
ccrecallhttps://github.com/spences10/ccrecall
mcp-omnisearchhttps://github.com/spences10/mcp-omnisearch
mcp-sqlite-toolshttps://github.com/spences10/mcp-sqlite-tools
mcpickhttps://github.com/spences10/mcpick

Svelte Components

Quick Start

Component libraries: Bits UI (headless) | Ark UI | Melt UI (primitives)

Form trick: Use form attribute when form can't wrap inputs:

<form id="my-form" action="/submit"><!-- outside table --></form>
<table>
	<tr>
		<td><input form="my-form" name="email" /></td>
		<td><button form="my-form">Submit</button></td>
	</tr>
</table>

Web Components

// svelte.config.js
export default {
	compilerOptions: {
		customElement: true,
	},
};
<!-- MyButton.svelte -->
<svelte:options customElement="my-button" />

<button><slot /></button>

Reference Files

Notes

  • Bits UI 1.0: flexible, unstyled, accessible components for Svelte
  • Form defaultValue attribute enables easy form resets
  • Use snippets to wrap rich HTML in custom select options
  • Last verified: 2025-01-14

Svelte Deployment

Quick Start

pnpm 10+: Add prepare script (postinstall disabled by default):

{
	"scripts": {
		"prepare": "svelte-kit sync"
	}
}

Vite 7: Update both packages together:

pnpm add -D vite@7 @sveltejs/vite-plugin-svelte@6

Adapters

# Static site
pnpm add -D @sveltejs/adapter-static

# Node server
pnpm add -D @sveltejs/adapter-node

# Cloudflare
pnpm add -D @sveltejs/adapter-cloudflare

Reference Files

Notes

  • Cloudflare may strip Transfer-Encoding: chunked (breaks streaming)
  • Library authors: include svelte in keywords AND peerDependencies
  • Single-file bundle: kit.output.bundleStrategy: 'single'
  • Last verified: 2025-01-14

Svelte LayerChart

Docs: layerchart.com

Install

npm i layerchart d3-scale

Quick Start

<Chart {data} x="date" y="value" tooltip={{ mode: 'bisect-x' }}>
	<Svg><Area class="fill-primary/20" /><Highlight points /></Svg>
	<Tooltip.Root>{#snippet children({ data })}{data.value}{/snippet}</Tooltip.Root>
</Chart>

Core Patterns

  • Tooltip: {#snippet children({ data })} - NOT let:data
  • Chart context: {#snippet children({ context })}
  • Gradient: {#snippet children({ gradient })}
  • Enable tooltip: tooltip={{ mode: 'band' | 'bisect-x' }}
  • Type data: {#snippet children({ data }: { data: MyType })}

Tooltip Modes

ModeUse Case
bandBar charts (scaleBand)
bisect-xTime-series area/line
quadtree-xArea (nearest x)
quadtreeScatter plots

References

Svelte Runes

Quick Start

Which rune? Props: $props() | Bindable: $bindable() | Computed: $derived() | Side effect: $effect() | State: $state()

Key rules: Runes are top-level only. $derived can be overridden (use const for read-only). Don't mix Svelte 4/5 syntax. Objects/arrays are deeply reactive by default.

Example

<script>
	let count = $state(0); // Mutable state
	const doubled = $derived(count * 2); // Computed (const = read-only)

	$effect(() => {
		console.log(`Count is ${count}`); // Side effect
	});
</script>

<button onclick={() => count++}>
	{count} (doubled: {doubled})
</button>

Reference Files

For @attach and other template directives, see the svelte-template-directives skill.

Notes

  • Use onclick not on:click, {@render children()} in layouts
  • $derived can be reassigned (5.25+) - use const for read-only
  • Use createContext over setContext/getContext for type safety
  • Use $inspect.trace to debug reactivity issues
  • Last verified: 2026-03-12

Svelte Styling

Quick Start

JS vars in CSS: Use style: directive to set CSS custom properties from JavaScript.

<script>
	let columns = $state(3);
</script>

<div style:--columns={columns}>
	{@render children()}
</div>

<style>
	div {
		display: grid;
		grid-template-columns: repeat(var(--columns), 1fr);
	}
</style>

Styling Child Components

Preferred: Pass CSS custom properties as component props:

<!-- Parent.svelte -->
<Child --color="red" --spacing="1rem" />

<!-- Child.svelte -->
<h1>Hello</h1>

<style>
	h1 {
		color: var(--color, blue);
		margin: var(--spacing, 0);
	}
</style>

Fallback: Use :global when custom properties aren't possible (e.g., library components):

<div>
	<LibraryComponent />
</div>

<style>
	div :global {
		h1 { color: red; }
	}
</style>

Reference Files

Notes

  • All <style> blocks are scoped to the component by default
  • Use style: directive, not inline style strings, for dynamic values
  • Prefer CSS custom properties over :global for child styling
  • Last verified: 2026-03-12

Svelte Template Directives

@attach (Svelte 5.29+)

The reactive alternative to use: actions. Re-runs when dependencies change, passes through components via spread, supports cleanup functions.

<script>
	import ImageZoom from 'js-image-zoom';

	function useZoom(options) {
		return (element) => {
			new ImageZoom(element, options);
			return () => console.log('cleanup');
		};
	}
</script>

<!-- Re-runs if options changes (use: wouldn't!) -->
<figure {@attach useZoom({ width: 400 })}>
	<img src="photo.jpg" alt="zoomable" />
</figure>

Quick Reference

DirectivePurposeReactive?
{@attach}DOM manipulation, 3rd-partyYes
{@html}Render raw HTML stringsYes
{@render}Render snippetsYes
{@const}Local constants in blocksN/A
{@debug}Pause debugger on value changeN/A
{#each (key)}Keyed iteration (always key!)Yes
<svelte:window>Window event listenersN/A

@attach vs use: Actions

Featureuse:@attach
Re-runs on arg changeNoYes
ComposableLimitedFully
Pass through propsManualAuto via spread
Convert legacyN/AfromAction()

Reference Files

Notes

  • @attach requires Svelte 5.29+
  • Use fromAction from svelte/attachments to convert legacy actions
  • Attachments pass through wrapper components when you spread props
  • Always use keyed each blocks — never use index as key
  • Use <svelte:window>/<svelte:document> for global events, not $effect
  • Last verified: 2026-03-12

SvelteKit Data Flow

Quick Start

Which file? Server-only (DB/secrets): +page.server.ts | Universal (runs both): +page.ts | API: +server.ts

Load decision: Need server resources? → server load | Need client APIs? → universal load

Form actions: Always +page.server.ts. Return fail() for errors, throw redirect() to navigate, throw error() for failures.

Example

// +page.server.ts
import { fail, redirect } from '@sveltejs/kit';

export const load = async ({ locals }) => {
	const user = await db.users.get(locals.userId);
	return { user }; // Must be JSON-serializable
};

export const actions = {
	default: async ({ request }) => {
		const data = await request.formData();
		const email = data.get('email');

		if (!email) return fail(400, { email, missing: true });

		await updateEmail(email);
		throw redirect(303, '/success');
	},
};

Reference Files

Notes

  • Server load → universal load via data param | ALWAYS throw redirect()/error()
  • No class instances/functions from server load (not serializable)
  • Last verified: 2025-01-11

SvelteKit Remote Functions

Current Status

Remote functions are experimental in SvelteKit 2.58. Enable them in svelte.config.js:

export default {
	kit: { experimental: { remoteFunctions: true } },
	compilerOptions: { experimental: { async: true } } // only for await in components
};

Quick Start

File naming: export remote functions from *.remote.ts or *.remote.js. Remote files can live anywhere under src except src/lib/server.

Which function?

  • Dynamic reads → query()
  • Progressive forms → form()
  • Event-handler mutations → command()
  • Build-time/static reads → prerender()

Example

// posts.remote.ts
import { command, query, requested } from '$app/server';
import * as v from 'valibot';

export const getPosts = query(v.object({ tag: v.optional(v.string()) }), async (filter) => {
	return db.posts.find(filter);
});

export const createPost = command(v.object({ title: v.string() }), async (data) => {
	await db.posts.create(data);

	for (const { query } of requested(getPosts, 5)) {
		void query.refresh();
	}
});

Client:

<script lang="ts">
	import { createPost, getPosts } from './posts.remote';

	const posts = $derived(await getPosts({ tag: 'svelte' }));
</script>

<button onclick={() => createPost({ title: 'New' }).updates(getPosts)}>
	Create
</button>

Current Rules

  • Remote functions always run on the server, even when called from the browser.
  • Args/returns use devalue; avoid functions, class instances, symbols, circular refs, and RegExp.
  • Validate exposed inputs with Standard Schema (valibot, zod, arktype, etc.) or use .unchecked/'unchecked' deliberately.
  • query.batch() batches calls from the same macrotask to solve n+1 reads.
  • form().enhance() submit() returns true when submission is valid/successful and false for validation failures.
  • .updates() is client-requested; server handlers must opt in with requested(queryFn, limit).
  • requested() now yields { arg, query }; call query.refresh()/query.set(...) on the bound instance.
  • limit is required for requested() to cap client-controlled refresh requests.
  • Inside command/form handlers, use void query.refresh()/void query.set(value); SvelteKit awaits and serializes the updates.
  • Prefer form() over command() where progressive enhancement matters.
  • Use prerender() for data that changes at most once per deployment.
  • Last verified: SvelteKit 2.58.0, 2026-04-24

Reference Files

SvelteKit Structure

Quick Start

File types: +page.svelte (page) | +layout.svelte (wrapper) | +error.svelte (error boundary) | +server.ts (API endpoint)

Routes: src/routes/about/+page.svelte → /about | src/routes/posts/[id]/+page.svelte → /posts/123

Layouts: Apply to all child routes. +layout.svelte at any level wraps descendants.

Example

src/routes/
├── +layout.svelte              # Root layout (all pages)
├── +page.svelte                # Homepage /
├── about/+page.svelte          # /about
└── dashboard/
    ├── +layout.svelte          # Dashboard layout (dashboard pages only)
    ├── +page.svelte            # /dashboard
    └── settings/+page.svelte   # /dashboard/settings
<!-- +layout.svelte -->
<script>
	let { children } = $props();
</script>

<nav><!-- Navigation --></nav>
<main>{@render children()}</main>
<footer><!-- Footer --></footer>

Reference Files

Notes

  • Layouts: {@render children()} | Errors: +error.svelte above failing route
  • Groups: (name) folders don't affect URL | Client-only: check browser
  • Last verified: 2025-01-11

Sponsors

Details

Marketplace
spences10/svelte-skills-kit
Source
plugins/svelte-skills
Author
Scott Spence
Category
Framework
License
MIT
Keywords
svelte, sveltekit, runes, routing, ssr

More from spences10/svelte-skills-kit

All 3