What is 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.
Related terms
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.
Protected Platform Files
The glue agents must not rewrite: layout, app.html, vite config, package manifest, llms.txt, env files. Protection keeps regeneration from destroying working infrastructure.
Design Mixer Patterns
A library of composable visual directions (around 30 named patterns) the mixer combines per project. Patterns give the model a vocabulary beyond the default neutral look it reaches for otherwise.
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.