Audit Your SvelteKit Codebase with a JSON Feed of 34 Svelte 5 Patterns

My Migrate to Svelte 5 site started as a side-by-side reference for developers wanting to convert to Svelte 5, from React, Vue, or Angular. It maps concepts across frameworks: "your useState is Svelte's $state," "your useEffect is $effect," and so on — about 300 entries covering syntax, architecture, and ecosystem. That's useful, for a human reading the site. But I kept running into a different scenario: working in a SvelteKit codebase with Claude Code and wanting to ask "go check what's new in Svelte and see what applies here." Because that kind of quick synthesis is what AI Agents are good at. The data was all on the site, but there was no machine-friendly way to query it for actionable patterns. So I added two things to the site: a structured patterns feed and a browsable patterns page. This post covers the thinking and the implementation. The Problem with Static Migration Guides A migration guide answers "how do I do X in Svelte?" That's a pull interaction — the developer has a que