Svelte Deployment
CheckedHelps with Svelte, deployment as part of building frontend UIs and user experiences workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add spences10/svelte-skills-kit --skill svelte-deployment -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
spences10
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.
Automated safety checks
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 spences10/svelte-skills-kit at 2a9d88379b.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 2a9d88379b
- Scanned
- 4 files, 314 lines
About this skill
What it does
This skill assists with deploying Svelte applications, particularly within frontend UI and user experience workflows. It provides guidance on setting up deployment processes using tools like svelte-kit, Vite, and various adapters for different platforms (static sites, Node servers, Cloudflare). The skill also offers references for publishing Svelte packages, implementing Progressive Web App (PWA) functionality with Workbox, and troubleshooting common issues when deploying to Cloudflare.
When to use it
- When setting up a new Svelte project and needing guidance on deployment options.
- If you're experiencing difficulties deploying a Svelte application to a specific platform like Cloudflare.
- For developers looking to publish their own Svelte packages and need assistance with the publishing process.
- To implement offline functionality in your Svelte app using Workbox.
Key capabilities
- Provides instructions for setting up prepare scripts (using
svelte-kit sync). - Offers guidance on updating Vite and
@sveltejs/vite-plugin-sveltepackages together. - Lists available adapters for deployment to static sites, Node servers, and Cloudflare.
- Includes reference materials for library authoring, PWA setup, and Cloudflare specific issues.
- Provides notes regarding potential Cloudflare streaming issues and best practices for Svelte package publishing.
Example prompts
- "How do I deploy my SvelteKit app to a static site?"
- "What are the steps to publish a Svelte library?"
- "I'm having trouble with streaming on Cloudflare, what should I check?"
- "How can I add offline capabilities to my Svelte application?"
Tips & gotchas
- When deploying to Cloudflare, be aware that it may strip
Transfer-Encoding: chunked, which can break streaming. - For library authors, ensure you include both
sveltein the keywords and as a peerDependency in your package.json. - Consider using
kit.output.bundleStrategy: 'single'for creating a single-file bundle.