What is UI Kit Adapter?
One component kit per app — shadcn-svelte, Flowbite, Skeleton, or DaisyUI — chosen at setup and used consistently. One kit means one visual language and one upgrade path.
Related terms
Tailwind CSS 4 & app.css Tokens
Theme variables extended, never rewritten: generated apps customize the design system through tokens so regeneration preserves the brand instead of resetting it.
Svelte Components
Reusable UI units (.svelte files) composing a SvelteKit app. Generated projects keep components small and named by feature so humans and AI alike can modify them safely.
Redesign Patterns
Repeatable fixes for common generated-site flaws: hierarchy, spacing rhythm, contrast, and component consistency. Auditing new builds against patterns beats redesigning from taste.
Svelte Runes
The `$state`, `$derived`, `$effect`, and `$props` primitives powering Svelte 5 reactivity. Runes are mandatory in generated code: explicit, compilable, and consistent across every component.
File-Based Routing
Pages defined by file location: `+page.svelte` renders, `+layout.svelte` wraps, `+server.js` serves data. The route tree is the app map — no separate router config to drift.
Load Function
Server-side data loading for a route before it renders. Load on the server for content crawlers and users need immediately; reach for client fetching only for interactive extras.