svelte-components
Svelte component patterns. Use for web components, component libraries (Bits UI, Ark UI, Melt UI), form patterns, or third-party integration.
Browse published AI skills maintained by spences10. Compare skill descriptions and follow each source repository for setup instructions.
Indexed skills
39Repository stars across indexed skills
1,858Repository forks
202Average repository stars per indexed skill
48Repository stars may repeat across skills from the same repository.
Svelte component patterns. Use for web components, component libraries (Bits UI, Ark UI, Melt UI), form patterns, or third-party integration.
Svelte runes guidance. Use for reactive state, props, effects, attachments, or migration. Covers $state, $derived, $effect, @attach. Prevents reactivity mistakes.
Svelte deployment guidance. Use for adapters, Vite config, pnpm setup, library authoring, PWA, or production builds.
Research topics by verifying actual source content. Use when asked to research or study links and documentation.
SvelteKit remote functions guidance. Use for command(), query(), form() patterns in .remote.ts files.
SvelteKit data flow guidance. Use for load functions, form actions, and server/client data. Covers +page.server.ts vs +page.ts, serialization, fail(), redirect(), error().
SvelteKit structure guidance. Use for routing, layouts, error handling, SSR, or svelte:boundary. Covers file naming, nested layouts, error boundaries, pending UI, and hydration.
Fix and create Svelte 5 tests with vitest-browser-svelte and Playwright. Use when fixing broken tests, debugging failures, writing unit/SSR/e2e tests, or working with vitest/Playwright.
Create new blog posts with proper frontmatter, structure, and ScottInk voice. Use when writing blog posts or starting technical articles.
Audit local analytics for bot traffic, referrer spam, and data quality. Use when investigating discrepancies between Fathom and local stats.
Validate blog posts for quality, consistency, en-GB spelling, and ScottInk style. Use when reviewing posts before publication.
Prepare newsletters for publication by validating format, structure, frontmatter, and content. Use when reviewing drafts before sending.
Write in Scott's authentic voice - British, conversational, self-deprecating, code-first. Use when writing blog posts, technical content, or documentation.
Lint content for spelling errors, en-GB compliance, and writing quality. Use when checking markdown files before publication.
Use when building, auditing, or reviewing SvelteKit remote functions for validation, batching, and optimistic UI patterns
SvelteKit data flow guidance. Use for load functions, form actions, server/client data, and invalidation. Covers +page.server.ts vs +page.ts, serialization, fail(), redirect(), error(), invalidateAll().
Guide to spences10's Claude Code ecosystem. Use when user asks which tool to use, how tools relate, or needs help choosing between MCP servers, skills, or CLIs.
LayerChart Svelte 5 patterns. Use for chart components with tooltip snippets, Chart context access, and all Svelte 5 snippet patterns for tooltips, gradients, highlights, and axes.
Svelte template directives ({@attach}, {@html}, {@render}, {@const}, {@debug}). Use for DOM manipulation, third-party libs, tooltips, canvas, dynamic HTML. @attach replaces use: actions.
Svelte runes guidance. Use for reactive state, props, effects, or migration. Covers $state, $derived, $effect, $props, $bindable. Prevents reactivity mistakes.
SvelteKit remote functions guidance. Use for command(), query(), form() patterns in .remote.ts files.
Query Claude Code session analytics from cclog database. Use when user asks about token usage, costs, session history, or wants to analyze their Claude Code usage patterns.
Setup guide for essential MCP servers. Use when configuring MCP servers or when user asks about search, SQLite, or MCP management.
Analyze session history for learnings and persist to skills. Solves "memory zero" - correct once, never again.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.