What is 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.
Related terms
SvelteKit
The full-stack framework BYOB generates: Svelte 5 components with server rendering, file-based routing, and edge deployment. Standard code any developer can extend outside the builder.
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.
Skill Routing
Loading mandatory domain bundles (frontend, database, payments, auth, SEO, PWA, motion) before acting in that domain. Routing is why generated code follows one convention instead of improvising per prompt.
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.
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.