kf-g-sveltekit-docs

SvelteKit official docs reference rules

The purpose of this skill is to keep references consistent when handling SvelteKit-specific specifications.

Background

• Because SvelteKit skills are not officially provided, SvelteKit-specific information is treated as primary information under https://svelte.dev/docs/kit treat the files under this as primary information
• Do not assert SvelteKit-specific specifications based only on memory or general Svelte knowledge

When to use

• +page +layout +server file conventions such as
• routing params layout error loading
• load actions redirect error
• hooks handle handleFetch
• ssr csr prerender trailingSlash page options such as
• adapters deploy build env modules
• $app/* $env/* @sveltejs/kit API

Basic rules

1. First check the local implementation and configuration
2. When SvelteKit-specific specifications or APIs are involved,https://svelte.dev/docs/kit check the relevant page under this
3. In answers and implementations, use the docs terminology and file names as-is
4. If it is about general Svelte features, prioritize referencing the svelte-code-writer や svelte-core-bestpractices skill, and supplement only the SvelteKit-specific parts with this skill
5. Do not confuse Svelte with SvelteKit

Guideline for what to check

• For routing, Routing Advanced routing
• For data fetching, Loading data
• For form submission, Form actions
• For execution environment or rendering mode, Page options
• For server processing, Hooks Server-only modules
• For deployment, Adapters Node servers Static site generation Single-page apps
• For API reference, Reference section

URL list (as of 2026/07/06)

• /introduction
• /creating-a-project
• /project-types
• /project-structure
• /web-standards
• /routing
• /load
• /form-actions
• /page-options
• /state-management
• /remote-functions
• /environment-variables
• /building-your-app
• /adapters
• /adapter-auto
• /adapter-node
• /adapter-static
• /single-page-apps
• /adapter-cloudflare
• /adapter-cloudflare-workers
• /adapter-netlify
• /adapter-vercel
• /writing-adapters
• /advanced-routing
• /hooks
• /errors
• /link-options
• /service-workers
• /server-only-modules
• /snapshots
• /shallow-routing
• /observability
• /packaging
• /auth
• /performance
• /icons
• /images
• /accessibility
• /seo
• /faq
• /integrations
• /debugging
• /migrating-to-sveltekit-2
• /migrating
• /additional-resources
• /glossary
• /@sveltejs-kit
• /@sveltejs-kit-hooks
• /@sveltejs-kit-node-polyfills
• /@sveltejs-kit-node
• /@sveltejs-kit-vite
• /$app-env
• /$app-env-private
• /$app-env-public
• /$app-environment
• /$app-forms
• /$app-navigation
• /$app-paths
• /$app-server
• /$app-state
• /$app-stores
• /$app-types
• /$env-dynamic-private
• /$env-dynamic-public
• /$env-static-private
• /$env-static-public
• /$lib
• /$service-worker
• /configuration
• /cli
• /types

Final check

• Are you asserting SvelteKit-specific specifications based only on memory?
• https://svelte.dev/docs/kit Have you overlooked whether this is a point that should reference something under
• Are general Svelte topics and SvelteKit-specific topics separated?