Svelte Core Bestpractices

Name: Svelte Core Bestpractices
Author: sveltejs

Official

sveltejs·vlatest·frontend·MIT

Ensures Svelte components adhere to best practices using svelte/core, optimizing performance and maintainability.

Repository

Install on your platform

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

Run this in your project

terminal

$ npx skills add sveltejs/ai-tools --skill svelte-core-bestpractices -a claude-code

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

sveltejs

Matched to the vendor's own GitHub organisation.

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 30 Sept 2026

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 sveltejs/ai-tools at a5a92c680e.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit: a5a92c680e
Manifest: tools/skills/svelte-core-bestpractices/SKILL.md
Scanned: 30 files, 3,411 lines
Copies in repo: 3 — all of them scanned

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 Core. It offers guidance on structuring components, managing state effectively, and optimizing performance within a Svelte project. The skill aims to improve code quality and maintainability by adhering to established conventions.

When to use it

New Svelte Projects: To establish a solid foundation from the beginning.
Refactoring Existing Code: To modernize legacy Svelte applications and improve their structure.
Code Reviews: To ensure team members are following consistent coding standards within a Svelte project.
Learning Svelte: As a resource for developers new to the Svelte framework.

Key capabilities

Component structuring guidance
State management best practices
Performance optimization techniques
Adherence to established Svelte conventions

Example prompts

"How should I structure components in my Svelte application?"
"What's the recommended way to manage state in a complex Svelte component?"
"Suggest ways to optimize the performance of this Svelte code snippet."

Tips & gotchas

This skill assumes basic familiarity with Svelte Core concepts. While it offers best practices, always consider project-specific requirements and context when applying these guidelines.