Topic: svelte
68 skills in this topic.
-
tauri
Tauri path handling, cross-platform file operations, and API usage. Use when the user mentions Tauri, desktop app, or when working with file paths in Tauri frontend code, accessing native filesystem APIs, invoking Tauri commands, or handling platform differences.
EpicenterHQ/epicenter 4,333
-
technical-articles
Write technical articles and blog posts with depth and honest trade-offs. Use when the user says "write a blog post", "draft an article", "write about this", or when creating articles in docs/articles/ explaining patterns, techniques, or lessons learned.
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
-
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
-
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
-
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
-
workspace-api
Workspace API patterns for defineTable, defineKv, versioning, migrations, and data access (CRUD + observation). Use when the user mentions workspace, defineTable, defineKv, createWorkspace, or when defining schemas, reading/writing table data, observing changes, or writing migrations.
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
-
method-shorthand-jsdoc
Move helper functions into return objects using method shorthand for proper JSDoc preservation. Use when factory functions have internal helpers that should expose documentation to consumers, or when hovering over returned methods shows no JSDoc.
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
-
encryption
Encryption patterns for HKDF key derivation, XChaCha20-Poly1305 symmetric encryption, encrypted blob formats, key hierarchy, and key rotation. Use when the user says "encrypt this", "add encryption", "key management", or when working with crypto primitives, encrypted CRDT values, or the EncryptedBlob type.
EpicenterHQ/epicenter 4,333
-
error-handling
Error handling patterns using wellcrafted trySync and tryAsync. Use when writing or reviewing try-catch blocks, refactoring try-catch to linear control flow, working with Result types, or returning HTTP error responses from route handlers.
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
-
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
-
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
-
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
-
incremental-commits
Break multi-file changes into atomic commits ordered by dependency. Use when the user says "split this into commits", "commit strategy", "break this up", or when making refactors, breaking API changes, or features touching 3+ files that need clean git history.
EpicenterHQ/epicenter 4,333
-
control-flow
Human-readable control flow patterns for early returns, guard clauses, and linearizing nested logic. Use when the user says "simplify this", "flatten these conditions", "too many nested ifs", or when refactoring nested conditionals, replacing try-catch with linear flow, or restructuring decision logic.
EpicenterHQ/epicenter 4,333
-
documentation
In-code documentation, folder READMEs, and code comments. Use when the user says "document this", "add JSDoc", "write a README", "explain this code", or when writing README.md files, JSDoc comments, or code organization docs.
EpicenterHQ/epicenter 4,333
-
define-errors
How to define and use defineErrors from wellcrafted. Use when creating new error types, updating error definitions, or reviewing error patterns. Covers variant factories, extractErrorMessage for cause, InferErrors/InferError for types, and call site patterns.
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
-
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
-
services-layer
Service layer patterns with defineErrors, namespace exports, and Result types. Use when the user says "create a service", "service layer", or when creating new services, defining domain-specific errors, or understanding the service architecture.
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