# svelte evals

These cases are prompts for sanity-checking the skill router and the skill's output quality; no automated runner ships here. Feed each `should_trigger` prompt to your router and confirm it selects `svelte`; feed each `should_not_trigger` prompt and confirm it routes to the named sibling (`nextjs`, `typescript`, `vercel`, `cloudflare`) instead. For the `capability` case, have the skill produce the SvelteKit `/dashboard` route and grade the result against the `must_include` rubric — the correct file split (server-only `load`/`actions`, no secret in universal load), runes usage (`$props`/`$derived`, not `$effect` for computed values), `use:enhance`, and typing from `./$types`. The `why`/`route_to` fields document intent; they are read by humans, not executed.
