Skip to main content
skillsFirst-partyReview first Safety Privacy

Svelte SvelteKit Full-Stack Development Skill

Build full-stack web apps with Svelte and SvelteKit. Minimal runtime overhead, reactive components, and server-side rendering. The most admired frontend framework of 2025. Svelte compiles components to vanilla JavaScript at build time, resulting in zero runtime overhead and exceptional performance.

HarnessClaude CodeCodexWindsurfGeminiCursorCLI
Level:advancedType:generalVerified:draft
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://svelte.dev/docs/kit/introduction, https://github.com/JSONbored/awesome-claude/blob/main/content/skills/svelte-sveltekit-fullstack.mdx
Package URL
/downloads/skills/svelte-sveltekit-fullstack.zip
Package SHA256
446158b7bf996f8a2538d024e254e925b83c93d8c1ae180f1a7576ed3a654a57
Safety notes
Scaffolds and runs a SvelteKit app (npm create svelte, npm install, dev/build servers that listen on a port and install dependencies); review generated server endpoints and dependencies before exposing them.
Privacy notes
Full-stack SvelteKit apps handle server-side env vars, sessions, and user data; keep secrets in $env/static/private (never $env/static/public), and review what server routes read, store, or log.
Platform compatibility
claude-code (native-skill), codex (native-skill), windsurf (native-skill), gemini (native-skill), cursor (adapter), cli (manual-context)
Author
JSONbored
Claim status
unclaimed
Last verified
2025-10-23

Decision playbook

Ready to evaluate for your workflow

Signals are comparatively strong, but you should still validate source, privacy posture, and package provenance for your environment.

Compare context
Selected

0

Current score

96

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as first-party.

    Done
  • Metadata reviewed

    Registry metadata indicates a reviewed listing.

    Done

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Complete

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    Package marked verified.

    Done
  • Checksum metadata

    SHA-256 hash is present.

    Done

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

Package install

Copy-ready — paste the snippet to get started.

Install command

Provided

Config snippet

Not provided

Copy snippet

Provided

Prerequisites

6 to clear

Platforms

6 listed

Difficulty

100/100

Adoption plan

Balanced adoption plan

Current risk score 0/100. Use staged verification before broader rollout.

Risk 0

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    Listing has review metadata.

    Done
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    Package verification/checksum metadata is available.

    Done

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Required evidence gates are covered (6/6 signals complete).

Risk 0

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Present

Package integrity metadata is present.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

6/6 steps complete with no blocking gaps for this preset.

Risk 0

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is available.

Done

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Prerequisite readiness

Prerequisite readiness

6 prerequisites to line up before setup.

0/6 ready
Install & runtime3General3

Safety & privacy surface

Safety & privacy surface

1 safety and 1 privacy notes across 2 risk areas. Review closely: credentials & tokens, network access.

2 areas
  • SafetyNetwork accessScaffolds and runs a SvelteKit app (npm create svelte, npm install, dev/build servers that listen on a port and install dependencies); review generated server endpoints and dependencies before exposing them.
  • PrivacyCredentials & tokensFull-stack SvelteKit apps handle server-side env vars, sessions, and user data; keep secrets in $env/static/private (never $env/static/public), and review what server routes read, store, or log.

Safety notes

  • Scaffolds and runs a SvelteKit app (npm create svelte, npm install, dev/build servers that listen on a port and install dependencies); review generated server endpoints and dependencies before exposing them.

Privacy notes

  • Full-stack SvelteKit apps handle server-side env vars, sessions, and user data; keep secrets in $env/static/private (never $env/static/public), and review what server routes read, store, or log.

Prerequisites

  • Node.js 18+ (20+ recommended)
  • @sveltejs/kit ^2.0.0
  • svelte ^4.0.0
  • vite ^5.0.0
  • Node.js 18+ runtime environment for running SvelteKit development server and build processes
  • Package manager (npm, pnpm, yarn, or bun) for installing SvelteKit dependencies and managing project packages

Schema details

Install type
package
Reading time
6 min
Difficulty score
100
Troubleshooting
Yes
Breaking changes
No
Package metadata
Package verified
Yes
SHA-256
446158b7bf996f8a2538d024e254e925b83c93d8c1ae180f1a7576ed3a654a57
Skill and platform metadata
Skill type
general
Skill level
advanced
Verification
draft
Verified at
2025-10-23
Retrieval sources
https://svelte.dev/docs/kit/introductionhttps://svelte.dev/docs/svelte/overview
Tested platforms
ClaudeCodexOpenClawCursorWindsurfGemini
PlatformSupportInstall path
claude-codeNative.claude/skills/<skill-name>/SKILL.md
codexNative.agents/skills/<skill-name>/SKILL.md
windsurfNative.windsurf/skills/<skill-name>/SKILL.md
geminiNative.gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md
cursorAdapter.cursor/rules/<skill-name>.mdc
cliManualAGENTS.md or tool-specific context file
Full copyable content
<script>
  let count = 0;
  
  // Reactive statement - automatically re-runs when count changes
  $: doubled = count * 2;
  $: console.log(`Count is now ${count}`);
  
  function increment() {
    count += 1;
  }
</script>

<div>
  <button on:click={increment}>Count: {count}</button>
  <p>Doubled: {doubled}</p>
</div>

About this resource

What This Skill Enables

Claude can build reactive web applications using Svelte's compile-time approach and SvelteKit's full-stack framework. Svelte compiles components to vanilla JavaScript at build time, resulting in minimal runtime overhead and exceptional performance. SvelteKit adds file-based routing, server-side rendering, API routes, and adapters for any platform. From simple components to production apps with authentication and databases, Claude handles the Svelte ecosystem end-to-end.

Compatibility

Native

  • Claude Code / Claude: native skill usage via SKILL.md.
  • Codex/OpenAI workflows: compatible with Agent Skills-style SKILL.md content as reusable workflow instructions.

Manual Adaptation

  • Gemini CLI: native skill usage via .gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md where supported.
  • Cursor: use the generated .cursor/rules/*.mdc adapter for project rules.
  • OpenClaw and similar agents: use the same skill content as a reusable prompt/workflow file when native skill import is unavailable.

Prerequisites

Required:

  • Claude Pro subscription or Claude Code CLI
  • Node.js 18+ (20+ recommended)
  • npm or pnpm package manager
  • Basic JavaScript knowledge

What Claude handles automatically:

  • Creating reactive Svelte components with stores
  • Building SvelteKit routes with +page.svelte files
  • Implementing server-side logic in +page.server.ts
  • Setting up form actions with progressive enhancement
  • Adding authentication with hooks and load functions
  • Configuring database connections and ORMs
  • Implementing real-time features with Svelte stores
  • Deploying to Vercel, Netlify, or Node servers

How to Use This Skill

Reactive Component Development

Prompt: "Create Svelte component for user profile with: editable bio, avatar upload with preview, reactive form validation, and optimistic UI updates. Use Svelte stores for state."

Claude will:

  1. Create component with $: reactive statements
  2. Set up writable stores for form state
  3. Add two-way binding with bind:value
  4. Implement file upload with FileReader
  5. Add reactive validation with $:
  6. Show optimistic updates
  7. Handle submission with fetch

SvelteKit Full-Stack App

Prompt: "Build SvelteKit blog with: file-based routing, Markdown posts with frontmatter, server-side API routes for CRUD, authentication with JWT, and SQLite database with Prisma."

Claude will:

  1. Set up SvelteKit project structure
  2. Create +page.svelte routes
  3. Add +page.server.ts load functions
  4. Implement API routes in +server.ts
  5. Configure Prisma with SQLite
  6. Add authentication hooks
  7. Parse Markdown with gray-matter

Form Handling with Actions

Prompt: "Create SvelteKit form for product creation with: server-side validation, progressive enhancement (works without JS), file uploads, and optimistic UI. Show errors next to fields."

Claude will:

  1. Create form in +page.svelte
  2. Add form action in +page.server.ts
  3. Implement server-side validation
  4. Use enhance for progressive enhancement
  5. Add file upload handling
  6. Display field-specific errors
  7. Show success messages

Real-Time Dashboard

Prompt: "Build real-time analytics dashboard with Svelte: WebSocket connection, reactive charts with Chart.js, derived stores for calculated metrics, and auto-refreshing data every 30s."

Claude will:

  1. Set up WebSocket in SvelteKit
  2. Create writable stores for data
  3. Add derived stores for calculations
  4. Integrate Chart.js reactively
  5. Implement auto-refresh with setInterval
  6. Add connection status indicator
  7. Handle reconnection logic

Tips for Best Results

  1. Use Reactive Statements: The $: syntax automatically re-runs when dependencies change. Use for derived values, side effects, and reactive logic.

  2. Embrace Two-Way Binding: bind:value, bind:checked, bind:group simplify form handling. No need for onChange handlers.

  3. Stores for Global State: Use writable, readable, or derived stores instead of React Context. Access with $ prefix in components.

  4. Server Load Functions: Fetch data in +page.server.ts load functions for SSR. Access with data prop in components.

  5. Form Actions Over APIs: SvelteKit form actions provide progressive enhancement. No JavaScript required for basic functionality.

  6. Compile-Time Optimization: Svelte compiles to optimal JavaScript. Avoid runtime overhead of virtual DOM. Components are just functions.

Common Workflows

E-Commerce Store

"Build SvelteKit e-commerce with:
1. Product catalog: +page.svelte with load function, search/filter
2. Product detail: dynamic [slug]/+page.svelte route
3. Cart: writable store with localStorage persistence
4. Checkout: form actions with Stripe integration
5. Auth: hooks for JWT validation, protected routes
6. Admin: +layout.server.ts for role-based access
7. Database: Prisma with PostgreSQL
8. Images: static adapter with CDN"

SaaS Dashboard

"Create multi-tenant SvelteKit SaaS:
1. Auth: +hooks.server.ts for session management
2. Multi-tenant: load function filters by tenant ID
3. Dashboard: reactive charts with derived stores
4. Settings: form actions for account updates
5. API: +server.ts routes for external integrations
6. Billing: Stripe webhooks in API routes
7. Real-time: Server-Sent Events for notifications
8. Deploy: Node adapter with PM2"

Static Site Generator

"Build Svelte static site generator:
1. Content: Markdown files with frontmatter
2. Processing: +page.server.ts loads and parses MD
3. Templates: layout components for post types
4. Navigation: derived store from post metadata
5. Search: client-side with Fuse.js
6. RSS: +server.ts generates feed.xml
7. Sitemap: prerender all routes
8. Deploy: Static adapter to Netlify"

Real-Time Collaboration

"Build collaborative doc editor with Svelte:
1. Editor: rich text with ProseMirror
2. Sync: WebSocket for real-time updates
3. Presence: writable store showing active users
4. Conflict resolution: operational transforms
5. Persistence: auto-save to database
6. Auth: session-based with refresh tokens
7. Rooms: dynamic [roomId] routes
8. Cursor positions: reactive SVG overlays"

Troubleshooting

Issue: "Reactive statements not updating when I expect" Solution: Ensure reactive statement depends on reactive value ($: result = calculate(value), not const). Use = for assignment in reactive block. Check that dependencies are in scope. Array/object mutations need reassignment: items = [...items, newItem].

Issue: "Load function data not available in component" Solution: Export data prop in +page.svelte: export let data;. Check +page.server.ts returns object from load(). Verify route has +page.server.ts file. Use $page.data for nested layouts.

Issue: "Form action not being called" Solution: Add name to form action: <form method="POST" action="?/create">. Export actions in +page.server.ts. Use enhance from $app/forms for progressive enhancement. Check method is POST.

Issue: "Stores not persisting across page navigation" Solution: Use writable store in separate .ts file, not component. Import same store instance everywhere. For persistence, sync to localStorage with custom store. Check SvelteKit isn't destroying store on navigation.

Issue: "Deployment build failing with adapter errors" Solution: Install correct adapter (@sveltejs/adapter-node, -vercel, -static). Check svelte.config.js has adapter configured. Verify build command in package.json. For static, ensure all routes are prerenderable.

Learn More

Features

  • Compile-time optimization with zero runtime overhead - Svelte compiles to vanilla JavaScript
  • Reactive programming with $: syntax for auto-updates and $state/$derived runes in Svelte 5
  • SvelteKit file-based routing with SSR, SSG, and hybrid rendering modes
  • Form actions with progressive enhancement (works without JavaScript)
  • Server load functions (+page.server.ts) for data fetching and authentication
  • Svelte stores (writable, readable, derived) for global state management
  • TypeScript support with automatic type generation from routes
  • Adapters for deployment to Vercel, Netlify, Node.js, Cloudflare Workers, and more

Use Cases

  • Building reactive dashboards with minimal JavaScript and real-time updates
  • Full-stack apps with authentication, databases (Prisma, Drizzle), and API routes
  • Static sites with Markdown content processing and SSG
  • E-commerce stores with cart management, checkout flows, and payment integration
  • SaaS dashboards with multi-tenant data isolation and role-based access
  • Real-time collaborative tools with WebSocket connections and presence tracking

Source citations

Add this badge to your README

Show that Svelte SvelteKit Full-Stack Development Skill is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/skills/svelte-sveltekit-fullstack.svg)](https://heyclau.de/entry/skills/svelte-sveltekit-fullstack)

How it compares

Svelte SvelteKit Full-Stack Development Skill side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

3 trust signals differ across this comparison (Package trust, Source provenance, Submitter).

Next steps differ across entries — use the actions in the table below to copy install commands and source links per resource.

Field

Build full-stack web apps with Svelte and SvelteKit. Minimal runtime overhead, reactive components, and server-side rendering. The most admired frontend framework of 2025. Svelte compiles components to vanilla JavaScript at build time, resulting in zero runtime overhead and exceptional performance.

Open dossier

Add Better Auth to a Next.js App Router project with API route handlers, database-backed sessions, client helpers, protected route checks, and production auth safety review.

Open dossier

Build JavaScript and TypeScript apps with Bun, an all-in-one toolchain that replaces Node.js, npm, a bundler, and a test runner with one fast binary that executes TypeScript directly.

Open dossier

Expert Claude Code computer use GUI QA capability pack that applies documented computer-use MCP enablement, per-app session approval, screenshot checkpoints, and macOS permission workflows for native app validation—not an official Anthropic QA product.

Open dossier
Next stepsDiffers
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustDiffersPackage verified2025-10-23Package not verifiedPackage verified2025-10-23Package not verified
Source provenanceDiffersSource-backedSource-backedNo submission linkSubmission linkedSource submission
SubmitterDiffersoktofeesh1kiannidev
Install riskReview firstReview firstLow riskReview first
Notes Safety Privacy Safety Privacy Safety Privacy Safety Privacy
Brand
Categoryskillsskillsskillsskills
Sourcefirst-partysource-backedfirst-partysource-backed
AuthorJSONboredoktofeesh1JSONboredkiannidev
Added2025-10-232026-06-042025-10-232026-06-16
Platforms
Claude CodeCodexWindsurfGeminiCursorCLI
Claude CodeCodexWindsurfGeminiCursorCLI
Claude CodeCodexWindsurfGeminiCursorCLI
Claude CodeCodexWindsurfGeminiCursorCLI
Source repo
Safety notesScaffolds and runs a SvelteKit app (npm create svelte, npm install, dev/build servers that listen on a port and install dependencies); review generated server endpoints and dependencies before exposing them.The download URL is Better Auth's external source archive, not a HeyClaude-packaged skill archive; review source provenance before using it in automated workflows. Do not commit Better Auth secrets, OAuth provider secrets, database URLs, email-provider credentials, API-key plugin secrets, or copied dashboard values. Run schema generation or migrations only against the intended database environment; auth tables, sessions, accounts, and verification records are production-critical. Treat route protection as server-side authorization work. UI hiding, optimistic middleware redirects, or cookie existence checks are not full access control. Review `proxy.ts` or `middleware.ts` behavior by Next.js version before relying on database-backed session checks inside request middleware. Keep OAuth callback URLs, base URLs, trusted origins, and cookie settings environment-specific to avoid broken login loops or cross-environment session confusion. Track Better Auth release notes and security advisories before introducing auth flows or enabling advanced plugins in production. Add rollback steps before replacing an existing auth provider because user, account, session, and verification tables can affect active logins.Installing Bun globally (`npm install -g bun`) adds a runtime to your system; install from the official npm package or bun.sh and keep it updated. Bun runs JavaScript/TypeScript with full system access like Node.js; review code before executing it, especially untrusted scripts.Computer use controls real desktop apps with per-app session approval—not sandboxed Bash. Review sentinel warnings before approving Terminal, Finder, or System Settings access. Press Esc or Ctrl+C to stop computer use and release the machine-wide lock immediately. Only one Claude Code session can hold the computer-use lock at a time.
Privacy notesFull-stack SvelteKit apps handle server-side env vars, sessions, and user data; keep secrets in $env/static/private (never $env/static/public), and review what server routes read, store, or log.Better Auth handles user identity, email addresses, password-auth state, OAuth profile data, sessions, cookies, accounts, verification tokens, and plugin-specific user data. Application logs, error trackers, request traces, AI prompts, and screenshots can retain user IDs, emails, callback URLs, cookies, session state, or OAuth provider details. Use synthetic users and test OAuth applications for examples, demos, issue reports, screenshots, and AI-assisted troubleshooting. If organization, API key, two-factor, passkey, or SSO plugins are enabled, treat membership, roles, credentials, and device metadata as sensitive authorization data. Review Better Auth, database, deployment-provider, analytics, email-provider, and AI-assistant retention policies before using real customer identity data.Bun apps you build can read local files, environment variables, and make network calls like any Node.js app; keep secrets in environment variables and review what your code sends externally.Screenshots are downscaled before model upload but may still capture sensitive UI content. Your terminal window is excluded from screenshots per official documentation. Redact customer or proprietary UI details before sharing screenshot evidence externally. Other visible apps are hidden while Claude works; still minimize sensitive windows before starting.
Prerequisites
  • Node.js 18+ (20+ recommended)
  • @sveltejs/kit ^2.0.0
  • svelte ^4.0.0
  • vite ^5.0.0
  • Next.js App Router project or migration branch with a known package manager.
  • Database choice and adapter plan, such as Drizzle, Prisma, MongoDB, or Better Auth's built-in Kysely-backed flow.
  • Local, preview, staging, and production secret-management path for Better Auth secrets, OAuth client IDs, and OAuth client secrets.
  • Route map that separates public pages, authenticated pages, API routes, server actions, admin routes, and organization-scoped areas.
  • Bun 1.0+ (install with `npm install -g bun`)
  • macOS, Linux, or WSL
  • Basic JavaScript/TypeScript knowledge
  • Node.js-compatible project structure with package.json for dependency management and module resolution
  • Interactive Claude Code session on macOS v2.1.85+ with Pro or Max plan per computer-use docs.
  • computer-use MCP server enabled through /mcp for the project.
  • macOS Accessibility and Screen Recording permissions granted when prompted.
  • Disposable QA target app or simulator without live customer data on screen.
Install
npm create svelte@latest my-app
pnpm add better-auth
npm install -g bun
Config
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.