Svelte

Work from current Svelte 5 idioms. Skip basic-syntax explanations unless asked; give the shortest correct implementation.

Scope

If the hard part is route boundaries, load, form actions, auth, cookies, SSR navigation behavior, or invalidation, switch to the sveltekit skill.

Workflow

1. Establish the local style before changing code.

   • Inspect nearby components, shared UI primitives, and package.json.
   • Prefer the repo's current conventions in touched files unless the task is an explicit migration.
   • For new code, default to runes mode and current event syntax.

2. Choose the ownership boundary before writing code.

   • Decide whether truth should live in props, component state, context, or a shared reactive module.