Orient Claude to the svelteflare monorepo before starting any task. Use this skill whenever the user says "orient yourself", "explain the repo", "what's the structure here", or kicks off a task where knowing where things live matters. Also invoke it proactively at the start of a new session in this repo — it saves repeated filesystem spelunking and gives you the full picture in one read.
Frontend/design system skill for the svelteflare monorepo. Use this whenever the user wants to build or modify UI — pages, sections, components, layouts, forms, cards, tables, dialogs, dashboards, or landing pages. Also invoke for anything theme-related: light/dark mode, custom colors, design tokens, typography, or spacing. Trigger on "add a [card/table/dialog/form/dashboard]", "build a [landing/marketing] section", "change the theme", "add dark mode", "customize colors", "install [shadcn component]", "make it look like X", "style this", "create a [component]". When in doubt, invoke — this skill prevents hard-coded colors, raw HTML elements, and design inconsistencies.
Backend product systems skill for the svelteflare monorepo. Invoke whenever the user wants to work with auth, sessions, protected routes, users, the database, schema changes, migrations, Stripe billing, subscriptions, paid feature gates, or any server-only logic in the Hono API. Trigger on "add a protected route", "gate this behind a subscription", "add a DB column", "run migrations", "how do I check if the user is logged in", "add a new table", "wire up Stripe checkout", "check the user's plan", "add a role check", "add server-only logic", or any mention of better-auth, drizzle, D1, or Stripe. When in doubt, invoke — this skill prevents auth bypasses, wrong DB access patterns, and billing logic landing in the wrong layer.
Main orchestration skill for adding features to the svelteflare monorepo. Invoke whenever the user wants to add, build, implement, or create any new functionality — a page, API endpoint, DB table, form, component, auth-gated route, billing feature, or any combination. Trigger on "add X", "build X", "implement X", "I want X to do Y", "create a [page/endpoint/form/feature]", "wire up X", "make it so users can X". When in doubt, invoke — it's better to orchestrate than to start coding blind in a multi-layer monorepo.
Form handling skill for the svelteflare monorepo. Use this whenever the user wants to add, build, or modify any form — login forms, settings forms, profile editors, onboarding flows, multi-step wizards, or any input that validates and submits data. Covers the full stack: Zod schema, superforms setup, FormSnap field components, field-level errors, loading/success/error states, and toast feedback. Trigger on "add a form", "build a form for X", "create a settings page", "add a field", "handle form submission", "validate input", "show errors", "wire up a form to the API". When in doubt, invoke — this skill prevents inconsistent patterns, missing validation, and broken error handling.
Guidance on writing fast, robust, modern Svelte code. Load this skill whenever in a Svelte project and asked to write/edit or analyze a Svelte component or module. Covers reactivity, event handling, styling, integration with libraries and more.