How do I install the Cloudflare Sveltekit Workers D1 skill?

Run npx skillmds@latest add tomevault-io/cloudflare-sveltekit-workers-d1 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Cloudflare Sveltekit Workers D1 safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Cloudflare Sveltekit Workers D1?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Cloudflare Sveltekit Workers D1 free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Cloudflare Sveltekit Workers D1?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Cloudflare Sveltekit Workers D1 by tomevault-io

Name: Cloudflare Sveltekit Workers D1
Author: tomevault-io

Cloudflare Sveltekit Workers D1

Expert guidance for deploying TypeScript SvelteKit apps to Cloudflare Workers (edge) with D1. Use when configuring @sveltejs/adapter-cloudflare, Wrangler config, Workers Assets, D1 bindings/migrations, or when writing precise step-by-step deployment instructions for SvelteKit on Cloudflare Workers/Pages with D1. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Cloudflare SvelteKit Workers D1

Overview

Provide a clear, current workflow to connect a SvelteKit TypeScript app to Cloudflare Workers and D1, including adapter setup, Wrangler configuration, D1 bindings/migrations, local testing, and deployment instructions.

Workflow Decision Tree

Existing SvelteKit app -> Use the Manual Setup workflow in references/manual-workers-d1.md.
Brand new project -> Use the Cloudflare framework CLI flow in references/manual-workers-d1.md (C3 option).
User wants fastest/auto config -> Use references/wrangler-autoconfig.md (experimental) and still verify the generated config.

Core Workflow (Manual Setup)

Verify the latest Cloudflare + SvelteKit docs with web.run (adapter-cloudflare, Workers framework guide, D1 commands).
Add the Cloudflare adapter and update svelte.config.js.
Create or update wrangler.toml for Workers Assets and D1 bindings.
Create the D1 database and copy its binding block into wrangler.toml.
Add TypeScript platform typings and use platform.env.DB in server endpoints.
Create/apply migrations locally and remotely.
Build, test with Wrangler, then deploy.

Use the exact steps and snippets in references/manual-workers-d1.md.

D1 Integration Checklist

Ensure the binding name is a valid JS identifier and matches platform.env.<BINDING> in code.
Ensure wrangler.toml includes [[d1_databases]] with database_name + database_id.
Create and apply migrations with both --local and --remote as needed.
Update TypeScript declarations in src/app.d.ts.

Local Dev and Testing Guidance

Prefer SvelteKit dev server for general UI work.
For Cloudflare-specific behavior, build and run wrangler dev .svelte-kit/cloudflare.
Use adapter platformProxy options if local bindings need tweaks.

Writing Deployment Instructions

Be explicit about files, commands, and where to paste blocks.
Always include the wrangler.toml skeleton and D1 binding block.
Include verification steps (local dev and a deploy check).
If there is any uncertainty in versions or commands, re-check docs via web.run.

Resources

references/manual-workers-d1.md - canonical manual setup workflow + snippets
references/wrangler-autoconfig.md - experimental Wrangler auto-setup path

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: cloudflare-sveltekit-workers-d1description: Expert guidance for deploying TypeScript SvelteKit apps to Cloudflare Workers (edge) with D1. Use when configuring @sveltejs/adapter-cloudflare, Wrangler config, Workers Assets, D1 bindings/migrations, or when writing precise step-by-step deployment instructions for SvelteKit on Cloudflare Workers/Pages with D1. Use when this capability is needed.---# Cloudflare SvelteKit Workers D1## OverviewProvide a clear, current workflow to connect a SvelteKit TypeScript app to Cloudflare Workers and D1, including adapter setup, Wrangler configuration, D1 bindings/migrations, local testing, and deployment instructions.## Workflow Decision Tree- **Existing SvelteKit app** -> Use the Manual Setup workflow in `references/manual-workers-d1.md`.- **Brand new project** -> Use the Cloudflare framework CLI flow in `references/manual-workers-d1.md` (C3 option).- **User wants fastest/auto config** -> Use `references/wrangler-autoconfig.md` (experimental) and still verify the generated config.## Core Workflow (Manual Setup)1. Verify the latest Cloudflare + SvelteKit docs with `web.run` (adapter-cloudflare, Workers framework guide, D1 commands).2. Add the Cloudflare adapter and update `svelte.config.js`.3. Create or update `wrangler.toml` for Workers Assets and D1 bindings.4. Create the D1 database and copy its binding block into `wrangler.toml`.5. Add TypeScript platform typings and use `platform.env.DB` in server endpoints.6. Create/apply migrations locally and remotely.7. Build, test with Wrangler, then deploy.Use the exact steps and snippets in `references/manual-workers-d1.md`.## D1 Integration Checklist- Ensure the binding name is a valid JS identifier and matches `platform.env.<BINDING>` in code.- Ensure `wrangler.toml` includes `[[d1_databases]]` with `database_name` + `database_id`.- Create and apply migrations with both `--local` and `--remote` as needed.- Update TypeScript declarations in `src/app.d.ts`.## Local Dev and Testing Guidance- Prefer SvelteKit dev server for general UI work.- For Cloudflare-specific behavior, build and run `wrangler dev .svelte-kit/cloudflare`.- Use adapter `platformProxy` options if local bindings need tweaks.## Writing Deployment Instructions- Be explicit about files, commands, and where to paste blocks.- Always include the `wrangler.toml` skeleton and D1 binding block.- Include verification steps (local dev and a deploy check).- If there is any uncertainty in versions or commands, re-check docs via `web.run`.## Resources- `references/manual-workers-d1.md` - canonical manual setup workflow + snippets- `references/wrangler-autoconfig.md` - experimental Wrangler auto-setup path---> Converted and distributed by [TomeVault](https://tomevault.io/claim/maximxlss) — claim your Tome and manage your conversions.

Frequently asked questions