spences10

sveltekit-remote-functions

@spences10/sveltekit-remote-functions
spences10
0
0 forks
Updated 1/6/2026
View on GitHub

SvelteKit remote functions guidance. Use for command(), query(), form() patterns in .remote.ts files.

Installation

$skills install @spences10/sveltekit-remote-functions
Claude Code
Cursor
Copilot
Codex
Antigravity

Details

Pathplugins/svelte-skills/skills/sveltekit-remote-functions/SKILL.md
Branchmain
Scoped Name@spences10/sveltekit-remote-functions

Usage

After installing, this skill will be available to your AI coding assistant.

Verify installation:

skills list

Skill Instructions


name: sveltekit-remote-functions

IMPORTANT: Keep description on ONE line for Claude Code compatibility

prettier-ignore

description: SvelteKit remote functions guidance. Use for command(), query(), form() patterns in .remote.ts files.

SvelteKit Remote Functions

Quick Start

File naming: *.remote.ts for remote function files

Which function? One-time action → command() | Repeated reads → query() | Forms → form()

Example

// actions.remote.ts
import { command } from "$app/server";
import * as v from "valibot";

export const delete_user = command(
  v.object({ id: v.string() }),
  async ({ id }) => {
    await db.users.delete(id);
    return { success: true };
  }
);

// Call from client: await delete_user({ id: '123' });

Reference Files

Notes

  • Remote functions execute on server when called from browser
  • Args/returns must be JSON-serializable
  • Schema validation via StandardSchemaV1 (Valibot/Zod)
  • getRequestEvent() available for cookies/headers access
  • In components: Use <svelte:boundary> + {@const await} (no flicker)
  • Refresh queries: Call query().refresh() - updates without flicker
  • Last verified: 2025-12-24
<!-- PROGRESSIVE DISCLOSURE GUIDELINES: - Keep this file ~50 lines total (max ~150 lines) - Use 1-2 code blocks only (recommend 1) - Keep description <200 chars for Level 1 efficiency - Move detailed docs to references/ for Level 3 loading - This is Level 2 - quick reference ONLY, not a manual LLM WORKFLOW (when editing this file): 1. Write/edit SKILL.md 2. Format (if formatter available) 3. Run: claude-skills-cli validate <path> 4. If multi-line description warning: run claude-skills-cli doctor <path> 5. Validate again to confirm -->