OpenParable
Skip to content
← Back to skills

Sveltekit

Development
sveltekit

Sveltekit is an Agent Skill for development published in the EpicenterHQ/epicenter repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

SvelteKit routing, load functions, server-only modules, form actions, hooks, cookies, env, adapters, and invalidation. Use when editing +page.ts, +page.server.ts, +layout.ts, +server.ts, hooks.server.ts, app.d.ts, or SvelteKit route behavior.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/EpicenterHQ/epicenter/blob/HEAD/.agents/skills/sveltekit/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/sveltekit, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

SvelteKit

Reference Repositories

  • SvelteKit - Svelte application framework for routing, server rendering, form actions, and adapters
  • Svelte - Svelte 5 compiler and runtime

Upstream Grounding

When SvelteKit load behavior, invalidation, cookies, hooks, env handling, server-only modules, generated $types, or adapter behavior affects correctness, ask DeepWiki a narrow question against sveltejs/kit before relying on memory. Verify decisive details against local installed types and source.

Use the svelte skill for component runes and template mechanics.

Server Versus Universal Code

  • Use +page.server.ts or +layout.server.ts for secrets, database access, auth, cookies, and locals.
  • Use universal +page.ts or +layout.ts only for client-safe data and behavior.
  • Keep server-only code in $lib/server, .server modules, hooks.server.ts, +server.ts, or server route files.
  • Server load return values must be serializable.
  • Do not store shared mutable request state in server modules or load functions. Put per-request state in event.locals.

Loading, Invalidation, And Forms

  • Use depends, invalidate, invalidateAll, and untrack deliberately. Do not assume server fetches are invalidation-trackable unless the dependency is explicit.
  • Define form actions in +page.server.ts.
  • Use fail() for validation failures so the page keeps form state and status.
  • Use use:enhance only for POST forms.
  • Put auth and session lookup in hooks.server.ts, then expose the request result through event.locals.

Types And Boundaries

  • Import generated route types from ./$types in route files.
  • Keep env reads in server code unless the value is intentionally public.
  • Keep redirects and errors explicit with SvelteKit helpers so status codes survive SSR and client navigation.