Svelte Component Factoring

Use this skill when the real question is not "can this markup be extracted?" but "who owns this behavior, state, remote result, and proof?"

Required Sources

• Read the current component, route, tests, and nearby patterns before proposing a boundary.
• Use the official Svelte/SvelteKit docs for APIs touched by the change, especially context, $derived, $effect, remote functions, async boundaries, and testing.
• Read any accepted design artifact or ADR for the affected route before moving ownership.

Factoring Standard

Prefer components that own one product job end to end: