svelte-core-bestpractices

Svelte best practices for reactivity involve using $state for mutable values, $derived for computed values, and $effect for side effects to ensure fast, robust component data flow. This skill provides vetted guidance on applying these patterns correctly.

Structuring Svelte components for maintainability requires following vetted best practices for component composition, styling, and event handling. This skill offers guidance on assessing component boundaries and improving testability during refactoring.

Yes, you can apply these Svelte best practices when refactoring an existing web application. The skill is designed to guide developers during writing, reviewing, or analyzing components to improve performance and reliable UI behavior.

The best way to handle events and data flow in Svelte is by applying practical reactivity patterns using $state, $derived, and $effect. This skill provides clear guidance on these patterns for robust component design.

Yes, this guidance covers library integration best practices for Svelte projects. It provides vetted recommendations to improve performance and maintainability when integrating external libraries into your components.

YAML frontmatter with a name and description is required for discovery and linking to optional references, scripts, or assets. It ensures the Svelte best-practice guidance is properly structured and accessible when analyzing components.