svelte5-stack

To enforce Svelte 5 runes conventions, apply a Skill that mandates the use of `$state`, `$derived`, `$effect`, and `$props` over legacy Svelte patterns in all components and route files. This ensures modern SvelteKit state management consistency.

Standardizing shadcn-svelte and TailwindCSS involves enforcing a Skill that promotes shadcn-svelte components for UI elements like tables and cards. This guarantees a unified look and feel across your SvelteKit application's interactive dashboard and forms.

Drizzle ORM works with Supabase for SvelteKit server logic by enforcing a strict data layer adherence. A Skill can mandate Drizzle ORM for all database interactions, ensuring type-safe queries and consistent data fetching from your Supabase backend.

To refactor a legacy Svelte component to Svelte 5 runes, use a Skill to guide the transformation of existing state management. This ensures the updated component correctly implements `$state` and `$props` while integrating shadcn-svelte UI elements.

You can use TypeScript strict typing with SvelteKit and Drizzle ORM by enforcing a Skill that mandates well-defined interfaces. This prevents the use of `any` and ensures strict TypeScript typing across all server logic and database interactions.

You should use Svelte 5 runes instead of legacy Svelte patterns for all new interactive components and route files. Enforcing this convention guarantees adherence to modern Svelte patterns, preventing legacy code from causing inconsistencies in your SvelteKit project.