Skip to content
TrustedSkillsbeta
Back to all skills

Svelte5 Best Practices

Listed
ejirocodes·vlatest·frontend·MIT

Ensures Svelte 5 code adheres to ejirocodes' recommended best practices for performance, maintainability, and accessibility.

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 ejirocodes/agent-skills --skill svelte5-best-practices -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

ejirocodes

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 failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No undeclared network calls: failed

    Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: api.stripe.com.

    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.

    Hosts contacted

    api.stripe.comundeclared

    What it found

    • svelte/skills/svelte5-best-practices/references/sveltekit.md:30contacts api.stripe.com
      const response = await fetch('https://api.stripe.com/charges', {
    • svelte/skills/svelte5-best-practices/references/sveltekit.md:43contacts api.stripe.com
      const response = await fetch('https://api.stripe.com/charges', {

  • 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 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 ejirocodes/agent-skills at 6e805e4cc8.

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

Commit
6e805e4cc8
Manifest
svelte/skills/svelte5-best-practices/SKILL.md
Scanned
8 files, 2,301 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 provides best practices for developing applications using Svelte 5, including efficient component organization, state management strategies, and performance optimization techniques. It helps developers write clean, maintainable code that leverages the latest features of Svelte.

When to use it

  • When building a new Svelte application and looking for guidance on structuring your project.
  • When optimizing an existing Svelte app for better performance or scalability.
  • When preparing documentation or training materials for a team working with Svelte 5.
  • When refactoring legacy code to align with modern Svelte practices.

Key capabilities

  • Guidance on component structure and reusability
  • Recommendations for state management patterns (e.g., stores, context)
  • Performance optimization techniques like lazy loading and SSR support
  • Code organization strategies for large-scale applications

Example prompts

  • "How should I organize my components in a Svelte 5 project?"
  • "What are the best practices for managing global state in Svelte 5?"
  • "Can you suggest ways to optimize the performance of my Svelte app?"

Tips & gotchas

  • Ensure your development environment supports Svelte 5 features before applying these practices.
  • Some recommendations may require additional tooling or configuration, such as Vite or Webpack.