What problem does it solve?
Building Svelte 5 components that are accessible, performant, and follow industry best practices often requires piecing together fragmented guidance, leading to inconsistent implementations, poor accessibility compliance, and unnecessary JavaScript bloat from custom solutions that replicate native browser functionality.
Core Features & Use Cases
- Semantic HTML Enforcement: Guides developers to use native HTML elements instead of custom divs to leverage built-in accessibility, reduce bundle size, and improve cross-browser performance.
- Svelte 5 & Tailwind 4.2 Best Practices: Provides patterns for Svelte 5 runes, callback props, modern CSS features, and Tailwind integration to build maintainable, type-safe components.
- Accessibility & Testing Guidance: Includes WCAG 2.1 compliance checklists, ARIA usage rules, and examples for unit (Vitest) and E2E (Playwright) testing to ensure components work for all users.
- Use Case: A frontend developer building a design system for a Svelte 5 app can use this skill to create a reusable Button component that is fully keyboard accessible, supports screen readers, and uses native browser functionality instead of custom JavaScript.
Quick Start
Use the svelte-components skill to build an accessible, type-safe Progress component for your Svelte 5 app using the native HTML progress element and Tailwind 4.2 styling.