What is 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.
Related terms
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.
llms.txt
An experimental convention (a Markdown file at /llms.txt) that summarizes a site for language models. Adoption and crawler support are still thin, so it sits below core crawlability and content quality in priority.
Machine-Readable Content
Content structured so parsers extract it reliably: semantic HTML, one H1, real lists and tables, descriptive link text, alt text, and schema that mirrors visible content.
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.