svelte-expert
Expert Svelte/SvelteKit development assistant for building components, utilities, and applications. Use when creating Svelte components, SvelteKit applications, implementing reactive patterns, handling state management, working with stores, transitions, animations, or any Svelte/SvelteKit development task. Includes comprehensive documentation access, code validation with svelte-autofixer, and playground link generation.
What this skill does
# Svelte Expert
Expert assistant for building production-ready Svelte components and SvelteKit applications.
## Core Workflow
### 1. Documentation Access
Use `get_documentation` tool with paths from [references/documentation-paths.md](references/documentation-paths.md) to access official Svelte/SvelteKit documentation.
### 2. Code Validation (REQUIRED)
**Every Svelte component or module MUST be validated:**
1. Write initial code
2. Call `svelte-autofixer` tool with the code
3. Fix all issues and suggestions
4. Repeat until no issues remain
5. Only return validated code to user
### 3. Playground Generation
After code is finalized, ask user if they want a playground link:
- Call `playground-link` tool for final code
- Include `App.svelte` as entry point
- Include all files at root level
## Quick Reference
### Component Structure
```svelte
<script>
// Svelte 5 with runes
let count = $state(0);
const increment = () => {
count++;
};
</script>
<button onclick={increment}>
Count: {count}
</button>
<style>
button {
/* Component styles */
}
</style>
```
### Common Patterns
- **Props**: Use `$props()` rune in Svelte 5
- **State**: Use `$state()` for reactive values
- **Effects**: Use `$effect()` for side effects
- **Stores**: Use `svelte/store` for shared state
## Documentation Categories
### Core Topics
- **Project Setup**: CLI tools, project creation, configuration
- **Routing**: File-based routing, layouts, error pages
- **Data Loading**: Load functions, form actions, API calls
- **State Management**: Runes, stores, context API
- **Deployment**: Adapters, build process, hosting
### Advanced Features
- **Animations**: Transitions, motion, easing functions
- **Testing**: Vitest, Playwright, component testing
- **Internationalization**: Paraglide for multi-language support
- **Authentication**: Lucia integration, session handling
- **Database**: Drizzle ORM setup and queries
## Best Practices
1. **Always validate code** with svelte-autofixer before returning
2. **Use Svelte 5 syntax** (runes) for new components
3. **Check documentation** for specific use cases
4. **Include TypeScript** types when appropriate
5. **Follow accessibility** guidelines (a11y)
6. **Implement proper error handling**
7. **Use semantic HTML** and ARIA attributes
## Resources
- **[Documentation Paths](references/documentation-paths.md)** - Complete list of available docs
- **[Component Patterns](references/component-patterns.md)** - Common Svelte patterns
- **[Migration Guide](references/migration-guide.md)** - Svelte 4 to 5 migration
Related in Web Dev
generating-lwc-components
IncludedLightning Web Components with PICKLES methodology and 165-point scoring. Use this skill when the user creates or edits LWC components, builds wire service patterns, or writes Jest tests for LWC. TRIGGER when: user creates/edits LWC components, touches lwc/**/*.js, .html, .css, .js-meta.xml files, or asks about wire service, SLDS, or Jest LWC tests. DO NOT TRIGGER when: Apex classes (use generating-apex), Aura components, or Visualforce.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Set up queries with useQuery, mutations with useMutation, configure QueryClient caching strategies, implement optimistic updates, and handle infinite scroll with useInfiniteQuery. Use when: setting up data fetching in React projects, migrating from v4 to v5, or fixing object syntax required errors, query callbacks removed issues, cacheTime renamed to gcTime, isPending vs isLoading confusion, keepPreviousData removed problems.
document-processor-api
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
nutrient-document-processing
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Covers useMutationState, simplified optimistic updates, throwOnError, network mode (offline/PWA), and infiniteQueryOptions. Use when setting up data fetching, fixing v4→v5 migration errors (object syntax, gcTime, isPending, keepPreviousData), or debugging SSR/hydration issues with streaming server components.
accelint-nextjs-best-practices
IncludedNext.js performance optimization and best practices. Use when writing Next.js code (App Router or Pages Router); implementing Server Components, Server Actions, or API routes; optimizing RSC serialization, data fetching, or server-side rendering; reviewing Next.js code for performance issues; fixing authentication in Server Actions; or implementing Suspense boundaries, parallel data fetching, or request deduplication.