What is 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.
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.
llms.txt
A machine-readable site map every generated app must carry. It tells AI agents what the site is and where things live — required infrastructure, not an afterthought.
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.
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.
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.
Form Actions
Progressive-enhancement mutations: forms that work without JavaScript and upgrade with it. The default for generated app mutations — resilient and accessible by construction.