
Sveltekit Structure
spences10/svelte-skills-kit/plugins/svelte-skills/skills/sveltekit-structureby spences102a9d88379bf62cee464a16db852edda7790a58f5No licenseListed Oct 9, 2026Updated Oct 9, 2026
SvelteKit structure guidance. Use for routing, layouts, error handling, SSR, or svelte:boundary. Covers file naming, nested layouts, error boundaries, pending UI, and hydration.
- 2a9d88379bf62cee464a16db852edda7790a58f5Currentcommit 2a9d883Published Oct 9, 2026
Source and attribution
Source:spences10/svelte-skills-kitinplugins/svelte-skills/skills/sveltekit-structureat commit2a9d883
License: No license
Content belongs to its original authors. SourceWeft indexes it from a public repository.
More from spences10/svelte-skills-kit

Sveltekit Data Flow
spences10
Guidance for SvelteKit data flow: load functions, form actions, serialization, and error or redirect handling.

Svelte Runes
spences10
Guides Svelte 5 runes usage for reactive state, props, effects and migration from Svelte 4.

Svelte Components
spences10
Reference guidance on Svelte component patterns, including component libraries, web components, and form handling.
More in Software Development

Playground
anthropics
Builds self-contained interactive HTML playgrounds with controls, live preview, and copyable prompt output.

M5 Onboard
anthropics
Provisions M5Stack ESP32 boards by detecting them on USB, flashing UIFlow 2.0 firmware, and installing a MicroPython app bundle.

Cardputer Buddy
anthropics
Guides iterating on a Cardputer-Adv MicroPython app bundle: adding apps, pushing files over USB-serial, tailing logs, and running REPL commands.

Web Design Guidelines
vercel-labs
Reviews UI code against Web Interface Guidelines fetched from a remote source and reports findings as file:line entries.

Vercel React Native Skills
vercel-labs
React Native and Expo best-practice rules covering list performance, animation, navigation, UI patterns, state, and monorepo setup.

Vercel React Best Practices
vercel-labs
Vercel's React and Next.js performance guidelines, organized as 70 rules for writing, reviewing, and refactoring code.