sveltekit-remote-functions — Claude Code skill for SvelteKit remote functions

What sveltekit-remote-functions does

The skill covers the four remote function types and picks the right one for the job: query() for dynamic reads, form() for progressive forms, command() for mutations from event handlers, prerender() for data that barely changes between deploys. Exports live in *.remote.ts or *.remote.js files, placed anywhere under src apart from src/lib/server.

It also collects the rules that trip people up. Arguments and return values travel through devalue, so functions, class instances, symbols, circular references and RegExp are out. Exposed inputs get validated with a Standard Schema library such as valibot, zod or arktype, unless you deliberately reach for .unchecked. Reads that would fan out into n+1 calls can go through query.batch(). Client-side refreshes only happen when the server handler opts in with requested(queryFn, limit) — and that limit argument is not optional.

Remote functions are still experimental, with the skill pinned to SvelteKit 2.58.0. You need experimental.remoteFunctions in svelte.config.js, plus compilerOptions.experimental.async if you want await inside components. Skip those flags and the guidance is moot: the code will not compile.