SK Minimal

SK Minimal does exactly what it says. TypeScript configured properly, Tailwind ready to go, a clean folder structure, and nothing else. No auth you’ll rip out. No database config you’ll change. No component library you’ll replace.

This is the starter for developers who have opinions about their stack and just need the SvelteKit foundation done right.

What stands out

The project structure. Layouts, shared components, utility functions, and type definitions are all where you’d expect them. The Tailwind config extends sensibly without going overboard. ESLint and Prettier are pre-configured with Svelte-specific rules.

Svelte 5 runes are used throughout — no legacy reactive statements. If you’re learning runes, this is a clean reference implementation.

The project structure follows a clear convention: src/lib/components for shared UI, src/lib/utils for helpers, src/lib/types for TypeScript definitions, and src/routes kept deliberately flat. There are no deeply nested route groups or layout gymnastics — just a root layout with a slot, a single +error.svelte, and example pages you can delete without consequence. The $lib alias is pre-configured, and path aliases for $components and $utils are already set in svelte.config.js.

Runes appear in practical patterns: $state for component-local reactivity, $derived for computed values in utility functions, and $effect used sparingly in the example toast notification component. The starter avoids $effect overuse — a common trap for developers migrating from Svelte 4’s reactive statements — which makes it a reliable reference for idiomatic Svelte 5 code.

Where it could improve

If you’re building anything with user accounts, you’re on your own. That’s by design, but it means SK Minimal is a starting line, not a shortcut. Budget time for integrating your auth and database layers.

The lack of a component library means your first few hours will be building buttons, inputs, and modals. Consider pairing with shadcn-svelte if you want to move faster.