[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72ABG0NT7P6VCFNCZ5G6PRF":3,"skill-same:01M72ABG0NT7P6VCFNCZ5G6PRF":58},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":38,"commitSha":39,"skillDirectory":40,"forksCount":13,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":43,"install":44,"resources":57},"01M72ABG0NT7P6VCFNCZ5G6PRF","sveltekit",null,"Build full-stack web applications with SvelteKit — file-based routing, SSR, SSG, API routes, and form actions in one framework.","Sansar35\u002Fclaude-agent","Sansar35","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F145020281?v=4","01M724CQ2SCC86MGNSD87D0D4K","01M724CQ3965G9WJ3QXE3AJ5YY",1,"MIT","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fantigravity\u002Fsveltekit\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: sveltekit\ndescription: \"Build full-stack web applications with SvelteKit — file-based routing, SSR, SSG, API routes, and form actions in one framework.\"\ncategory: frontend\nrisk: safe\nsource: community\ndate_added: \"2026-03-18\"\nauthor: suhaibjanjua\ntags: [svelte, sveltekit, fullstack, ssr, ssg, typescript]\ntools: [claude, cursor, gemini]\n---\n\n# SvelteKit Full-Stack Development\n\n## Overview\n\nSvelteKit is the official full-stack framework built on top of Svelte. It provides file-based routing, server-side rendering (SSR), static site generation (SSG), API routes, and progressive form actions — all with Svelte's compile-time reactivity model that ships zero runtime overhead to the browser. Use this skill when building fast, modern web apps where both DX and performance matter.\n\n## When to Use This Skill\n\n- Use when building a new full-stack web application with Svelte\n- Use when you need SSR or SSG with fine-grained control per route\n- Use when migrating a SPA to a framework with server capabilities\n- Use when working on a project that needs file-based routing and collocated API endpoints\n- Use when the user asks about `+page.svelte`, `+layout.svelte`, `load` functions, or form actions\n\n## How It Works\n\n### Step 1: Project Setup\n\n```bash\nnpm create svelte@latest my-app\ncd my-app\nnpm install\nnpm run dev\n```\n\nChoose **Skeleton project** + **TypeScript** + **ESLint\u002FPrettier** when prompted.\n\nDirectory structure after scaffolding:\n\n```\nsrc\u002F\n  routes\u002F\n    +page.svelte        ← Root page component\n    +layout.svelte      ← Root layout (wraps all pages)\n    +error.svelte       ← Error boundary\n  lib\u002F\n    server\u002F             ← Server-only code (never bundled to client)\n    components\u002F         ← Shared components\n  app.html              ← HTML shell\nstatic\u002F                 ← Static assets\n```\n\n### Step 2: File-Based Routing\n\nEvery `+page.svelte` file in `src\u002Froutes\u002F` maps directly to a URL:\n\n```\nsrc\u002Froutes\u002F+page.svelte          → \u002F\nsrc\u002Froutes\u002Fabout\u002F+page.svelte    → \u002Fabout\nsrc\u002Froutes\u002Fblog\u002F[slug]\u002F+page.svelte  → \u002Fblog\u002F:slug\nsrc\u002Froutes\u002Fshop\u002F[...path]\u002F+page.svelte → \u002Fshop\u002F* (catch-all)\n```\n\n**Route groups** (no URL segment): wrap in `(group)\u002F` folder.\n**Private routes** (not accessible as URLs): prefix with `_` or `(group)`.\n\n### Step 3: Loading Data with `load` Functions\n\nUse a `+page.ts` (universal) or `+page.server.ts` (server-only) file alongside the page:\n\n```typescript\n\u002F\u002F src\u002Froutes\u002Fblog\u002F[slug]\u002F+page.server.ts\nimport { error } from '@sveltejs\u002Fkit';\nimport type { PageServerLoad } from '.\u002F$types';\n\nexport const load: PageServerLoad = async ({ params, fetch }) => {\n  const post = await fetch(`\u002Fapi\u002Fposts\u002F${params.slug}`).then(r => r.json());\n\n  if (!post) {\n    error(404, 'Post not found');\n  }\n\n  return { post };\n};\n```\n\n```svelte\n\u003C!-- src\u002Froutes\u002Fblog\u002F[slug]\u002F+page.svelte -->\n\u003Cscript lang=\"ts\">\n  import type { PageData } from '.\u002F$types';\n  export let data: PageData;\n\u003C\u002Fscript>\n\n\u003Ch1>{data.post.title}\u003C\u002Fh1>\n\u003Carticle>{@html data.post.content}\u003C\u002Farticle>\n```\n\n### Step 4: API Routes (Server Endpoints)\n\nCreate `+server.ts` files for REST-style endpoints:\n\n```typescript\n\u002F\u002F src\u002Froutes\u002Fapi\u002Fposts\u002F+server.ts\nimport { json } from '@sveltejs\u002Fkit';\nimport type { RequestHandler } from '.\u002F$types';\n\nexport const GET: RequestHandler = async ({ url }) => {\n  const limit = Number(url.searchParams.get('limit') ?? 10);\n  const posts = await db.post.findMany({ take: limit });\n  return json(posts);\n};\n\nexport const POST: RequestHandler = async ({ request }) => {\n  const body = await request.json();\n  const post = await db.post.create({ data: body });\n  return json(post, { status: 201 });\n};\n```\n\n### Step 5: Form Actions\n\nForm actions are the SvelteKit-native way to handle mutations — no client-side fetch required:\n\n```typescript\n\u002F\u002F src\u002Froutes\u002Fcontact\u002F+page.server.ts\nimport { fail, redirect } from '@sveltejs\u002Fkit';\nimport type { Actions } from '.\u002F$types';\n\nexport const actions: Actions = {\n  default: async ({ request }) => {\n    const data = await request.formData();\n    const email = data.get('email');\n\n    if (!email) {\n      return fail(400, { email, missing: true });\n    }\n\n    await sendEmail(String(email));\n    redirect(303, '\u002Fthank-you');\n  }\n};\n```\n\n```svelte\n\u003C!-- src\u002Froutes\u002Fcontact\u002F+page.svelte -->\n\u003Cscript lang=\"ts\">\n  import { enhance } from '$app\u002Fforms';\n  import type { ActionData } from '.\u002F$types';\n  export let form: ActionData;\n\u003C\u002Fscript>\n\n\u003Cform method=\"POST\" use:enhance>\n  \u003Cinput name=\"email\" type=\"email\" \u002F>\n  {#if form?.missing}\u003Cp class=\"error\">Email is required\u003C\u002Fp>{\u002Fif}\n  \u003Cbutton type=\"submit\">Subscribe\u003C\u002Fbutton>\n\u003C\u002Fform>\n```\n\n### Step 6: Layouts and Nested Routes\n\n```svelte\n\u003C!-- src\u002Froutes\u002F+layout.svelte -->\n\u003Cscript lang=\"ts\">\n  import type { LayoutData } from '.\u002F$types';\n  export let data: LayoutData;\n\u003C\u002Fscript>\n\n\u003Cnav>\n  \u003Ca href=\"\u002F\">Home\u003C\u002Fa>\n  \u003Ca href=\"\u002Fblog\">Blog\u003C\u002Fa>\n  {#if data.user}\n    \u003Ca href=\"\u002Fdashboard\">Dashboard\u003C\u002Fa>\n  {\u002Fif}\n\u003C\u002Fnav>\n\n\u003Cslot \u002F>  \u003C!-- child page renders here -->\n```\n\n```typescript\n\u002F\u002F src\u002Froutes\u002F+layout.server.ts\nimport type { LayoutServerLoad } from '.\u002F$types';\n\nexport const load: LayoutServerLoad = async ({ locals }) => {\n  return { user: locals.user ?? null };\n};\n```\n\n### Step 7: Rendering Modes\n\nControl per-route rendering with page options:\n\n```typescript\n\u002F\u002F src\u002Froutes\u002Fdocs\u002F+page.ts\nexport const prerender = true;   \u002F\u002F Static — generated at build time\nexport const ssr = true;         \u002F\u002F Default — rendered on server per request\nexport const csr = false;        \u002F\u002F Disable client-side hydration entirely\n```\n\n## Examples\n\n### Example 1: Protected Dashboard Route\n\n```typescript\n\u002F\u002F src\u002Froutes\u002Fdashboard\u002F+layout.server.ts\nimport { redirect } from '@sveltejs\u002Fkit';\nimport type { LayoutServerLoad } from '.\u002F$types';\n\nexport const load: LayoutServerLoad = async ({ locals }) => {\n  if (!locals.user) {\n    redirect(303, '\u002Flogin');\n  }\n  return { user: locals.user };\n};\n```\n\n### Example 2: Hooks — Session Middleware\n\n```typescript\n\u002F\u002F src\u002Fhooks.server.ts\nimport type { Handle } from '@sveltejs\u002Fkit';\nimport { verifyToken } from '$lib\u002Fserver\u002Fauth';\n\nexport const handle: Handle = async ({ event, resolve }) => {\n  const token = event.cookies.get('session');\n  if (token) {\n    event.locals.user = await verifyToken(token);\n  }\n  return resolve(event);\n};\n```\n\n### Example 3: Preloading and Invalidation\n\n```svelte\n\u003Cscript lang=\"ts\">\n  import { invalidateAll } from '$app\u002Fnavigation';\n\n  async function refresh() {\n    await invalidateAll(); \u002F\u002F re-runs all load functions on the page\n  }\n\u003C\u002Fscript>\n\n\u003Cbutton on:click={refresh}>Refresh\u003C\u002Fbutton>\n```\n\n## Best Practices\n\n- ✅ Use `+page.server.ts` for database\u002Fauth logic — it never ships to the client\n- ✅ Use `$lib\u002Fserver\u002F` for shared server-only modules (DB client, auth helpers)\n- ✅ Use form actions for mutations instead of client-side `fetch` — works without JS\n- ✅ Type all `load` return values with generated `$types` (`PageData`, `LayoutData`)\n- ✅ Use `event.locals` in hooks to pass server-side context to load functions\n- ❌ Don't import server-only code in `+page.svelte` or `+layout.svelte` directly\n- ❌ Don't store sensitive state in stores — use `locals` on the server\n- ❌ Don't skip `use:enhance` on forms — without it, forms lose progressive enhancement\n\n## Security & Safety Notes\n\n- All code in `+page.server.ts`, `+server.ts`, and `$lib\u002Fserver\u002F` runs exclusively on the server — safe for DB queries, secrets, and session validation.\n- Always validate and sanitize form data before database writes.\n- Use `error(403)` or `redirect(303)` from `@sveltejs\u002Fkit` rather than returning raw error objects.\n- Set `httpOnly: true` and `secure: true` on all auth cookies.\n- CSRF protection is built-in for form actions — do not disable `checkOrigin` in production.\n\n## Common Pitfalls\n\n- **Problem:** `Cannot use import statement in a module` in `+page.server.ts`\n  **Solution:** The file must be `.ts` or `.js`, not `.svelte`. Server files and Svelte components are separate.\n\n- **Problem:** Store value is `undefined` on first SSR render\n  **Solution:** Populate the store from the `load` function return value (`data` prop), not from client-side `onMount`.\n\n- **Problem:** Form action does not redirect after submit\n  **Solution:** Use `redirect(303, '\u002Fpath')` from `@sveltejs\u002Fkit`, not a plain `return`. 303 is required for POST redirects.\n\n- **Problem:** `locals.user` is undefined inside a `+page.server.ts` load function\n  **Solution:** Set `event.locals.user` in `src\u002Fhooks.server.ts` before the `resolve()` call.\n\n## Related Skills\n\n- `@nextjs-app-router-patterns` — When you prefer React over Svelte for SSR\u002FSSG\n- `@trpc-fullstack` — Add end-to-end type safety to SvelteKit API routes\n- `@auth-implementation-patterns` — Authentication patterns usable with SvelteKit hooks\n- `@tailwind-patterns` — Styling SvelteKit apps with Tailwind CSS\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","# SvelteKit Full-Stack Development\n\n## Overview\n\nSvelteKit is the official full-stack framework built on top of Svelte. It provides file-based routing, server-side rendering (SSR), static site generation (SSG), API routes, and progressive form actions — all with Svelte's compile-time reactivity model that ships zero runtime overhead to the browser. Use this skill when building fast, modern web apps where both DX and performance matter.\n\n## When to Use This Skill\n\n- Use when building a new full-stack web application with Svelte\n- Use when you need SSR or SSG with fine-grained control per route\n- Use when migrating a SPA to a framework with server capabilities\n- Use when working on a project that needs file-based routing and collocated API endpoints\n- Use when the user asks about `+page.svelte`, `+layout.svelte`, `load` functions, or form actions\n\n## How It Works\n\n### Step 1: Project Setup\n\n```bash\nnpm create svelte@latest my-app\ncd my-app\nnpm install\nnpm run dev\n```\n\nChoose **Skeleton project** + **TypeScript** + **ESLint\u002FPrettier** when prompted.\n\nDirectory structure after scaffolding:\n\n```\nsrc\u002F\n  routes\u002F\n    +page.svelte        ← Root page component\n    +layout.svelte      ← Root layout (wraps all pages)\n    +error.svelte       ← Error boundary\n  lib\u002F\n    server\u002F             ← Server-only code (never bundled to client)\n    components\u002F         ← Shared components\n  app.html              ← HTML shell\nstatic\u002F                 ← Static assets\n```\n\n### Step 2: File-Based Routing\n\nEvery `+page.svelte` file in `src\u002Froutes\u002F` maps directly to a URL:\n\n```\nsrc\u002Froutes\u002F+page.svelte          → \u002F\nsrc\u002Froutes\u002Fabout\u002F+page.svelte    → \u002Fabout\nsrc\u002Froutes\u002Fblog\u002F[slug]\u002F+page.svelte  → \u002Fblog\u002F:slug\nsrc\u002Froutes\u002Fshop\u002F[...path]\u002F+page.svelte → \u002Fshop\u002F* (catch-all)\n```\n\n**Route groups** (no URL segment): wrap in `(group)\u002F` folder.\n**Private routes** (not accessible as URLs): prefix with `_` or `(group)`.\n\n### Step 3: Loading Data with `load` Functions\n\nUse a `+page.ts` (universal) or `+page.server.ts` (server-only) file alongside the page:\n\n```typescript\n\u002F\u002F src\u002Froutes\u002Fblog\u002F[slug]\u002F+page.server.ts\nimport { error } from '@sveltejs\u002Fkit';\nimport type { PageServerLoad } from '.\u002F$types';\n\nexport const load: PageServerLoad = async ({ params, fetch }) => {\n  const post = await fetch(`\u002Fapi\u002Fposts\u002F${params.slug}`).then(r => r.json());\n\n  if (!post) {\n    error(404, 'Post not found');\n  }\n\n  return { post };\n};\n```\n\n```svelte\n\u003C!-- src\u002Froutes\u002Fblog\u002F[slug]\u002F+page.svelte -->\n\u003Cscript lang=\"ts\">\n  import type { PageData } from '.\u002F$types';\n  export let data: PageData;\n\u003C\u002Fscript>\n\n\u003Ch1>{data.post.title}\u003C\u002Fh1>\n\u003Carticle>{@html data.post.content}\u003C\u002Farticle>\n```\n\n### Step 4: API Routes (Server Endpoints)\n\nCreate `+server.ts` files for REST-style endpoints:\n\n```typescript\n\u002F\u002F src\u002Froutes\u002Fapi\u002Fposts\u002F+server.ts\nimport { json } from '@sveltejs\u002Fkit';\nimport type { RequestHandler } from '.\u002F$types';\n\nexport const GET: RequestHandler = async ({ url }) => {\n  const limit = Number(url.searchParams.get('limit') ?? 10);\n  const posts = await db.post.findMany({ take: limit });\n  return json(posts);\n};\n\nexport const POST: RequestHandler = async ({ request }) => {\n  const body = await request.json();\n  const post = await db.post.create({ data: body });\n  return json(post, { status: 201 });\n};\n```\n\n### Step 5: Form Actions\n\nForm actions are the SvelteKit-native way to handle mutations — no client-side fetch required:\n\n```typescript\n\u002F\u002F src\u002Froutes\u002Fcontact\u002F+page.server.ts\nimport { fail, redirect } from '@sveltejs\u002Fkit';\nimport type { Actions } from '.\u002F$types';\n\nexport const actions: Actions = {\n  default: async ({ request }) => {\n    const data = await request.formData();\n    const email = data.get('email');\n\n    if (!email) {\n      return fail(400, { email, missing: true });\n    }\n\n    await sendEmail(String(email));\n    redirect(303, '\u002Fthank-you');\n  }\n};\n```\n\n```svelte\n\u003C!-- src\u002Froutes\u002Fcontact\u002F+page.svelte -->\n\u003Cscript lang=\"ts\">\n  import { enhance } from '$app\u002Fforms';\n  import type { ActionData } from '.\u002F$types';\n  export let form: ActionData;\n\u003C\u002Fscript>\n\n\u003Cform method=\"POST\" use:enhance>\n  \u003Cinput name=\"email\" type=\"email\" \u002F>\n  {#if form?.missing}\u003Cp class=\"error\">Email is required\u003C\u002Fp>{\u002Fif}\n  \u003Cbutton type=\"submit\">Subscribe\u003C\u002Fbutton>\n\u003C\u002Fform>\n```\n\n### Step 6: Layouts and Nested Routes\n\n```svelte\n\u003C!-- src\u002Froutes\u002F+layout.svelte -->\n\u003Cscript lang=\"ts\">\n  import type { LayoutData } from '.\u002F$types';\n  export let data: LayoutData;\n\u003C\u002Fscript>\n\n\u003Cnav>\n  \u003Ca href=\"\u002F\">Home\u003C\u002Fa>\n  \u003Ca href=\"\u002Fblog\">Blog\u003C\u002Fa>\n  {#if data.user}\n    \u003Ca href=\"\u002Fdashboard\">Dashboard\u003C\u002Fa>\n  {\u002Fif}\n\u003C\u002Fnav>\n\n\u003Cslot \u002F>  \u003C!-- child page renders here -->\n```\n\n```typescript\n\u002F\u002F src\u002Froutes\u002F+layout.server.ts\nimport type { LayoutServerLoad } from '.\u002F$types';\n\nexport const load: LayoutServerLoad = async ({ locals }) => {\n  return { user: locals.user ?? null };\n};\n```\n\n### Step 7: Rendering Modes\n\nControl per-route rendering with page options:\n\n```typescript\n\u002F\u002F src\u002Froutes\u002Fdocs\u002F+page.ts\nexport const prerender = true;   \u002F\u002F Static — generated at build time\nexport const ssr = true;         \u002F\u002F Default — rendered on server per request\nexport const csr = false;        \u002F\u002F Disable client-side hydration entirely\n```\n\n## Examples\n\n### Example 1: Protected Dashboard Route\n\n```typescript\n\u002F\u002F src\u002Froutes\u002Fdashboard\u002F+layout.server.ts\nimport { redirect } from '@sveltejs\u002Fkit';\nimport type { LayoutServerLoad } from '.\u002F$types';\n\nexport const load: LayoutServerLoad = async ({ locals }) => {\n  if (!locals.user) {\n    redirect(303, '\u002Flogin');\n  }\n  return { user: locals.user };\n};\n```\n\n### Example 2: Hooks — Session Middleware\n\n```typescript\n\u002F\u002F src\u002Fhooks.server.ts\nimport type { Handle } from '@sveltejs\u002Fkit';\nimport { verifyToken } from '$lib\u002Fserver\u002Fauth';\n\nexport const handle: Handle = async ({ event, resolve }) => {\n  const token = event.cookies.get('session');\n  if (token) {\n    event.locals.user = await verifyToken(token);\n  }\n  return resolve(event);\n};\n```\n\n### Example 3: Preloading and Invalidation\n\n```svelte\n\u003Cscript lang=\"ts\">\n  import { invalidateAll } from '$app\u002Fnavigation';\n\n  async function refresh() {\n    await invalidateAll(); \u002F\u002F re-runs all load functions on the page\n  }\n\u003C\u002Fscript>\n\n\u003Cbutton on:click={refresh}>Refresh\u003C\u002Fbutton>\n```\n\n## Best Practices\n\n- ✅ Use `+page.server.ts` for database\u002Fauth logic — it never ships to the client\n- ✅ Use `$lib\u002Fserver\u002F` for shared server-only modules (DB client, auth helpers)\n- ✅ Use form actions for mutations instead of client-side `fetch` — works without JS\n- ✅ Type all `load` return values with generated `$types` (`PageData`, `LayoutData`)\n- ✅ Use `event.locals` in hooks to pass server-side context to load functions\n- ❌ Don't import server-only code in `+page.svelte` or `+layout.svelte` directly\n- ❌ Don't store sensitive state in stores — use `locals` on the server\n- ❌ Don't skip `use:enhance` on forms — without it, forms lose progressive enhancement\n\n## Security & Safety Notes\n\n- All code in `+page.server.ts`, `+server.ts`, and `$lib\u002Fserver\u002F` runs exclusively on the server — safe for DB queries, secrets, and session validation.\n- Always validate and sanitize form data before database writes.\n- Use `error(403)` or `redirect(303)` from `@sveltejs\u002Fkit` rather than returning raw error objects.\n- Set `httpOnly: true` and `secure: true` on all auth cookies.\n- CSRF protection is built-in for form actions — do not disable `checkOrigin` in production.\n\n## Common Pitfalls\n\n- **Problem:** `Cannot use import statement in a module` in `+page.server.ts`\n  **Solution:** The file must be `.ts` or `.js`, not `.svelte`. Server files and Svelte components are separate.\n\n- **Problem:** Store value is `undefined` on first SSR render\n  **Solution:** Populate the store from the `load` function return value (`data` prop), not from client-side `onMount`.\n\n- **Problem:** Form action does not redirect after submit\n  **Solution:** Use `redirect(303, '\u002Fpath')` from `@sveltejs\u002Fkit`, not a plain `return`. 303 is required for POST redirects.\n\n- **Problem:** `locals.user` is undefined inside a `+page.server.ts` load function\n  **Solution:** Set `event.locals.user` in `src\u002Fhooks.server.ts` before the `resolve()` call.\n\n## Related Skills\n\n- `@nextjs-app-router-patterns` — When you prefer React over Svelte for SSR\u002FSSG\n- `@trpc-fullstack` — Add end-to-end type safety to SvelteKit API routes\n- `@auth-implementation-patterns` — Authentication patterns usable with SvelteKit hooks\n- `@tailwind-patterns` — Styling SvelteKit apps with Tailwind CSS\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":23,"tags":24,"tools":30,"author":34,"source":35,"category":36,"date_added":37,"description":7},"safe",[25,5,26,27,28,29],"svelte","fullstack","ssr","ssg","typescript",[31,32,33],"claude","cursor","gemini","suhaibjanjua","community","frontend","2026-03-18","main","d046d088ce5a79a083f0abc0fe1b7ded73bc5b1f","claude-config\u002Fskills\u002Fantigravity\u002Fsveltekit","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent","https:\u002F\u002Fgithub.com\u002FSansar35","2026-05-10 16:04:53",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add Sansar35\u002Fclaude-agent --skill sveltekit",{"tool":50,"command":51},"bunx","bunx skills add Sansar35\u002Fclaude-agent --skill sveltekit",{"tool":53,"command":54},"pnpm","pnpm dlx skills add Sansar35\u002Fclaude-agent --skill sveltekit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fantigravity\u002Fsveltekit\u002FSKILL.md",true,[],[59,66,73,80,87,95],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M72DVAN1JYEA302MT0C5MGD6","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M72DV8J5NBRRM4RPDFRV95N7","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M72DV5EMHW0BHP9BZ167MDCB","zinc-database","Access ZINC (230M+ purchasable compounds). Search by ZINC ID\u002FSMILES, similarity searches, 3D-ready structures for docking, analog discovery, for virtual screening and drug discovery.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzinc-database\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M72DV216QY0E693ZPEVQ0DBS","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":18},"01M72DTXQREMCRKA8NHCVKHN4W","zapier-workflows","Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to \"run\" any process. Also handles Perplexity-based research and Google Sheets data tracking.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-workflows\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-workflows\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":18},"01M72DTT17TBSJ0Y8J2XZ4C9TZ","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-make-patterns\u002FSKILL.md",[],[]]