Svelte Core Bestpractices

Name: Svelte Core Bestpractices
Author: sveltejs

Official

sveltejs·vlatest·frontend·MIT

Enforces Svelte best practices—component structure, reactivity, stores—for cleaner, maintainable, and performant codebases.

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 27 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/mcp 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 access to best practices and guidelines for developing applications using Svelte Core. It helps developers write more efficient, maintainable, and performant Svelte code by adhering to established conventions and patterns. The skill aims to improve the overall quality and consistency of Svelte projects.

When to use it

New Svelte Projects: To establish a solid foundation based on proven best practices from the outset.
Code Reviews: To ensure existing code aligns with recommended Svelte coding standards.
Refactoring Legacy Code: To modernize and improve older Svelte applications by applying current best practices.
Team Onboarding: To quickly bring new developers up to speed on the team's preferred Svelte development style.

Key capabilities

Svelte Core Best Practices
Coding Guidelines
Performance Optimization Techniques
Maintainability Standards

Example prompts

"What are the recommended ways to handle state in a Svelte component?"
"Show me an example of how to optimize a Svelte loop for performance."
"How should I structure my project files when using Svelte Core?"

Tips & gotchas

This skill assumes a basic understanding of Svelte Core concepts. Referencing specific versions or features within the Svelte documentation may be necessary for more advanced scenarios.