Svelte 5 runes, component patterns, reactivity, and SvelteKit data loading best practices
99
99%
Does it follow best practices?
Impact
99%
1.11xAverage score across 10 eval scenarios
Passed
No known issues
A design tool startup is building a brand kit editor for their web app. One of the core UI pieces needed is a color picker component — a reusable Svelte component that lets users pick a color from a palette of swatches and see a live preview of the selected color.
The component needs to be genuinely reusable: the parent page must be able to read and write the currently selected color directly (two-way binding), so it can be pre-loaded with a saved brand color on mount and automatically save any changes. The component should also notify the parent whenever the selection changes via a callback so the parent can trigger autosave logic.
The team is adopting Svelte 5 and wants everything written in that style — no legacy Svelte 4 patterns.
Create the following files:
src/lib/ColorPicker.svelte — The reusable color picker component. It should:
src/routes/brand/+page.svelte — A page that:
Both files should be written for Svelte 5 with TypeScript.
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
skills
svelte-best-practices