Skip to content
TrustedSkillsbeta
Back to all skills

Svelte Kit

Checked
tomlord1122·vlatest·frontend

Generates, debugs, and optimizes SvelteKit applications, including routes, stores, and component logic for efficient web development.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add tomlord1122/tomtom-skill --skill svelte-kit -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

tomlord1122

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned tomlord1122/tomtom-skill at bfa41ed48c.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
bfa41ed48c
Manifest
skills/svelte-kit/SKILL.md
Scanned
1 file, 463 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill acts as an expert assistant for Svelte and SvelteKit development. It helps users generate, debug, and optimize SvelteKit applications by providing guidance on routing, server-side rendering (SSR) / static site generation (SSG) strategies, component design patterns, and reactivity management using either the newer "runes" syntax (Svelte 5) or older store-based approach (Svelte 4). The skill follows a structured thinking process to identify problems and suggest appropriate solutions.

When to use it

  • You're encountering issues with SvelteKit routing, such as navigation problems or incorrect parameter handling.
  • You need help understanding the implications of SSR vs CSR for your application’s rendering performance and data availability.
  • You are experiencing reactivity problems where state updates aren't reflected correctly in your components.
  • You're unsure how to structure your data loading logic using +page.ts versus +page.server.ts.
  • You need assistance with component design patterns, including prop management and slot usage.

Key capabilities

  • Problem Classification: Identifies the type of Svelte/SvelteKit problem (reactivity, rendering, routing, data loading, or component design).
  • Version Awareness: Checks for Svelte version (4 vs 5) and SvelteKit version to ensure compatibility.
  • SSR/CSR Analysis: Evaluates code execution context (server-only, server + client, client-only) and potential hydration mismatches.
  • Data Flow Design Guidance: Provides advice on where data should come from and when it should be fetched.
  • Syntax Assistance: Offers guidance on using Svelte 5 "runes" syntax versus the older store approach.

Example prompts

  • "I'm having trouble with navigation in my SvelteKit app, how do I handle route parameters?"
  • "My component isn’t updating when a variable changes. How can I debug this reactivity issue using runes?"
  • "What's the difference between +page.ts and +page.server.ts, and when should I use each one?"

Tips & gotchas

  • The skill defaults to Svelte 5 "runes" syntax unless explicitly told otherwise.
  • Be mindful of SSR/CSR implications; avoid using browser-specific APIs (like window or document) in server-only code without proper checks. Use the provided $app/environment pattern for safe client-side execution.
  • Always provide context about your Svelte and SvelteKit versions for more accurate assistance.