Curious about Svelte but comfortable with React? Join us as we take a simple NEXT/React app and migrate it live to SvelteKit/Svelte, showing how your existing React knowledge translates directly to Svelte concepts.

How we're progressively moving an actively worked on codebase (with 4 engineers) into SvelteKit, to enable us to progressively enhance the frontend with Svelte + Kit whilst minimising impact on product velocity.

What happens when you need to refactor 377 files in a SvelteKit codebase? Without AI, you retire. With Claude Code, you ship it in 11 hours.

This talk walks through real-world examples of using Claude Code for massive refactoring work that would be soul-crushing to do manually. I'll cover:

How I approach large-scale refactors with Claude (377 files → 364 files → and counting)

Building and activating Claude Code skills reliably (based on my viral post that's getting 4k+ views in 3 days)

The workflow patterns that actually work vs the ones that waste your time

Real examples from production codebases

This isn't about AI replacing developers - it's about using AI to handle the tedious parts so you can focus on the interesting problems.

The brand new view transition API is hot right now, sveltekit recently added a way to interact with it and while really powerful it's pretty low level. But what if there was a better way?

The brand new view transition API is hot right now, sveltekit recently added a way to interact with it and while really powerful it's pretty low level. But what if there was a better way?