What is Frontend Review / Critic Loop?
Screenshot-only scoring out of ten with a two-iteration cap. The critic sees pixels, not code — which is exactly what users see too.
Example
A generated landing scores 6/10 (“hero competes with nav, CTA below fold on mobile”); two focused iterations land it at 9 without a redesign spiral.
Related terms
Visual Testing Agent
A preview-URL auditor that checks rendered pages like a visitor would. Read-only by default; writes structured findings the builder can act on.
Design Antipatterns
Banned default aesthetics: neutral cream palettes, generic serif editorial looks, muted placeholder styling. Naming what good taste excludes keeps generated design from converging on the same safe average.
User-Facing Copy
Outcome-first interface text: CTAs, errors, empty states, and paywalls written for the user’s job, not the implementation. Good microcopy converts; placeholder copy leaks trust.
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.