Sponsored by

Find leads on Reddit on auto pilot

Agent skills
sveltekit

Topic: sveltekit

57 skills in this topic.

sveltekit-data-flow 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().
spences10/svelte-skills-kit 64
svelte-deployment Svelte deployment guidance. Use for adapters, Vite config, pnpm setup, library authoring, PWA, or production builds.
spences10/svelte-skills-kit 64
svelte-runes Svelte runes guidance. Use for reactive state, props, effects, or migration. Covers $state, $derived, $effect, $props, $bindable. Prevents reactivity mistakes.
spences10/svelte-skills-kit 64
ecosystem-guide 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.
spences10/svelte-skills-kit 64
svelte-template-directives
spences10/svelte-skills-kit 64
layerchart-svelte5 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.
spences10/svelte-skills-kit 64
sveltekit-structure SvelteKit structure guidance. Use for routing, layouts, error handling, SSR, or svelte:boundary. Covers file naming, nested layouts, error boundaries, pending UI, and hydration.
spences10/svelte-skills-kit 64
svelte-styling
spences10/svelte-skills-kit 64
sveltekit-remote-functions SvelteKit remote functions guidance. Use for command(), query(), form() patterns in .remote.ts files.
spences10/svelte-skills-kit 64
svelte-components Svelte component patterns. Use for web components, component libraries (Bits UI, Ark UI, Melt UI), form patterns, or third-party integration.
spences10/svelte-skills-kit 64
git Git commit and pull request guidelines using conventional commits. Use when the user says "commit this", "stage and commit", "write a commit message", "create a PR", or when creating commits, writing commit messages, or reviewing PR descriptions.
EpicenterHQ/epicenter 4,333
better-auth-best-practices Configure Better Auth server and client, set up database adapters, manage sessions, add plugins, and handle environment variables. Use when users mention Better Auth, betterauth, auth.ts, or need to set up TypeScript authentication with email/password, OAuth, or plugin configuration.
EpicenterHQ/epicenter 4,333
web-design-guidelines Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
EpicenterHQ/epicenter 4,333
change-proposal Present proposed code changes visually before implementing. Use when the user says "show me options", "compare approaches", "what should we do", or when multiple approaches exist, changes span multiple files, or architecture decisions need before/after comparison.
EpicenterHQ/epicenter 4,333
honesty Behavioral guideline for providing brutally honest feedback. Use always - this skill defines core interaction expectations for code review and technical discussions.
EpicenterHQ/epicenter 4,333
refactoring Systematic code audit and refactoring methodology—caller counting, type safety boundaries, inlining single-use extractions, keeping trivial duplications inline over premature extraction, collapsing duplicate branches, and surgical commits. Use when cleaning up code, auditing for code smells, refactoring modules, or reviewing internal function structure.
EpicenterHQ/epicenter 4,333
github-issues GitHub issue comment guidelines for community interaction. Use when the user says "respond to this issue", "reply to this bug report", "close this issue", or when responding to GitHub issues, bug reports, feature requests, or any GitHub discussion.
EpicenterHQ/epicenter 4,333
typescript TypeScript code style, type co-location, naming conventions (including acronym casing), and arktype patterns. Use when the user mentions TypeScript types, naming conventions, or when writing .ts files, defining types, naming variables/functions, or organizing test files.
EpicenterHQ/epicenter 4,333
specification-writing Write technical specifications that give agents enough context to implement features autonomously. Use when the user says "write a spec", "plan this feature", "create a planning doc", or when planning features, documenting architecture decisions, or creating implementation guides.
EpicenterHQ/epicenter 4,333
rust-errors Rust to TypeScript error handling patterns for Tauri apps. Use when the user mentions Rust errors, Tauri command errors, invoke errors, or when defining Rust error types for TypeScript consumption or creating discriminated union error types from Rust.
EpicenterHQ/epicenter 4,333
arktype Arktype patterns for runtime validation, discriminated unions with .merge() and .or(), spread key syntax, and type composition. Use when the user mentions arktype, type(), or when building union types, combining schemas with variants, or defining command/event schemas.
EpicenterHQ/epicenter 4,333
email-and-password-best-practices Configure email verification, implement password reset flows, set password policies, and customise hashing algorithms for Better Auth email/password authentication. Use when users need to set up login, sign-in, sign-up, credential authentication, or password security with Better Auth.
EpicenterHQ/epicenter 4,333
elysia Elysia.js server patterns for error handling, status responses, and plugin composition. Use when the user mentions Elysia, Eden Treaty, or when writing API route handlers, returning HTTP errors, creating server plugins, or working with type-safe API clients.
EpicenterHQ/epicenter 4,333
drizzle-orm Drizzle ORM patterns for type branding, custom types, and SQLite column definitions. Use when the user mentions Drizzle, drizzle-orm, or when working with database schemas, branded column types, or custom type conversions in Drizzle.
EpicenterHQ/epicenter 4,333