fix: rename title

fix: rename repos in file
Version Packages (#164 )
2026-07-04 03:19:38 +08:00 · 2026-02-27 19:53:47 +01:00 · 2026-02-27 19:35:02 +01:00 · 2026-02-22 15:05:33 +01:00 · 2026-02-22 15:02:31 +01:00 · 2026-02-11 22:57:09 +01:00
74 changed files with 4507 additions and 2012 deletions
--- a/.changeset/config.json
+++ b/.changeset/config.json
@@ -1,11 +1,11 @@
 {
 	"$schema": "https://unpkg.com/@changesets/config@3.1.1/schema.json",
-	"changelog": ["@svitejs/changesets-changelog-github-compact", { "repo": "sveltejs/mcp" }],
+	"changelog": ["@svitejs/changesets-changelog-github-compact", { "repo": "sveltejs/ai-tools" }],
 	"commit": false,
 	"fixed": [],
 	"linked": [],
 	"access": "public",
 	"baseBranch": "main",
 	"updateInternalDependencies": "patch",
-	"ignore": ["!@sveltejs/mcp"]
+	"ignore": ["!@sveltejs/mcp", "!@sveltejs/opencode"]
 }
--- a/.claude-plugin/marketplace.json
+++ b/.claude-plugin/marketplace.json
@@ -0,0 +1,22 @@
+{
+	"name": "svelte",
+	"owner": {
+		"name": "Svelte"
+	},
+	"plugins": [
+		{
+			"name": "svelte",
+			"source": "./plugins/svelte",
+			"description": "A plugin for all things Svelte development, MCP, skills, and more.",
+			"lspServers": {
+				"svelte": {
+					"command": "svelteserver",
+					"args": ["--stdio"],
+					"extensionToLanguage": {
+						".svelte": "svelte"
+					}
+				}
+			}
+		}
+	]
+}
--- a/.github/workflows/check.yml
+++ b/.github/workflows/check.yml
@@ -18,10 +18,10 @@ jobs:
      - name: Setup pnpm
        uses: pnpm/action-setup@v4
        with:
-          version: 10.26.1
+          version: 10.28.2

      - name: Setup Node.js
-        uses: actions/setup-node@v6
+        uses: actions/setup-node@6044e13b5dc448c55e2357c09f80417699197238 # v6.2.0
        with:
          node-version: '24'
          cache: 'pnpm'
--- a/.github/workflows/lint.yml
+++ b/.github/workflows/lint.yml
@@ -18,10 +18,10 @@ jobs:
      - name: Setup pnpm
        uses: pnpm/action-setup@v4
        with:
-          version: 10.26.1
+          version: 10.28.2

      - name: Setup Node.js
-        uses: actions/setup-node@v6
+        uses: actions/setup-node@6044e13b5dc448c55e2357c09f80417699197238 # v6.2.0
        with:
          node-version: '24'
          cache: 'pnpm'
--- a/.github/workflows/publish-any-commit.yml
+++ b/.github/workflows/publish-any-commit.yml
@@ -12,7 +12,7 @@ jobs:
        uses: actions/checkout@v6

      - run: corepack enable
-      - uses: actions/setup-node@v6
+      - uses: actions/setup-node@6044e13b5dc448c55e2357c09f80417699197238 # v6.2.0
        with:
          node-version: 24
          cache: 'pnpm'
@@ -20,4 +20,4 @@ jobs:
      - name: Install dependencies
        run: pnpm install

-      - run: pnpm dlx pkg-pr-new publish --compact './packages/mcp-stdio' --pnpm
+      - run: pnpm dlx pkg-pr-new publish --compact './packages/mcp-stdio' './packages/opencode' --pnpm
--- a/.github/workflows/release-svelte-skill.yml
+++ b/.github/workflows/release-svelte-skill.yml
@@ -0,0 +1,45 @@
+name: Release Svelte Code Writer Skill
+
+on:
+  push:
+    branches:
+      - main
+    paths:
+      - 'plugins/svelte/skills/svelte-code-writer/**'
+  workflow_dispatch:
+
+permissions: {}
+
+jobs:
+  release:
+    permissions:
+      contents: write
+    # prevents this action from running on forks
+    if: github.repository == 'sveltejs/ai-tools'
+    name: Release Svelte Code Writer Skill
+    runs-on: ubuntu-latest
+    steps:
+      - name: checkout
+        uses: actions/checkout@v6
+
+      - name: Get version from date
+        id: version
+        run: echo "version=$(date +'%Y.%m.%d-%H%M%S')" >> $GITHUB_OUTPUT
+
+      - name: Create zip
+        run: |
+          cd plugins/svelte/skills
+          zip -r svelte-code-writer.zip svelte-code-writer/
+
+      - name: Create Release
+        uses: softprops/action-gh-release@v2
+        with:
+          tag_name: svelte-code-writer-v${{ steps.version.outputs.version }}
+          name: Svelte Code Writer Skill v${{ steps.version.outputs.version }}
+          body: |
+            Automated release of the Svelte Code Writer skill.
+
+            This release was triggered by changes to the `plugins/svelte/skills/svelte-code-writer/` directory.
+          files: plugins/svelte/skills/svelte-code-writer.zip
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -13,11 +13,11 @@ jobs:
      id-token: write # OpenID Connect token needed for provenance
      pull-requests: write # to create pull request (changesets/action)
    # prevents this action from running on forks
-    if: github.repository == 'sveltejs/mcp'
+    if: github.repository == 'sveltejs/ai-tools'
    name: Release
    runs-on: ${{ matrix.os }}
    outputs:
-      published: ${{ steps.changesets.outputs.published }}
+      publishedPackages: ${{ steps.changesets.outputs.publishedPackages }}
    strategy:
      matrix:
        # pseudo-matrix for convenience, NEVER use more than a single combination
@@ -29,7 +29,7 @@ jobs:
        with:
          # This makes Actions fetch all Git history so that Changesets can generate changelogs with the correct commits
          fetch-depth: 0
-      - uses: actions/setup-node@v6
+      - uses: actions/setup-node@6044e13b5dc448c55e2357c09f80417699197238 # v6.2.0
        with:
          node-version: ${{ matrix.node }}
          package-manager-cache: false # pnpm is not installed yet
@@ -39,10 +39,11 @@ jobs:
          PNPM_VER=$(jq -r '.packageManager | if .[0:5] == "pnpm@" then .[5:] else "packageManager in package.json does not start with pnpm@\n" | halt_error(1)  end' package.json)
          echo installing pnpm version $PNPM_VER
          npm i -g pnpm@$PNPM_VER
-      - uses: actions/setup-node@v6
+      - uses: actions/setup-node@6044e13b5dc448c55e2357c09f80417699197238 # v6.2.0
        with:
          node-version: ${{ matrix.node }}
          package-manager-cache: true # caches pnpm via packageManager field in package.json
+          cache: 'pnpm'
      - name: install
        run: pnpm install --frozen-lockfile --prefer-offline --ignore-scripts
      - name: build
@@ -51,7 +52,7 @@ jobs:
      - name: Create Release Pull Request or Publish to npm
        id: changesets
        # pinned for security, always review third party action code before updating
-        uses: changesets/action@e0145edc7d9d8679003495b11f87bd8ef63c0cba # v1.5.3
+        uses: changesets/action@c48e67d110a68bc90ccf1098e9646092baacaa87 # v1.6.0
        with:
          # This expects you to have a script called changeset:version version that calls changeset version and updated what it needs to be updated
          version: pnpm changeset:version
@@ -63,7 +64,7 @@ jobs:

  publish-mcp:
    needs: release
-    if: needs.release.outputs.published == 'true'
+    if: contains(needs.release.outputs.publishedPackages, '"@sveltejs/ai-tools"')
    uses: ./.github/workflows/publish-mcp.yml
    secrets:
      MCP_KEY: ${{ secrets.MCP_KEY }}
--- a/.github/workflows/sync-agents-md.yml
+++ b/.github/workflows/sync-agents-md.yml
@@ -0,0 +1,71 @@
+name: Sync Agents Documentation
+
+on:
+  push:
+    branches:
+      - main
+    paths:
+      - 'instructions/AGENTS.md'
+
+permissions:
+  contents: write
+  pull-requests: write
+
+jobs:
+  sync-agents:
+    # prevents this action from running on forks
+    if: github.repository == 'sveltejs/ai-tools'
+    name: Sync AGENTS.md to OpenCode Package and Docs
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v6
+        with:
+          fetch-depth: 0
+
+      - name: Setup Node.js
+        uses: actions/setup-node@6044e13b5dc448c55e2357c09f80417699197238 # v6.2.0
+        with:
+          node-version: 24
+          package-manager-cache: false # pnpm is not installed yet
+
+      - name: Install pnpm
+        shell: bash
+        run: |
+          PNPM_VER=$(jq -r '.packageManager | if .[0:5] == "pnpm@" then .[5:] else "packageManager in package.json does not start with pnpm@\n" | halt_error(1)  end' package.json)
+          echo installing pnpm version $PNPM_VER
+          npm i -g pnpm@$PNPM_VER
+
+      - name: Sync AGENTS.md
+        run: pnpm sync-agents-md
+
+      - name: Check for changes
+        id: git-check
+        run: |
+          git diff --exit-code packages/opencode/instructions/opencode-agents.md documentation/docs/10-introduction/.generated/agents.md || echo "changed=true" >> $GITHUB_OUTPUT
+
+      - name: Create Pull Request
+        if: steps.git-check.outputs.changed == 'true'
+        uses: peter-evans/create-pull-request@c0f553fe549906ede9cf27b5156039d195d2ece0 # v8.1.0
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+          commit-message: 'chore: sync AGENTS.md to opencode package and documentation'
+          branch: chore/sync-agents-md
+          delete-branch: true
+          title: 'chore: sync AGENTS.md to opencode package and documentation'
+          body: |
+            ## Summary
+            Automatically synced AGENTS.md to the opencode package and documentation.
+
+            This PR was triggered by changes to `instructions/AGENTS.md`.
+
+            ## Changes
+            - Synced `packages/opencode/instructions/opencode-agents.md` with latest AGENTS.md
+            - Updated `documentation/docs/10-introduction/.generated/agents.md` with latest content
+
+            ## Generated by
+            GitHub Action: Sync Agents Documentation
+          labels: |
+            chore
+            documentation
+            automated
--- a/.github/workflows/sync-cursor-plugin.yml
+++ b/.github/workflows/sync-cursor-plugin.yml
@@ -0,0 +1,86 @@
+name: Sync Cursor Plugin
+
+on:
+  push:
+    branches:
+      - main
+    paths:
+      - 'plugins/svelte/skills/**'
+      - 'plugins/svelte/agents/**'
+      - 'instructions/AGENTS.md'
+
+permissions:
+  contents: write
+  pull-requests: write
+
+jobs:
+  sync-cursor:
+    # prevents this action from running on forks
+    if: github.repository == 'sveltejs/ai-tools'
+    name: Sync Cursor Plugin from Sources of Truth
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v6
+        with:
+          fetch-depth: 0
+
+      - name: Setup Node.js
+        uses: actions/setup-node@6044e13b5dc448c55e2357c09f80417699197238 # v6.2.0
+        with:
+          node-version: 24
+          package-manager-cache: false # pnpm is not installed yet
+
+      - name: Install pnpm
+        shell: bash
+        run: |
+          PNPM_VER=$(jq -r '.packageManager | if .[0:5] == "pnpm@" then .[5:] else "packageManager in package.json does not start with pnpm@\n" | halt_error(1)  end' package.json)
+          echo installing pnpm version $PNPM_VER
+          npm i -g pnpm@$PNPM_VER
+
+      - name: Setup Node.js with pnpm cache
+        uses: actions/setup-node@6044e13b5dc448c55e2357c09f80417699197238 # v6.2.0
+        with:
+          node-version: 24
+          package-manager-cache: true # caches pnpm via packageManager field in package.json
+          cache: 'pnpm'
+
+      - name: Install dependencies
+        run: pnpm install --frozen-lockfile --prefer-offline --ignore-scripts
+
+      - name: Sync Cursor plugin
+        run: pnpm sync-cursor-plugin
+
+      - name: Check for changes
+        id: git-check
+        run: |
+          git diff --exit-code svelte-cursor/ || echo "changed=true" >> $GITHUB_OUTPUT
+
+      - name: Create Pull Request
+        if: steps.git-check.outputs.changed == 'true'
+        uses: peter-evans/create-pull-request@c0f553fe549906ede9cf27b5156039d195d2ece0 # v8.1.0
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+          commit-message: 'chore: sync Cursor plugin from sources of truth'
+          branch: chore/sync-cursor-plugin
+          delete-branch: true
+          title: 'chore: sync Cursor plugin from sources of truth'
+          body: |
+            ## Summary
+            Automatically synced the Cursor plugin from sources of truth.
+
+            This PR was triggered by changes to one or more of:
+            - `plugins/svelte/skills/**` (skills)
+            - `plugins/svelte/agents/**` (agent definitions)
+            - `instructions/AGENTS.md` (agent instructions/rules)
+
+            ## Changes
+            - Synced `svelte-cursor/skills/` with latest skill definitions
+            - Synced `svelte-cursor/agents/` with latest agent definitions (stripped Claude-specific fields)
+            - Synced `svelte-cursor/rules/` with latest instructions from AGENTS.md
+
+            ## Generated by
+            GitHub Action: Sync Cursor Plugin
+          labels: |
+            chore
+            automated
--- a/.github/workflows/sync-opencode-skills.yml
+++ b/.github/workflows/sync-opencode-skills.yml
@@ -0,0 +1,84 @@
+name: Sync OpenCode Skills
+
+on:
+  push:
+    branches:
+      - main
+    paths:
+      - 'plugins/svelte/skills/**'
+
+permissions:
+  contents: write
+  pull-requests: write
+
+jobs:
+  sync-skills:
+    # prevents this action from running on forks
+    if: github.repository == 'sveltejs/ai-tools'
+    name: Sync Skills to OpenCode Package and Update Docs
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v6
+        with:
+          fetch-depth: 0
+
+      - name: Setup Node.js
+        uses: actions/setup-node@6044e13b5dc448c55e2357c09f80417699197238 # v6.2.0
+        with:
+          node-version: 24
+          package-manager-cache: false # pnpm is not installed yet
+
+      - name: Install pnpm
+        shell: bash
+        run: |
+          PNPM_VER=$(jq -r '.packageManager | if .[0:5] == "pnpm@" then .[5:] else "packageManager in package.json does not start with pnpm@\n" | halt_error(1)  end' package.json)
+          echo installing pnpm version $PNPM_VER
+          npm i -g pnpm@$PNPM_VER
+
+      - name: Setup Node.js with pnpm cache
+        uses: actions/setup-node@6044e13b5dc448c55e2357c09f80417699197238 # v6.2.0
+        with:
+          node-version: 24
+          package-manager-cache: true # caches pnpm via packageManager field in package.json
+          cache: 'pnpm'
+
+      - name: Install dependencies
+        run: pnpm install --frozen-lockfile --prefer-offline --ignore-scripts
+
+      - name: Sync skills folder
+        run: pnpm sync-opencode-skills
+
+      - name: Generate skills documentation
+        run: pnpm generate-skill-docs
+
+      - name: Check for changes
+        id: git-check
+        run: |
+          git diff --exit-code packages/opencode/skills documentation/docs/60-skills/10-skills.md || echo "changed=true" >> $GITHUB_OUTPUT
+
+      - name: Create Pull Request
+        if: steps.git-check.outputs.changed == 'true'
+        uses: peter-evans/create-pull-request@c0f553fe549906ede9cf27b5156039d195d2ece0 # v8.1.0
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+          commit-message: 'chore: sync skills and update documentation'
+          branch: chore/sync-opencode-skills
+          delete-branch: true
+          title: 'chore: sync skills and update documentation'
+          body: |
+            ## Summary
+            Automatically synced skills and updated documentation.
+
+            This PR was triggered by changes to the skills folder in `plugins/svelte/skills/`.
+
+            ## Changes
+            - Synced `packages/opencode/skills/` with latest skill definitions
+            - Updated `documentation/docs/60-skills/10-skills.md` with latest skill documentation
+
+            ## Generated by
+            GitHub Action: Sync OpenCode Skills
+          labels: |
+            chore
+            documentation
+            automated
--- a/.github/workflows/test.yml
+++ b/.github/workflows/test.yml
@@ -18,10 +18,10 @@ jobs:
      - name: Setup pnpm
        uses: pnpm/action-setup@v4
        with:
-          version: 10.26.1
+          version: 10.28.2

      - name: Setup Node.js
-        uses: actions/setup-node@v6
+        uses: actions/setup-node@6044e13b5dc448c55e2357c09f80417699197238 # v6.2.0
        with:
          node-version: '24'
          cache: 'pnpm'
--- a/.github/workflows/update-opencode-jsonschema.yml
+++ b/.github/workflows/update-opencode-jsonschema.yml
@@ -0,0 +1,78 @@
+name: Update OpenCode JSON Schema
+
+on:
+  push:
+    branches:
+      - main
+    paths:
+      - 'packages/opencode/config.ts'
+
+permissions:
+  contents: write
+  pull-requests: write
+
+jobs:
+  update-docs:
+    # prevents this action from running on forks
+    if: github.repository == 'sveltejs/ai-tools'
+    name: Update OpenCode JSON Schema
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v6
+        with:
+          fetch-depth: 0
+
+      - name: Setup Node.js
+        uses: actions/setup-node@6044e13b5dc448c55e2357c09f80417699197238 # v6.2.0
+        with:
+          node-version: 24
+          package-manager-cache: false # pnpm is not installed yet
+
+      - name: Install pnpm
+        shell: bash
+        run: |
+          PNPM_VER=$(jq -r '.packageManager | if .[0:5] == "pnpm@" then .[5:] else "packageManager in package.json does not start with pnpm@\n" | halt_error(1)  end' package.json)
+          echo installing pnpm version $PNPM_VER
+          npm i -g pnpm@$PNPM_VER
+
+      - name: Setup Node.js with pnpm cache
+        uses: actions/setup-node@6044e13b5dc448c55e2357c09f80417699197238 # v6.2.0
+        with:
+          node-version: 24
+          package-manager-cache: true # caches pnpm via packageManager field in package.json
+          cache: 'pnpm'
+
+      - name: Install dependencies
+        run: pnpm install --frozen-lockfile --prefer-offline --ignore-scripts
+
+      - name: Generate opencode JSON schema
+        run: pnpm generate-opencode-jsonschema
+
+      - name: Check for changes
+        id: git-check
+        run: |
+          git diff --exit-code packages/opencode/schema.json || echo "changed=true" >> $GITHUB_OUTPUT
+
+      - name: Create Pull Request
+        if: steps.git-check.outputs.changed == 'true'
+        uses: peter-evans/create-pull-request@c0f553fe549906ede9cf27b5156039d195d2ece0 # v8.1.0
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+          commit-message: 'docs: update opencode JSON schema'
+          branch: docs/update-opencode-jsonschema
+          delete-branch: true
+          title: 'docs: update opencode JSON schema'
+          body: |
+            ## Summary
+            Automatically generated update for OpenCode JSON schema.
+
+            This PR was triggered by changes to the OpenCode configuration file `packages/opencode/config.ts`.
+
+            ## Changes
+            - Updated `packages/opencode/schema.json` with latest JSON schema
+
+            ## Generated by
+            GitHub Action: Update OpenCode JSON Schema
+          labels: |
+            automated
--- a/.github/workflows/update-prompt-docs.yml
+++ b/.github/workflows/update-prompt-docs.yml
@@ -14,7 +14,7 @@ permissions:
 jobs:
  update-docs:
    # prevents this action from running on forks
-    if: github.repository == 'sveltejs/mcp'
+    if: github.repository == 'sveltejs/ai-tools'
    name: Update Prompt Documentation
    runs-on: ubuntu-latest
    steps:
@@ -24,7 +24,7 @@ jobs:
          fetch-depth: 0

      - name: Setup Node.js
-        uses: actions/setup-node@v6
+        uses: actions/setup-node@6044e13b5dc448c55e2357c09f80417699197238 # v6.2.0
        with:
          node-version: 24
          package-manager-cache: false # pnpm is not installed yet
@@ -37,10 +37,11 @@ jobs:
          npm i -g pnpm@$PNPM_VER

      - name: Setup Node.js with pnpm cache
-        uses: actions/setup-node@v6
+        uses: actions/setup-node@6044e13b5dc448c55e2357c09f80417699197238 # v6.2.0
        with:
          node-version: 24
          package-manager-cache: true # caches pnpm via packageManager field in package.json
+          cache: 'pnpm'

      - name: Install dependencies
        run: pnpm install --frozen-lockfile --prefer-offline --ignore-scripts
@@ -55,7 +56,7 @@ jobs:

      - name: Create Pull Request
        if: steps.git-check.outputs.changed == 'true'
-        uses: peter-evans/create-pull-request@v8
+        uses: peter-evans/create-pull-request@c0f553fe549906ede9cf27b5156039d195d2ece0 # v8.1.0
        with:
          token: ${{ secrets.GITHUB_TOKEN }}
          commit-message: 'docs: update prompts documentation'
--- a/.prettierignore
+++ b/.prettierignore
@@ -12,4 +12,6 @@ bun.lockb

 # Claude Code
 .claude/
-.changeset/
+.changeset/
+
+/packages/opencode/schema.json
--- a/apps/mcp-remote/src/hooks.server.ts
+++ b/apps/mcp-remote/src/hooks.server.ts
@@ -25,22 +25,5 @@ export async function handle({ event, resolve }) {
 					await track(event, { session_id, ...(extra ? { extra } : {}) });
 				},
 	});
-	// we are deploying on vercel the SSE connection will timeout after 5 minutes...for
-	// the moment we are not sending back any notifications (logs, or list changed notifications)
-	// so it's a waste of resources to keep a connection open that will error
-	// after 5 minutes making the logs dirty. For this reason if we have a response from
-	// the MCP server and it's a GET request we just return an empty response (it has to be
-	// 200 or the MCP client will complain)
-	if (mcp_response && event.request.method === 'GET') {
-		try {
-			return mcp_response;
-		} finally {
-			try {
-				await mcp_response.body?.cancel();
-			} catch {
-				// ignore
-			}
-		}
-	}
 	return mcp_response ?? resolve(event);
 }
--- a/apps/mcp-remote/src/lib/mcp/index.ts
+++ b/apps/mcp-remote/src/lib/mcp/index.ts
@@ -4,4 +4,9 @@ import { HttpTransport } from '@tmcp/transport-http';
 export const http_transport = new HttpTransport(server, {
 	cors: true,
 	path: '/mcp',
+	// we are deploying on vercel the SSE connection will timeout after 5 minutes...for
+	// the moment we are not sending back any notifications (logs, or list changed notifications)
+	// so it's a waste of resources to keep a connection open that will error
+	// after 5 minutes making the logs dirty.
+	disableSse: true,
 });
--- a/documentation/docs/10-introduction/.generated/agents.md
+++ b/documentation/docs/10-introduction/.generated/agents.md
@@ -0,0 +1,23 @@
+You are able to use the Svelte MCP server, where you have access to comprehensive Svelte 5 and SvelteKit documentation. Here's how to use the available tools effectively:
+
+## Available Svelte MCP Tools:
+
+### 1. list-sections
+
+Use this FIRST to discover all available documentation sections. Returns a structured list with titles, use_cases, and paths.
+When asked about Svelte or SvelteKit topics, ALWAYS use this tool at the start of the chat to find relevant sections.
+
+### 2. get-documentation
+
+Retrieves full documentation content for specific sections. Accepts single or multiple sections.
+After calling the list-sections tool, you MUST analyze the returned documentation sections (especially the use_cases field) and then use the get-documentation tool to fetch ALL documentation sections that are relevant for the user's task.
+
+### 3. svelte-autofixer
+
+Analyzes Svelte code and returns issues and suggestions.
+You MUST use this tool whenever writing Svelte code before sending it to the user. Keep calling it until no issues or suggestions are returned.
+
+### 4. playground-link
+
+Generates a Svelte Playground link with the provided code.
+After completing the code, ask the user if they want a playground link. Only call this tool after user confirmation and NEVER if code was written to files in their project.
--- a/documentation/docs/10-introduction/10-overview.md
+++ b/documentation/docs/10-introduction/10-overview.md
@@ -17,30 +17,6 @@ To get the most out of the MCP server we recommend including the following promp

 > [!NOTE] This is already setup for you when using `npx sv add mcp`

-```md
-You are able to use the Svelte MCP server, where you have access to comprehensive Svelte 5 and SvelteKit documentation. Here's how to use the available tools effectively:
-
-## Available MCP Tools:
-
-### 1. list-sections
-
-Use this FIRST to discover all available documentation sections. Returns a structured list with titles, use_cases, and paths.
-When asked about Svelte or SvelteKit topics, ALWAYS use this tool at the start of the chat to find relevant sections.
-
-### 2. get-documentation
-
-Retrieves full documentation content for specific sections. Accepts single or multiple sections.
-After calling the list-sections tool, you MUST analyze the returned documentation sections (especially the use_cases field) and then use the get-documentation tool to fetch ALL documentation sections that are relevant for the user's task.
-
-### 3. svelte-autofixer
-
-Analyzes Svelte code and returns issues and suggestions.
-You MUST use this tool whenever writing Svelte code before sending it to the user. Keep calling it until no issues or suggestions are returned.
-
-### 4. playground-link
-
-Generates a Svelte Playground link with the provided code.
-After completing the code, ask the user if they want a playground link. Only call this tool after user confirmation and NEVER if code was written to files in their project.
-```
+@include .generated/agents.md

 If your MCP client supports it, we also recommend using the [svelte-task](prompts#svelte-task) prompt to instruct the LLM on the best way to use the MCP server.
--- a/documentation/docs/20-setup/20-local-setup.md
+++ b/documentation/docs/20-setup/20-local-setup.md
@@ -45,6 +45,27 @@ command = "npx"
 args = ["-y", "@sveltejs/mcp"]
 ```

+## Copilot CLI
+
+Use the Copilot CLI to interactively add the MCP server:
+
+```bash
+/mcp add
+```
+
+Alternatively, create or edit `~/.copilot/mcp-config.json` and add the following configuration:
+
+```json
+{
+	"mcpServers": {
+		"svelte": {
+			"command": "npx",
+			"args": ["-y", "@sveltejs/mcp"]
+		}
+	}
+}
+```
+
 ## Gemini CLI

 To include the local MCP version in Gemini CLI, simply run the following command:
@@ -57,7 +78,7 @@ The `[scope]` must be `user`, `project` or `local`.

 ## OpenCode

-Run the command:
+You can automatically configure the MCP server using the [OpenCode plugin](opencode-plugin) (recommended). If you prefer to configure the MCP server manually, run:

 ```bash
 opencode mcp add
--- a/documentation/docs/20-setup/30-remote-setup.md
+++ b/documentation/docs/20-setup/30-remote-setup.md
@@ -16,6 +16,8 @@ claude mcp add -t http -s [scope] svelte https://mcp.svelte.dev/mcp

 You can choose your preferred `scope` (it must be `user`, `project` or `local`) and `name`.

+If you prefer you can also install the `svelte` plugin in [the Svelte Claude Code Marketplace](plugin) that will give you both the remote server and useful [skills](skills).
+
 ## Claude Desktop

 - Open Settings > Connectors
@@ -34,6 +36,26 @@ experimental_use_rmcp_client = true
 url = "https://mcp.svelte.dev/mcp"
 ```

+## Copilot CLI
+
+Use the Copilot CLI to interactively add the MCP server:
+
+```bash
+/mcp add
+```
+
+Alternatively, create or edit `~/.copilot/mcp-config.json` and add the following configuration:
+
+```json
+{
+	"mcpServers": {
+		"svelte": {
+			"url": "https://mcp.svelte.dev/mcp"
+		}
+	}
+}
+```
+
 ## Gemini CLI

 To use the remote MCP server with Gemini CLI, simply run the following command:
@@ -46,7 +68,7 @@ The `[scope]` must be `user` or `project`.

 ## OpenCode

-Run the command:
+You can automatically configure the MCP server using the [OpenCode plugin](opencode-plugin) (recommended). If you prefer to configure the MCP server manually, run:

 ```bash
 opencode mcp add
--- a/documentation/docs/30-capabilities/.generated/prompts.md
+++ b/documentation/docs/30-capabilities/.generated/prompts.md
@@ -0,0 +1,209 @@
+## svelte-task
+
+This prompt should be used whenever you are asking the model to work on a Svelte-related task. It will instruct the LLM which documentation sections are available, which tools to invoke, when to invoke them, and how to interpret the results.
+
+<details>
+	<summary>Copy the prompt</summary>
+
+```md
+You are a Svelte expert tasked to build components and utilities for Svelte developers. If you need documentation for anything related to Svelte you can invoke the tool `get-documentation` with one of the following paths. However: before invoking the `get-documentation` tool, try to answer the users query using your own knowledge and the `svelte-autofixer` tool. Be mindful of how many section you request, since it is token-intensive!
+<available-docs>
+
+- title: Overview, use_cases: project setup, creating new svelte apps, scaffolding, cli tools, initializing projects, path: cli/overview
+- title: Frequently asked questions, use_cases: project setup, initializing new svelte projects, troubleshooting cli installation, package manager configuration, path: cli/faq
+- title: sv create, use_cases: project setup, starting new sveltekit app, initializing project, creating from playground, choosing project template, path: cli/sv-create
+- title: sv add, use_cases: project setup, adding features to existing projects, integrating tools, testing setup, styling setup, authentication, database setup, deployment adapters, path: cli/sv-add
+- title: sv check, use_cases: code quality, ci/cd pipelines, error checking, typescript projects, pre-commit hooks, finding unused css, accessibility auditing, production builds, path: cli/sv-check
+- title: sv migrate, use_cases: migration, upgrading svelte versions, upgrading sveltekit versions, modernizing codebase, svelte 3 to 4, svelte 4 to 5, sveltekit 1 to 2, adopting runes, refactoring deprecated apis, path: cli/sv-migrate
+- title: devtools-json, use_cases: development setup, chrome devtools integration, browser-based editing, local development workflow, debugging setup, path: cli/devtools-json
+- title: drizzle, use_cases: database setup, sql queries, orm integration, data modeling, postgresql, mysql, sqlite, server-side data access, database migrations, type-safe queries, path: cli/drizzle
+- title: eslint, use_cases: code quality, linting, error detection, project setup, code standards, team collaboration, typescript projects, path: cli/eslint
+- title: lucia, use_cases: authentication, login systems, user management, registration pages, session handling, auth setup, path: cli/lucia
+- title: mcp, use_cases: use title and path to estimate use case, path: cli/mcp
+- title: mdsvex, use_cases: blog, content sites, markdown rendering, documentation sites, technical writing, cms integration, article pages, path: cli/mdsvex
+- title: paraglide, use_cases: internationalization, multi-language sites, i18n, translation, localization, language switching, global apps, multilingual content, path: cli/paraglide
+- title: playwright, use_cases: browser testing, e2e testing, integration testing, test automation, quality assurance, ci/cd pipelines, testing user flows, path: cli/playwright
+- title: prettier, use_cases: code formatting, project setup, code style consistency, team collaboration, linting configuration, path: cli/prettier
+- title: storybook, use_cases: component development, design systems, ui library, isolated component testing, documentation, visual testing, component showcase, path: cli/storybook
+- title: sveltekit-adapter, use_cases: deployment, production builds, hosting setup, choosing deployment platform, configuring adapters, static site generation, node server, vercel, cloudflare, netlify, path: cli/sveltekit-adapter
+- title: tailwindcss, use_cases: project setup, styling, css framework, rapid prototyping, utility-first css, design systems, responsive design, adding tailwind to svelte, path: cli/tailwind
+- title: vitest, use_cases: testing, unit tests, component testing, test setup, quality assurance, ci/cd pipelines, test-driven development, path: cli/vitest
+- title: add-on, use_cases: use title and path to estimate use case, path: cli/add-on
+- title: Introduction, use_cases: learning sveltekit, project setup, understanding framework basics, choosing between svelte and sveltekit, getting started with full-stack apps, path: kit/introduction
+- title: Creating a project, use_cases: project setup, starting new sveltekit app, initial development environment, first-time sveltekit users, scaffolding projects, path: kit/creating-a-project
+- title: Project types, use_cases: deployment, project setup, choosing adapters, ssg, spa, ssr, serverless, mobile apps, desktop apps, pwa, offline apps, browser extensions, separate backend, docker containers, path: kit/project-types
+- title: Project structure, use_cases: project setup, understanding file structure, organizing code, starting new project, learning sveltekit basics, path: kit/project-structure
+- title: Web standards, use_cases: always, any sveltekit project, data fetching, forms, api routes, server-side rendering, deployment to various platforms, path: kit/web-standards
+- title: Routing, use_cases: routing, navigation, multi-page apps, project setup, file structure, api endpoints, data loading, layouts, error pages, always, path: kit/routing
+- title: Loading data, use_cases: data fetching, api calls, database queries, dynamic routes, page initialization, loading states, authentication checks, ssr data, form data, content rendering, path: kit/load
+- title: Form actions, use_cases: forms, user input, data submission, authentication, login systems, user registration, progressive enhancement, validation errors, path: kit/form-actions
+- title: Page options, use_cases: prerendering static sites, ssr configuration, spa setup, client-side rendering control, url trailing slash handling, adapter deployment config, build optimization, path: kit/page-options
+- title: State management, use_cases: sveltekit, server-side rendering, ssr, state management, authentication, data persistence, load functions, context api, navigation, component lifecycle, path: kit/state-management
+- title: Remote functions, use_cases: data fetching, server-side logic, database queries, type-safe client-server communication, forms, user input, mutations, authentication, crud operations, optimistic updates, path: kit/remote-functions
+- title: Building your app, use_cases: production builds, deployment preparation, build process optimization, adapter configuration, preview before deployment, path: kit/building-your-app
+- title: Adapters, use_cases: deployment, production builds, hosting setup, choosing deployment platform, configuring adapters, path: kit/adapters
+- title: Zero-config deployments, use_cases: deployment, production builds, hosting setup, choosing deployment platform, ci/cd configuration, path: kit/adapter-auto
+- title: Node servers, use_cases: deployment, production builds, node.js hosting, custom server setup, environment configuration, reverse proxy setup, docker deployment, systemd services, path: kit/adapter-node
+- title: Static site generation, use_cases: static site generation, ssg, prerendering, deployment, github pages, spa mode, blogs, documentation sites, marketing sites, path: kit/adapter-static
+- title: Single-page apps, use_cases: spa mode, single-page apps, client-only rendering, static hosting, mobile app wrappers, no server-side logic, adapter-static setup, fallback pages, path: kit/single-page-apps
+- title: Cloudflare, use_cases: deployment, cloudflare workers, cloudflare pages, hosting setup, production builds, serverless deployment, edge computing, path: kit/adapter-cloudflare
+- title: Cloudflare Workers, use_cases: deploying to cloudflare workers, cloudflare workers sites deployment, legacy cloudflare adapter, wrangler configuration, cloudflare platform bindings, path: kit/adapter-cloudflare-workers
+- title: Netlify, use_cases: deployment, netlify hosting, production builds, serverless functions, edge functions, static site hosting, path: kit/adapter-netlify
+- title: Vercel, use_cases: deployment, vercel hosting, production builds, serverless functions, edge functions, isr, image optimization, environment variables, path: kit/adapter-vercel
+- title: Writing adapters, use_cases: custom deployment, building adapters, unsupported platforms, adapter development, custom hosting environments, path: kit/writing-adapters
+- title: Advanced routing, use_cases: advanced routing, dynamic routes, file viewers, nested paths, custom 404 pages, url validation, route parameters, multi-level navigation, path: kit/advanced-routing
+- title: Hooks, use_cases: authentication, logging, error tracking, request interception, api proxying, custom routing, internationalization, database initialization, middleware logic, session management, path: kit/hooks
+- title: Errors, use_cases: error handling, custom error pages, 404 pages, api error responses, production error logging, error tracking, type-safe errors, path: kit/errors
+- title: Link options, use_cases: routing, navigation, multi-page apps, performance optimization, link preloading, forms with get method, search functionality, focus management, scroll behavior, path: kit/link-options
+- title: Service workers, use_cases: offline support, pwa, caching strategies, performance optimization, precaching assets, network resilience, progressive web apps, path: kit/service-workers
+- title: Server-only modules, use_cases: api keys, environment variables, sensitive data protection, backend security, preventing data leaks, server-side code isolation, path: kit/server-only-modules
+- title: Snapshots, use_cases: forms, user input, preserving form data, multi-step forms, navigation state, preventing data loss, textarea content, input fields, comment systems, surveys, path: kit/snapshots
+- title: Shallow routing, use_cases: modals, dialogs, image galleries, overlays, history-driven ui, mobile-friendly navigation, photo viewers, lightboxes, drawer menus, path: kit/shallow-routing
+- title: Observability, use_cases: performance monitoring, debugging, observability, tracing requests, production diagnostics, analyzing slow requests, finding bottlenecks, monitoring server-side operations, path: kit/observability
+- title: Packaging, use_cases: building component libraries, publishing npm packages, creating reusable svelte components, library development, package distribution, path: kit/packaging
+- title: Auth, use_cases: authentication, login systems, user management, session handling, jwt tokens, protected routes, user credentials, authorization checks, path: kit/auth
+- title: Performance, use_cases: performance optimization, slow loading pages, production deployment, debugging performance issues, reducing bundle size, improving load times, path: kit/performance
+- title: Icons, use_cases: icons, ui components, styling, css frameworks, tailwind, unocss, performance optimization, dependency management, path: kit/icons
+- title: Images, use_cases: image optimization, responsive images, performance, hero images, product photos, galleries, cms integration, cdn setup, asset management, path: kit/images
+- title: Accessibility, use_cases: always, any sveltekit project, screen reader support, keyboard navigation, multi-page apps, client-side routing, internationalization, multilingual sites, path: kit/accessibility
+- title: SEO, use_cases: seo optimization, search engine ranking, content sites, blogs, marketing sites, public-facing apps, sitemaps, amp pages, meta tags, performance optimization, path: kit/seo
+- title: Frequently asked questions, use_cases: troubleshooting package imports, library compatibility issues, client-side code execution, external api integration, middleware setup, database configuration, view transitions, yarn configuration, path: kit/faq
+- title: Integrations, use_cases: project setup, css preprocessors, postcss, scss, sass, less, stylus, typescript setup, adding integrations, tailwind, testing, auth, linting, formatting, path: kit/integrations
+- title: Breakpoint Debugging, use_cases: debugging, breakpoints, development workflow, troubleshooting issues, vscode setup, ide configuration, inspecting code execution, path: kit/debugging
+- title: Migrating to SvelteKit v2, use_cases: migration, upgrading from sveltekit 1 to 2, breaking changes, version updates, path: kit/migrating-to-sveltekit-2
+- title: Migrating from Sapper, use_cases: migrating from sapper, upgrading legacy projects, sapper to sveltekit conversion, project modernization, path: kit/migrating
+- title: Additional resources, use_cases: troubleshooting, getting help, finding examples, learning sveltekit, project templates, common issues, community support, path: kit/additional-resources
+- title: Glossary, use_cases: rendering strategies, performance optimization, deployment configuration, seo requirements, static sites, spas, server-side rendering, prerendering, edge deployment, pwa development, path: kit/glossary
+- title: @sveltejs/kit, use_cases: forms, form actions, server-side validation, form submission, error handling, redirects, json responses, http errors, server utilities, path: kit/@sveltejs-kit
+- title: @sveltejs/kit/hooks, use_cases: middleware, request processing, authentication chains, logging, multiple hooks, request/response transformation, path: kit/@sveltejs-kit-hooks
+- title: @sveltejs/kit/node/polyfills, use_cases: node.js environments, custom servers, non-standard runtimes, ssr setup, web api compatibility, polyfill requirements, path: kit/@sveltejs-kit-node-polyfills
+- title: @sveltejs/kit/node, use_cases: node.js adapter, custom server setup, http integration, streaming files, node deployment, server-side rendering with node, path: kit/@sveltejs-kit-node
+- title: @sveltejs/kit/vite, use_cases: project setup, vite configuration, initial sveltekit setup, build tooling, path: kit/@sveltejs-kit-vite
+- title: $app/environment, use_cases: always, conditional logic, client-side code, server-side code, build-time logic, prerendering, development vs production, environment detection, path: kit/$app-environment
+- title: $app/forms, use_cases: forms, user input, data submission, progressive enhancement, custom form handling, form validation, path: kit/$app-forms
+- title: $app/navigation, use_cases: routing, navigation, multi-page apps, programmatic navigation, data reloading, preloading, shallow routing, navigation lifecycle, scroll handling, view transitions, path: kit/$app-navigation
+- title: $app/paths, use_cases: static assets, images, fonts, public files, base path configuration, subdirectory deployment, cdn setup, asset urls, links, navigation, path: kit/$app-paths
+- title: $app/server, use_cases: remote functions, server-side logic, data fetching, form handling, api endpoints, client-server communication, prerendering, file reading, batch queries, path: kit/$app-server
+- title: $app/state, use_cases: routing, navigation, multi-page apps, loading states, url parameters, form handling, error states, version updates, page metadata, shallow routing, path: kit/$app-state
+- title: $app/stores, use_cases: legacy projects, sveltekit pre-2.12, migration from stores to runes, maintaining older codebases, accessing page data, navigation state, app version updates, path: kit/$app-stores
+- title: $app/types, use_cases: routing, navigation, type safety, route parameters, dynamic routes, link generation, pathname validation, multi-page apps, path: kit/$app-types
+- title: $env/dynamic/private, use_cases: api keys, secrets management, server-side config, environment variables, backend logic, deployment-specific settings, private data handling, path: kit/$env-dynamic-private
+- title: $env/dynamic/public, use_cases: environment variables, client-side config, runtime configuration, public api keys, deployment-specific settings, multi-environment apps, path: kit/$env-dynamic-public
+- title: $env/static/private, use_cases: server-side api keys, backend secrets, database credentials, private configuration, build-time optimization, server endpoints, authentication tokens, path: kit/$env-static-private
+- title: $env/static/public, use_cases: environment variables, public config, client-side data, api endpoints, build-time configuration, public constants, path: kit/$env-static-public
+- title: $lib, use_cases: project setup, component organization, importing shared components, reusable ui elements, code structure, path: kit/$lib
+- title: $service-worker, use_cases: offline support, pwa, service workers, caching strategies, progressive web apps, offline-first apps, path: kit/$service-worker
+- title: Configuration, use_cases: project setup, configuration, adapters, deployment, build settings, environment variables, routing customization, prerendering, csp security, csrf protection, path configuration, typescript setup, path: kit/configuration
+- title: Command Line Interface, use_cases: project setup, typescript configuration, generated types, ./$types imports, initial project configuration, path: kit/cli
+- title: Types, use_cases: typescript, type safety, route parameters, api endpoints, load functions, form actions, generated types, jsconfig setup, path: kit/types
+- title: Overview, use_cases: use title and path to estimate use case, path: mcp/overview
+- title: Local setup, use_cases: use title and path to estimate use case, path: mcp/local-setup
+- title: Remote setup, use_cases: use title and path to estimate use case, path: mcp/remote-setup
+- title: Tools, use_cases: use title and path to estimate use case, path: mcp/tools
+- title: Resources, use_cases: use title and path to estimate use case, path: mcp/resources
+- title: Prompts, use_cases: use title and path to estimate use case, path: mcp/prompts
+- title: Overview, use_cases: use title and path to estimate use case, path: mcp/plugin
+- title: Skill, use_cases: use title and path to estimate use case, path: mcp/skill
+- title: Subagent, use_cases: use title and path to estimate use case, path: mcp/subagent
+- title: Overview, use_cases: use title and path to estimate use case, path: mcp/opencode-plugin
+- title: Subagent, use_cases: use title and path to estimate use case, path: mcp/opencode-subagent
+- title: Overview, use_cases: always, any svelte project, getting started, learning svelte, introduction, project setup, understanding framework basics, path: svelte/overview
+- title: Getting started, use_cases: project setup, starting new svelte project, initial installation, choosing between sveltekit and vite, editor configuration, path: svelte/getting-started
+- title: .svelte files, use_cases: always, any svelte project, component creation, project setup, learning svelte basics, path: svelte/svelte-files
+- title: .svelte.js and .svelte.ts files, use_cases: shared reactive state, reusable reactive logic, state management across components, global stores, custom reactive utilities, path: svelte/svelte-js-files
+- title: What are runes?, use_cases: always, any svelte 5 project, understanding core syntax, learning svelte 5, migration from svelte 4, path: svelte/what-are-runes
+- title: $state, use_cases: always, any svelte project, core reactivity, state management, counters, forms, todo apps, interactive ui, data updates, class-based components, path: svelte/$state
+- title: $derived, use_cases: always, any svelte project, computed values, reactive calculations, derived data, transforming state, dependent values, path: svelte/$derived
+- title: $effect, use_cases: canvas drawing, third-party library integration, dom manipulation, side effects, intervals, timers, network requests, analytics tracking, path: svelte/$effect
+- title: $props, use_cases: always, any svelte project, passing data to components, component communication, reusable components, component props, path: svelte/$props
+- title: $bindable, use_cases: forms, user input, two-way data binding, custom input components, parent-child communication, reusable form fields, path: svelte/$bindable
+- title: $inspect, use_cases: debugging, development, tracking state changes, reactive state monitoring, troubleshooting reactivity issues, path: svelte/$inspect
+- title: $host, use_cases: custom elements, web components, dispatching custom events, component library, framework-agnostic components, path: svelte/$host
+- title: Basic markup, use_cases: always, any svelte project, basic markup, html templating, component structure, attributes, events, props, text rendering, path: svelte/basic-markup
+- title: {#if ...}, use_cases: always, conditional rendering, showing/hiding content, dynamic ui, user permissions, loading states, error handling, form validation, path: svelte/if
+- title: {#each ...}, use_cases: always, lists, arrays, iteration, product listings, todos, tables, grids, dynamic content, shopping carts, user lists, comments, feeds, path: svelte/each
+- title: {#key ...}, use_cases: animations, transitions, component reinitialization, forcing component remount, value-based ui updates, resetting component state, path: svelte/key
+- title: {#await ...}, use_cases: async data fetching, api calls, loading states, promises, error handling, lazy loading components, dynamic imports, path: svelte/await
+- title: {#snippet ...}, use_cases: reusable markup, component composition, passing content to components, table rows, list items, conditional rendering, reducing duplication, path: svelte/snippet
+- title: {@render ...}, use_cases: reusable ui patterns, component composition, conditional rendering, fallback content, layout components, slot alternatives, template reuse, path: svelte/@render
+- title: {@html ...}, use_cases: rendering html strings, cms content, rich text editors, markdown to html, blog posts, wysiwyg output, sanitized html injection, dynamic html content, path: svelte/@html
+- title: {@attach ...}, use_cases: tooltips, popovers, dom manipulation, third-party libraries, canvas drawing, element lifecycle, interactive ui, custom directives, wrapper components, path: svelte/@attach
+- title: {@const ...}, use_cases: computed values in loops, derived calculations in blocks, local variables in each iterations, complex list rendering, path: svelte/@const
+- title: {@debug ...}, use_cases: debugging, development, troubleshooting, tracking state changes, monitoring variables, reactive data inspection, path: svelte/@debug
+- title: bind:, use_cases: forms, user input, two-way data binding, interactive ui, media players, file uploads, checkboxes, radio buttons, select dropdowns, contenteditable, dimension tracking, path: svelte/bind
+- title: use:, use_cases: custom directives, dom manipulation, third-party library integration, tooltips, click outside, gestures, focus management, element lifecycle hooks, path: svelte/use
+- title: transition:, use_cases: animations, interactive ui, modals, dropdowns, notifications, conditional content, show/hide elements, smooth state changes, path: svelte/transition
+- title: in: and out:, use_cases: animation, transitions, interactive ui, conditional rendering, independent enter/exit effects, modals, tooltips, notifications, path: svelte/in-and-out
+- title: animate:, use_cases: sortable lists, drag and drop, reorderable items, todo lists, kanban boards, playlist editors, priority queues, animated list reordering, path: svelte/animate
+- title: style:, use_cases: dynamic styling, conditional styles, theming, dark mode, responsive design, interactive ui, component styling, path: svelte/style
+- title: class, use_cases: always, conditional styling, dynamic classes, tailwind css, component styling, reusable components, responsive design, path: svelte/class
+- title: await, use_cases: async data fetching, loading states, server-side rendering, awaiting promises in components, async validation, concurrent data loading, path: svelte/await-expressions
+- title: Scoped styles, use_cases: always, styling components, scoped css, component-specific styles, preventing style conflicts, animations, keyframes, path: svelte/scoped-styles
+- title: Global styles, use_cases: global styles, third-party libraries, css resets, animations, styling body/html, overriding component styles, shared keyframes, base styles, path: svelte/global-styles
+- title: Custom properties, use_cases: theming, custom styling, reusable components, design systems, dynamic colors, component libraries, ui customization, path: svelte/custom-properties
+- title: Nested <style> elements, use_cases: component styling, scoped styles, dynamic styles, conditional styling, nested style tags, custom styling logic, path: svelte/nested-style-elements
+- title: <svelte:boundary>, use_cases: error handling, async data loading, loading states, error recovery, flaky components, error reporting, resilient ui, path: svelte/svelte-boundary
+- title: <svelte:window>, use_cases: keyboard shortcuts, scroll tracking, window resize handling, responsive layouts, online/offline detection, viewport dimensions, global event listeners, path: svelte/svelte-window
+- title: <svelte:document>, use_cases: document events, visibility tracking, fullscreen detection, pointer lock, focus management, document-level interactions, path: svelte/svelte-document
+- title: <svelte:body>, use_cases: mouse tracking, hover effects, cursor interactions, global body events, drag and drop, custom cursors, interactive backgrounds, body-level actions, path: svelte/svelte-body
+- title: <svelte:head>, use_cases: seo optimization, page titles, meta tags, social media sharing, dynamic head content, multi-page apps, blog posts, product pages, path: svelte/svelte-head
+- title: <svelte:element>, use_cases: dynamic content, cms integration, user-generated content, configurable ui, runtime element selection, flexible components, path: svelte/svelte-element
+- title: <svelte:options>, use_cases: migration, custom elements, web components, legacy mode compatibility, runes mode setup, svg components, mathml components, css injection control, path: svelte/svelte-options
+- title: Stores, use_cases: shared state, cross-component data, reactive values, async data streams, manual control over updates, rxjs integration, extracting logic, path: svelte/stores
+- title: Context, use_cases: shared state, avoiding prop drilling, component communication, theme providers, user context, authentication state, configuration sharing, deeply nested components, path: svelte/context
+- title: Lifecycle hooks, use_cases: component initialization, cleanup tasks, timers, subscriptions, dom measurements, chat windows, autoscroll features, migration from svelte 4, path: svelte/lifecycle-hooks
+- title: Imperative component API, use_cases: project setup, client-side rendering, server-side rendering, ssr, hydration, testing, programmatic component creation, tooltips, dynamic mounting, path: svelte/imperative-component-api
+- title: Hydratable data, use_cases: use title and path to estimate use case, path: svelte/hydratable
+- title: Testing, use_cases: testing, quality assurance, unit tests, integration tests, component tests, e2e tests, vitest setup, playwright setup, test automation, path: svelte/testing
+- title: TypeScript, use_cases: typescript setup, type safety, component props typing, generic components, wrapper components, dom type augmentation, project configuration, path: svelte/typescript
+- title: Custom elements, use_cases: web components, custom elements, component library, design system, framework-agnostic components, embedding svelte in non-svelte apps, shadow dom, path: svelte/custom-elements
+- title: Svelte 4 migration guide, use_cases: upgrading svelte 3 to 4, version migration, updating dependencies, breaking changes, legacy project maintenance, path: svelte/v4-migration-guide
+- title: Svelte 5 migration guide, use_cases: migrating from svelte 4 to 5, upgrading projects, learning svelte 5 syntax changes, runes migration, event handler updates, path: svelte/v5-migration-guide
+- title: Frequently asked questions, use_cases: getting started, learning svelte, beginner setup, project initialization, vs code setup, formatting, testing, routing, mobile apps, troubleshooting, community support, path: svelte/faq
+- title: svelte, use_cases: migration from svelte 4 to 5, upgrading legacy code, component lifecycle hooks, context api, mounting components, event dispatchers, typescript component types, path: svelte/svelte
+- title: svelte/action, use_cases: typescript types, actions, use directive, dom manipulation, element lifecycle, custom behaviors, third-party library integration, path: svelte/svelte-action
+- title: svelte/animate, use_cases: animated lists, sortable items, drag and drop, reordering elements, todo lists, kanban boards, playlist management, smooth position transitions, path: svelte/svelte-animate
+- title: svelte/attachments, use_cases: library development, component libraries, programmatic element manipulation, migrating from actions to attachments, spreading props onto elements, path: svelte/svelte-attachments
+- title: svelte/compiler, use_cases: build tools, custom compilers, ast manipulation, preprocessors, code transformation, migration scripts, syntax analysis, bundler plugins, dev tools, path: svelte/svelte-compiler
+- title: svelte/easing, use_cases: animations, transitions, custom easing, smooth motion, interactive ui, modals, dropdowns, carousels, page transitions, scroll effects, path: svelte/svelte-easing
+- title: svelte/events, use_cases: window events, document events, global event listeners, event delegation, programmatic event handling, cleanup functions, media queries, path: svelte/svelte-events
+- title: svelte/legacy, use_cases: migration from svelte 4 to svelte 5, upgrading legacy code, event modifiers, class components, imperative component instantiation, path: svelte/svelte-legacy
+- title: svelte/motion, use_cases: animation, smooth transitions, interactive ui, sliders, counters, physics-based motion, drag gestures, accessibility, reduced motion, path: svelte/svelte-motion
+- title: svelte/reactivity/window, use_cases: responsive design, viewport tracking, scroll effects, window resize handling, online/offline detection, zoom level tracking, path: svelte/svelte-reactivity-window
+- title: svelte/reactivity, use_cases: reactive data structures, state management with maps/sets, game boards, selection tracking, url manipulation, query params, real-time clocks, media queries, responsive design, path: svelte/svelte-reactivity
+- title: svelte/server, use_cases: server-side rendering, ssr, static site generation, seo optimization, initial page load, pre-rendering, node.js server, custom server setup, path: svelte/svelte-server
+- title: svelte/store, use_cases: state management, shared data, reactive stores, cross-component communication, global state, computed values, data synchronization, legacy svelte projects, path: svelte/svelte-store
+- title: svelte/transition, use_cases: animations, transitions, interactive ui, modals, dropdowns, tooltips, notifications, svg animations, list animations, page transitions, path: svelte/svelte-transition
+- title: Compiler errors, use_cases: animation, transitions, keyed each blocks, list animations, path: svelte/compiler-errors
+- title: Compiler warnings, use_cases: accessibility, a11y compliance, wcag standards, screen readers, keyboard navigation, aria attributes, semantic html, interactive elements, path: svelte/compiler-warnings
+- title: Runtime errors, use_cases: debugging errors, error handling, troubleshooting runtime issues, migration to svelte 5, component binding, effects and reactivity, path: svelte/runtime-errors
+- title: Runtime warnings, use_cases: debugging state proxies, console logging reactive values, inspecting state changes, development troubleshooting, path: svelte/runtime-warnings
+- title: Overview, use_cases: migrating from svelte 3/4 to svelte 5, maintaining legacy components, understanding deprecated features, gradual upgrade process, path: svelte/legacy-overview
+- title: Reactive let/var declarations, use_cases: migration, legacy svelte projects, upgrading from svelte 4, understanding old reactivity, maintaining existing code, learning runes differences, path: svelte/legacy-let
+- title: Reactive $: statements, use_cases: legacy mode, migration from svelte 4, reactive statements, computed values, derived state, side effects, path: svelte/legacy-reactive-assignments
+- title: export let, use_cases: legacy mode, migration from svelte 4, maintaining older projects, component props without runes, exporting component methods, renaming reserved word props, path: svelte/legacy-export-let
+- title: $$props and $$restProps, use_cases: legacy mode migration, component wrappers, prop forwarding, button components, reusable ui components, spreading props to child elements, path: svelte/legacy-$$props-and-$$restProps
+- title: on:, use_cases: legacy mode, event handling, button clicks, forms, user interactions, component communication, event forwarding, event modifiers, path: svelte/legacy-on
+- title: <slot>, use_cases: legacy mode, migrating from svelte 4, component composition, reusable components, passing content to components, modals, layouts, wrappers, path: svelte/legacy-slots
+- title: $$slots, use_cases: legacy mode, conditional slot rendering, optional content sections, checking if slots provided, migrating from legacy to runes, path: svelte/legacy-$$slots
+- title: <svelte:fragment>, use_cases: named slots, component composition, layout systems, avoiding wrapper divs, legacy svelte projects, slot content organization, path: svelte/legacy-svelte-fragment
+- title: <svelte:component>, use_cases: dynamic components, component switching, conditional rendering, legacy mode migration, tabbed interfaces, multi-step forms, path: svelte/legacy-svelte-component
+- title: <svelte:self>, use_cases: recursive components, tree structures, nested menus, file explorers, comment threads, hierarchical data, path: svelte/legacy-svelte-self
+- title: Imperative component API, use_cases: migration from svelte 3/4 to 5, legacy component api, maintaining old projects, understanding deprecated patterns, path: svelte/legacy-component-api
+
+</available-docs>
+
+These are the available documentation sections that `list-sections` will return, you do not need to call it again.
+
+Every time you write a Svelte component or a Svelte module you MUST invoke the `svelte-autofixer` tool providing the code. The tool will return a list of issues or suggestions. If there are any issues or suggestions you MUST fix them and call the tool again with the updated code. You MUST keep doing this until the tool returns no issues or suggestions. Only then you can return the code to the user.
+
+This is the task you will work on:
+
+<task>
+[YOUR TASK HERE]
+</task>
+
+If you are not writing the code into a file, once you have the final version of the code ask the user if it wants to generate a playground link to quickly check the code in it and if it answer yes call the `playground-link` tool and return the url to the user nicely formatted. The playground link MUST be generated only once you have the final version of the code and you are ready to share it, it MUST include an entry point file called `App.svelte` where the main component should live. If you have multiple files to include in the playground link you can include them all at the root.
+```
+
+</details>
--- a/documentation/docs/30-capabilities/30-prompts.md
+++ b/documentation/docs/30-capabilities/30-prompts.md
@@ -4,206 +4,4 @@ title: Prompts

 This is the list of available prompts provided by the MCP server. Prompts are selected by the user and are sent as a user message. They can be useful to write repetitive instructions for the LLM on how to properly use the MCP server.

-## svelte-task
-
-This prompt should be used whenever you are asking the model to work on a Svelte-related task. It will instruct the LLM which documentation sections are available, which tools to invoke, when to invoke them, and how to interpret the results.
-
-<details>
-	<summary>Copy the prompt</summary>
-
-```md
-You are a Svelte expert tasked to build components and utilities for Svelte developers. If you need documentation for anything related to Svelte you can invoke the tool `get-documentation` with one of the following paths. However: before invoking the `get-documentation` tool, try to answer the users query using your own knowledge and the `svelte-autofixer` tool. Be mindful of how many section you request, since it is token-intensive!
-<available-docs>
-
- title: Overview, use_cases: project setup, creating new svelte apps, scaffolding, cli tools, initializing projects, path: cli/overview
- title: Frequently asked questions, use_cases: project setup, initializing new svelte projects, troubleshooting cli installation, package manager configuration, path: cli/faq
- title: sv create, use_cases: project setup, starting new sveltekit app, initializing project, creating from playground, choosing project template, path: cli/sv-create
- title: sv add, use_cases: project setup, adding features to existing projects, integrating tools, testing setup, styling setup, authentication, database setup, deployment adapters, path: cli/sv-add
- title: sv check, use_cases: code quality, ci/cd pipelines, error checking, typescript projects, pre-commit hooks, finding unused css, accessibility auditing, production builds, path: cli/sv-check
- title: sv migrate, use_cases: migration, upgrading svelte versions, upgrading sveltekit versions, modernizing codebase, svelte 3 to 4, svelte 4 to 5, sveltekit 1 to 2, adopting runes, refactoring deprecated apis, path: cli/sv-migrate
- title: devtools-json, use_cases: development setup, chrome devtools integration, browser-based editing, local development workflow, debugging setup, path: cli/devtools-json
- title: drizzle, use_cases: database setup, sql queries, orm integration, data modeling, postgresql, mysql, sqlite, server-side data access, database migrations, type-safe queries, path: cli/drizzle
- title: eslint, use_cases: code quality, linting, error detection, project setup, code standards, team collaboration, typescript projects, path: cli/eslint
- title: lucia, use_cases: authentication, login systems, user management, registration pages, session handling, auth setup, path: cli/lucia
- title: mcp, use_cases: use title and path to estimate use case, path: cli/mcp
- title: mdsvex, use_cases: blog, content sites, markdown rendering, documentation sites, technical writing, cms integration, article pages, path: cli/mdsvex
- title: paraglide, use_cases: internationalization, multi-language sites, i18n, translation, localization, language switching, global apps, multilingual content, path: cli/paraglide
- title: playwright, use_cases: browser testing, e2e testing, integration testing, test automation, quality assurance, ci/cd pipelines, testing user flows, path: cli/playwright
- title: prettier, use_cases: code formatting, project setup, code style consistency, team collaboration, linting configuration, path: cli/prettier
- title: storybook, use_cases: component development, design systems, ui library, isolated component testing, documentation, visual testing, component showcase, path: cli/storybook
- title: sveltekit-adapter, use_cases: deployment, production builds, hosting setup, choosing deployment platform, configuring adapters, static site generation, node server, vercel, cloudflare, netlify, path: cli/sveltekit-adapter
- title: tailwindcss, use_cases: project setup, styling, css framework, rapid prototyping, utility-first css, design systems, responsive design, adding tailwind to svelte, path: cli/tailwind
- title: vitest, use_cases: testing, unit tests, component testing, test setup, quality assurance, ci/cd pipelines, test-driven development, path: cli/vitest
- title: Introduction, use_cases: learning sveltekit, project setup, understanding framework basics, choosing between svelte and sveltekit, getting started with full-stack apps, path: kit/introduction
- title: Creating a project, use_cases: project setup, starting new sveltekit app, initial development environment, first-time sveltekit users, scaffolding projects, path: kit/creating-a-project
- title: Project types, use_cases: deployment, project setup, choosing adapters, ssg, spa, ssr, serverless, mobile apps, desktop apps, pwa, offline apps, browser extensions, separate backend, docker containers, path: kit/project-types
- title: Project structure, use_cases: project setup, understanding file structure, organizing code, starting new project, learning sveltekit basics, path: kit/project-structure
- title: Web standards, use_cases: always, any sveltekit project, data fetching, forms, api routes, server-side rendering, deployment to various platforms, path: kit/web-standards
- title: Routing, use_cases: routing, navigation, multi-page apps, project setup, file structure, api endpoints, data loading, layouts, error pages, always, path: kit/routing
- title: Loading data, use_cases: data fetching, api calls, database queries, dynamic routes, page initialization, loading states, authentication checks, ssr data, form data, content rendering, path: kit/load
- title: Form actions, use_cases: forms, user input, data submission, authentication, login systems, user registration, progressive enhancement, validation errors, path: kit/form-actions
- title: Page options, use_cases: prerendering static sites, ssr configuration, spa setup, client-side rendering control, url trailing slash handling, adapter deployment config, build optimization, path: kit/page-options
- title: State management, use_cases: sveltekit, server-side rendering, ssr, state management, authentication, data persistence, load functions, context api, navigation, component lifecycle, path: kit/state-management
- title: Remote functions, use_cases: data fetching, server-side logic, database queries, type-safe client-server communication, forms, user input, mutations, authentication, crud operations, optimistic updates, path: kit/remote-functions
- title: Building your app, use_cases: production builds, deployment preparation, build process optimization, adapter configuration, preview before deployment, path: kit/building-your-app
- title: Adapters, use_cases: deployment, production builds, hosting setup, choosing deployment platform, configuring adapters, path: kit/adapters
- title: Zero-config deployments, use_cases: deployment, production builds, hosting setup, choosing deployment platform, ci/cd configuration, path: kit/adapter-auto
- title: Node servers, use_cases: deployment, production builds, node.js hosting, custom server setup, environment configuration, reverse proxy setup, docker deployment, systemd services, path: kit/adapter-node
- title: Static site generation, use_cases: static site generation, ssg, prerendering, deployment, github pages, spa mode, blogs, documentation sites, marketing sites, path: kit/adapter-static
- title: Single-page apps, use_cases: spa mode, single-page apps, client-only rendering, static hosting, mobile app wrappers, no server-side logic, adapter-static setup, fallback pages, path: kit/single-page-apps
- title: Cloudflare, use_cases: deployment, cloudflare workers, cloudflare pages, hosting setup, production builds, serverless deployment, edge computing, path: kit/adapter-cloudflare
- title: Cloudflare Workers, use_cases: deploying to cloudflare workers, cloudflare workers sites deployment, legacy cloudflare adapter, wrangler configuration, cloudflare platform bindings, path: kit/adapter-cloudflare-workers
- title: Netlify, use_cases: deployment, netlify hosting, production builds, serverless functions, edge functions, static site hosting, path: kit/adapter-netlify
- title: Vercel, use_cases: deployment, vercel hosting, production builds, serverless functions, edge functions, isr, image optimization, environment variables, path: kit/adapter-vercel
- title: Writing adapters, use_cases: custom deployment, building adapters, unsupported platforms, adapter development, custom hosting environments, path: kit/writing-adapters
- title: Advanced routing, use_cases: advanced routing, dynamic routes, file viewers, nested paths, custom 404 pages, url validation, route parameters, multi-level navigation, path: kit/advanced-routing
- title: Hooks, use_cases: authentication, logging, error tracking, request interception, api proxying, custom routing, internationalization, database initialization, middleware logic, session management, path: kit/hooks
- title: Errors, use_cases: error handling, custom error pages, 404 pages, api error responses, production error logging, error tracking, type-safe errors, path: kit/errors
- title: Link options, use_cases: routing, navigation, multi-page apps, performance optimization, link preloading, forms with get method, search functionality, focus management, scroll behavior, path: kit/link-options
- title: Service workers, use_cases: offline support, pwa, caching strategies, performance optimization, precaching assets, network resilience, progressive web apps, path: kit/service-workers
- title: Server-only modules, use_cases: api keys, environment variables, sensitive data protection, backend security, preventing data leaks, server-side code isolation, path: kit/server-only-modules
- title: Snapshots, use_cases: forms, user input, preserving form data, multi-step forms, navigation state, preventing data loss, textarea content, input fields, comment systems, surveys, path: kit/snapshots
- title: Shallow routing, use_cases: modals, dialogs, image galleries, overlays, history-driven ui, mobile-friendly navigation, photo viewers, lightboxes, drawer menus, path: kit/shallow-routing
- title: Observability, use_cases: performance monitoring, debugging, observability, tracing requests, production diagnostics, analyzing slow requests, finding bottlenecks, monitoring server-side operations, path: kit/observability
- title: Packaging, use_cases: building component libraries, publishing npm packages, creating reusable svelte components, library development, package distribution, path: kit/packaging
- title: Auth, use_cases: authentication, login systems, user management, session handling, jwt tokens, protected routes, user credentials, authorization checks, path: kit/auth
- title: Performance, use_cases: performance optimization, slow loading pages, production deployment, debugging performance issues, reducing bundle size, improving load times, path: kit/performance
- title: Icons, use_cases: icons, ui components, styling, css frameworks, tailwind, unocss, performance optimization, dependency management, path: kit/icons
- title: Images, use_cases: image optimization, responsive images, performance, hero images, product photos, galleries, cms integration, cdn setup, asset management, path: kit/images
- title: Accessibility, use_cases: always, any sveltekit project, screen reader support, keyboard navigation, multi-page apps, client-side routing, internationalization, multilingual sites, path: kit/accessibility
- title: SEO, use_cases: seo optimization, search engine ranking, content sites, blogs, marketing sites, public-facing apps, sitemaps, amp pages, meta tags, performance optimization, path: kit/seo
- title: Frequently asked questions, use_cases: troubleshooting package imports, library compatibility issues, client-side code execution, external api integration, middleware setup, database configuration, view transitions, yarn configuration, path: kit/faq
- title: Integrations, use_cases: project setup, css preprocessors, postcss, scss, sass, less, stylus, typescript setup, adding integrations, tailwind, testing, auth, linting, formatting, path: kit/integrations
- title: Breakpoint Debugging, use_cases: debugging, breakpoints, development workflow, troubleshooting issues, vscode setup, ide configuration, inspecting code execution, path: kit/debugging
- title: Migrating to SvelteKit v2, use_cases: migration, upgrading from sveltekit 1 to 2, breaking changes, version updates, path: kit/migrating-to-sveltekit-2
- title: Migrating from Sapper, use_cases: migrating from sapper, upgrading legacy projects, sapper to sveltekit conversion, project modernization, path: kit/migrating
- title: Additional resources, use_cases: troubleshooting, getting help, finding examples, learning sveltekit, project templates, common issues, community support, path: kit/additional-resources
- title: Glossary, use_cases: rendering strategies, performance optimization, deployment configuration, seo requirements, static sites, spas, server-side rendering, prerendering, edge deployment, pwa development, path: kit/glossary
- title: @sveltejs/kit, use_cases: forms, form actions, server-side validation, form submission, error handling, redirects, json responses, http errors, server utilities, path: kit/@sveltejs-kit
- title: @sveltejs/kit/hooks, use_cases: middleware, request processing, authentication chains, logging, multiple hooks, request/response transformation, path: kit/@sveltejs-kit-hooks
- title: @sveltejs/kit/node/polyfills, use_cases: node.js environments, custom servers, non-standard runtimes, ssr setup, web api compatibility, polyfill requirements, path: kit/@sveltejs-kit-node-polyfills
- title: @sveltejs/kit/node, use_cases: node.js adapter, custom server setup, http integration, streaming files, node deployment, server-side rendering with node, path: kit/@sveltejs-kit-node
- title: @sveltejs/kit/vite, use_cases: project setup, vite configuration, initial sveltekit setup, build tooling, path: kit/@sveltejs-kit-vite
- title: $app/environment, use_cases: always, conditional logic, client-side code, server-side code, build-time logic, prerendering, development vs production, environment detection, path: kit/$app-environment
- title: $app/forms, use_cases: forms, user input, data submission, progressive enhancement, custom form handling, form validation, path: kit/$app-forms
- title: $app/navigation, use_cases: routing, navigation, multi-page apps, programmatic navigation, data reloading, preloading, shallow routing, navigation lifecycle, scroll handling, view transitions, path: kit/$app-navigation
- title: $app/paths, use_cases: static assets, images, fonts, public files, base path configuration, subdirectory deployment, cdn setup, asset urls, links, navigation, path: kit/$app-paths
- title: $app/server, use_cases: remote functions, server-side logic, data fetching, form handling, api endpoints, client-server communication, prerendering, file reading, batch queries, path: kit/$app-server
- title: $app/state, use_cases: routing, navigation, multi-page apps, loading states, url parameters, form handling, error states, version updates, page metadata, shallow routing, path: kit/$app-state
- title: $app/stores, use_cases: legacy projects, sveltekit pre-2.12, migration from stores to runes, maintaining older codebases, accessing page data, navigation state, app version updates, path: kit/$app-stores
- title: $app/types, use_cases: routing, navigation, type safety, route parameters, dynamic routes, link generation, pathname validation, multi-page apps, path: kit/$app-types
- title: $env/dynamic/private, use_cases: api keys, secrets management, server-side config, environment variables, backend logic, deployment-specific settings, private data handling, path: kit/$env-dynamic-private
- title: $env/dynamic/public, use_cases: environment variables, client-side config, runtime configuration, public api keys, deployment-specific settings, multi-environment apps, path: kit/$env-dynamic-public
- title: $env/static/private, use_cases: server-side api keys, backend secrets, database credentials, private configuration, build-time optimization, server endpoints, authentication tokens, path: kit/$env-static-private
- title: $env/static/public, use_cases: environment variables, public config, client-side data, api endpoints, build-time configuration, public constants, path: kit/$env-static-public
- title: $lib, use_cases: project setup, component organization, importing shared components, reusable ui elements, code structure, path: kit/$lib
- title: $service-worker, use_cases: offline support, pwa, service workers, caching strategies, progressive web apps, offline-first apps, path: kit/$service-worker
- title: Configuration, use_cases: project setup, configuration, adapters, deployment, build settings, environment variables, routing customization, prerendering, csp security, csrf protection, path configuration, typescript setup, path: kit/configuration
- title: Command Line Interface, use_cases: project setup, typescript configuration, generated types, ./$types imports, initial project configuration, path: kit/cli
- title: Types, use_cases: typescript, type safety, route parameters, api endpoints, load functions, form actions, generated types, jsconfig setup, path: kit/types
- title: Overview, use_cases: use title and path to estimate use case, path: mcp/overview
- title: Local setup, use_cases: use title and path to estimate use case, path: mcp/local-setup
- title: Remote setup, use_cases: use title and path to estimate use case, path: mcp/remote-setup
- title: Tools, use_cases: use title and path to estimate use case, path: mcp/tools
- title: Resources, use_cases: use title and path to estimate use case, path: mcp/resources
- title: Prompts, use_cases: use title and path to estimate use case, path: mcp/prompts
- title: Overview, use_cases: always, any svelte project, getting started, learning svelte, introduction, project setup, understanding framework basics, path: svelte/overview
- title: Getting started, use_cases: project setup, starting new svelte project, initial installation, choosing between sveltekit and vite, editor configuration, path: svelte/getting-started
- title: .svelte files, use_cases: always, any svelte project, component creation, project setup, learning svelte basics, path: svelte/svelte-files
- title: .svelte.js and .svelte.ts files, use_cases: shared reactive state, reusable reactive logic, state management across components, global stores, custom reactive utilities, path: svelte/svelte-js-files
- title: What are runes?, use_cases: always, any svelte 5 project, understanding core syntax, learning svelte 5, migration from svelte 4, path: svelte/what-are-runes
- title: $state, use_cases: always, any svelte project, core reactivity, state management, counters, forms, todo apps, interactive ui, data updates, class-based components, path: svelte/$state
- title: $derived, use_cases: always, any svelte project, computed values, reactive calculations, derived data, transforming state, dependent values, path: svelte/$derived
- title: $effect, use_cases: canvas drawing, third-party library integration, dom manipulation, side effects, intervals, timers, network requests, analytics tracking, path: svelte/$effect
- title: $props, use_cases: always, any svelte project, passing data to components, component communication, reusable components, component props, path: svelte/$props
- title: $bindable, use_cases: forms, user input, two-way data binding, custom input components, parent-child communication, reusable form fields, path: svelte/$bindable
- title: $inspect, use_cases: debugging, development, tracking state changes, reactive state monitoring, troubleshooting reactivity issues, path: svelte/$inspect
- title: $host, use_cases: custom elements, web components, dispatching custom events, component library, framework-agnostic components, path: svelte/$host
- title: Basic markup, use_cases: always, any svelte project, basic markup, html templating, component structure, attributes, events, props, text rendering, path: svelte/basic-markup
- title: {#if ...}, use_cases: always, conditional rendering, showing/hiding content, dynamic ui, user permissions, loading states, error handling, form validation, path: svelte/if
- title: {#each ...}, use_cases: always, lists, arrays, iteration, product listings, todos, tables, grids, dynamic content, shopping carts, user lists, comments, feeds, path: svelte/each
- title: {#key ...}, use_cases: animations, transitions, component reinitialization, forcing component remount, value-based ui updates, resetting component state, path: svelte/key
- title: {#await ...}, use_cases: async data fetching, api calls, loading states, promises, error handling, lazy loading components, dynamic imports, path: svelte/await
- title: {#snippet ...}, use_cases: reusable markup, component composition, passing content to components, table rows, list items, conditional rendering, reducing duplication, path: svelte/snippet
- title: {@render ...}, use_cases: reusable ui patterns, component composition, conditional rendering, fallback content, layout components, slot alternatives, template reuse, path: svelte/@render
- title: {@html ...}, use_cases: rendering html strings, cms content, rich text editors, markdown to html, blog posts, wysiwyg output, sanitized html injection, dynamic html content, path: svelte/@html
- title: {@attach ...}, use_cases: tooltips, popovers, dom manipulation, third-party libraries, canvas drawing, element lifecycle, interactive ui, custom directives, wrapper components, path: svelte/@attach
- title: {@const ...}, use_cases: computed values in loops, derived calculations in blocks, local variables in each iterations, complex list rendering, path: svelte/@const
- title: {@debug ...}, use_cases: debugging, development, troubleshooting, tracking state changes, monitoring variables, reactive data inspection, path: svelte/@debug
- title: bind:, use_cases: forms, user input, two-way data binding, interactive ui, media players, file uploads, checkboxes, radio buttons, select dropdowns, contenteditable, dimension tracking, path: svelte/bind
- title: use:, use_cases: custom directives, dom manipulation, third-party library integration, tooltips, click outside, gestures, focus management, element lifecycle hooks, path: svelte/use
- title: transition:, use_cases: animations, interactive ui, modals, dropdowns, notifications, conditional content, show/hide elements, smooth state changes, path: svelte/transition
- title: in: and out:, use_cases: animation, transitions, interactive ui, conditional rendering, independent enter/exit effects, modals, tooltips, notifications, path: svelte/in-and-out
- title: animate:, use_cases: sortable lists, drag and drop, reorderable items, todo lists, kanban boards, playlist editors, priority queues, animated list reordering, path: svelte/animate
- title: style:, use_cases: dynamic styling, conditional styles, theming, dark mode, responsive design, interactive ui, component styling, path: svelte/style
- title: class, use_cases: always, conditional styling, dynamic classes, tailwind css, component styling, reusable components, responsive design, path: svelte/class
- title: await, use_cases: async data fetching, loading states, server-side rendering, awaiting promises in components, async validation, concurrent data loading, path: svelte/await-expressions
- title: Scoped styles, use_cases: always, styling components, scoped css, component-specific styles, preventing style conflicts, animations, keyframes, path: svelte/scoped-styles
- title: Global styles, use_cases: global styles, third-party libraries, css resets, animations, styling body/html, overriding component styles, shared keyframes, base styles, path: svelte/global-styles
- title: Custom properties, use_cases: theming, custom styling, reusable components, design systems, dynamic colors, component libraries, ui customization, path: svelte/custom-properties
- title: Nested <style> elements, use_cases: component styling, scoped styles, dynamic styles, conditional styling, nested style tags, custom styling logic, path: svelte/nested-style-elements
- title: <svelte:boundary>, use_cases: error handling, async data loading, loading states, error recovery, flaky components, error reporting, resilient ui, path: svelte/svelte-boundary
- title: <svelte:window>, use_cases: keyboard shortcuts, scroll tracking, window resize handling, responsive layouts, online/offline detection, viewport dimensions, global event listeners, path: svelte/svelte-window
- title: <svelte:document>, use_cases: document events, visibility tracking, fullscreen detection, pointer lock, focus management, document-level interactions, path: svelte/svelte-document
- title: <svelte:body>, use_cases: mouse tracking, hover effects, cursor interactions, global body events, drag and drop, custom cursors, interactive backgrounds, body-level actions, path: svelte/svelte-body
- title: <svelte:head>, use_cases: seo optimization, page titles, meta tags, social media sharing, dynamic head content, multi-page apps, blog posts, product pages, path: svelte/svelte-head
- title: <svelte:element>, use_cases: dynamic content, cms integration, user-generated content, configurable ui, runtime element selection, flexible components, path: svelte/svelte-element
- title: <svelte:options>, use_cases: migration, custom elements, web components, legacy mode compatibility, runes mode setup, svg components, mathml components, css injection control, path: svelte/svelte-options
- title: Stores, use_cases: shared state, cross-component data, reactive values, async data streams, manual control over updates, rxjs integration, extracting logic, path: svelte/stores
- title: Context, use_cases: shared state, avoiding prop drilling, component communication, theme providers, user context, authentication state, configuration sharing, deeply nested components, path: svelte/context
- title: Lifecycle hooks, use_cases: component initialization, cleanup tasks, timers, subscriptions, dom measurements, chat windows, autoscroll features, migration from svelte 4, path: svelte/lifecycle-hooks
- title: Imperative component API, use_cases: project setup, client-side rendering, server-side rendering, ssr, hydration, testing, programmatic component creation, tooltips, dynamic mounting, path: svelte/imperative-component-api
- title: Hydratable data, use_cases: use title and path to estimate use case, path: svelte/hydratable
- title: Testing, use_cases: testing, quality assurance, unit tests, integration tests, component tests, e2e tests, vitest setup, playwright setup, test automation, path: svelte/testing
- title: TypeScript, use_cases: typescript setup, type safety, component props typing, generic components, wrapper components, dom type augmentation, project configuration, path: svelte/typescript
- title: Custom elements, use_cases: web components, custom elements, component library, design system, framework-agnostic components, embedding svelte in non-svelte apps, shadow dom, path: svelte/custom-elements
- title: Svelte 4 migration guide, use_cases: upgrading svelte 3 to 4, version migration, updating dependencies, breaking changes, legacy project maintenance, path: svelte/v4-migration-guide
- title: Svelte 5 migration guide, use_cases: migrating from svelte 4 to 5, upgrading projects, learning svelte 5 syntax changes, runes migration, event handler updates, path: svelte/v5-migration-guide
- title: Frequently asked questions, use_cases: getting started, learning svelte, beginner setup, project initialization, vs code setup, formatting, testing, routing, mobile apps, troubleshooting, community support, path: svelte/faq
- title: svelte, use_cases: migration from svelte 4 to 5, upgrading legacy code, component lifecycle hooks, context api, mounting components, event dispatchers, typescript component types, path: svelte/svelte
- title: svelte/action, use_cases: typescript types, actions, use directive, dom manipulation, element lifecycle, custom behaviors, third-party library integration, path: svelte/svelte-action
- title: svelte/animate, use_cases: animated lists, sortable items, drag and drop, reordering elements, todo lists, kanban boards, playlist management, smooth position transitions, path: svelte/svelte-animate
- title: svelte/attachments, use_cases: library development, component libraries, programmatic element manipulation, migrating from actions to attachments, spreading props onto elements, path: svelte/svelte-attachments
- title: svelte/compiler, use_cases: build tools, custom compilers, ast manipulation, preprocessors, code transformation, migration scripts, syntax analysis, bundler plugins, dev tools, path: svelte/svelte-compiler
- title: svelte/easing, use_cases: animations, transitions, custom easing, smooth motion, interactive ui, modals, dropdowns, carousels, page transitions, scroll effects, path: svelte/svelte-easing
- title: svelte/events, use_cases: window events, document events, global event listeners, event delegation, programmatic event handling, cleanup functions, media queries, path: svelte/svelte-events
- title: svelte/legacy, use_cases: migration from svelte 4 to svelte 5, upgrading legacy code, event modifiers, class components, imperative component instantiation, path: svelte/svelte-legacy
- title: svelte/motion, use_cases: animation, smooth transitions, interactive ui, sliders, counters, physics-based motion, drag gestures, accessibility, reduced motion, path: svelte/svelte-motion
- title: svelte/reactivity/window, use_cases: responsive design, viewport tracking, scroll effects, window resize handling, online/offline detection, zoom level tracking, path: svelte/svelte-reactivity-window
- title: svelte/reactivity, use_cases: reactive data structures, state management with maps/sets, game boards, selection tracking, url manipulation, query params, real-time clocks, media queries, responsive design, path: svelte/svelte-reactivity
- title: svelte/server, use_cases: server-side rendering, ssr, static site generation, seo optimization, initial page load, pre-rendering, node.js server, custom server setup, path: svelte/svelte-server
- title: svelte/store, use_cases: state management, shared data, reactive stores, cross-component communication, global state, computed values, data synchronization, legacy svelte projects, path: svelte/svelte-store
- title: svelte/transition, use_cases: animations, transitions, interactive ui, modals, dropdowns, tooltips, notifications, svg animations, list animations, page transitions, path: svelte/svelte-transition
- title: Compiler errors, use_cases: animation, transitions, keyed each blocks, list animations, path: svelte/compiler-errors
- title: Compiler warnings, use_cases: accessibility, a11y compliance, wcag standards, screen readers, keyboard navigation, aria attributes, semantic html, interactive elements, path: svelte/compiler-warnings
- title: Runtime errors, use_cases: debugging errors, error handling, troubleshooting runtime issues, migration to svelte 5, component binding, effects and reactivity, path: svelte/runtime-errors
- title: Runtime warnings, use_cases: debugging state proxies, console logging reactive values, inspecting state changes, development troubleshooting, path: svelte/runtime-warnings
- title: Overview, use_cases: migrating from svelte 3/4 to svelte 5, maintaining legacy components, understanding deprecated features, gradual upgrade process, path: svelte/legacy-overview
- title: Reactive let/var declarations, use_cases: migration, legacy svelte projects, upgrading from svelte 4, understanding old reactivity, maintaining existing code, learning runes differences, path: svelte/legacy-let
- title: Reactive $: statements, use_cases: legacy mode, migration from svelte 4, reactive statements, computed values, derived state, side effects, path: svelte/legacy-reactive-assignments
- title: export let, use_cases: legacy mode, migration from svelte 4, maintaining older projects, component props without runes, exporting component methods, renaming reserved word props, path: svelte/legacy-export-let
- title: $$props and $$restProps, use_cases: legacy mode migration, component wrappers, prop forwarding, button components, reusable ui components, spreading props to child elements, path: svelte/legacy-$$props-and-$$restProps
- title: on:, use_cases: legacy mode, event handling, button clicks, forms, user interactions, component communication, event forwarding, event modifiers, path: svelte/legacy-on
- title: <slot>, use_cases: legacy mode, migrating from svelte 4, component composition, reusable components, passing content to components, modals, layouts, wrappers, path: svelte/legacy-slots
- title: $$slots, use_cases: legacy mode, conditional slot rendering, optional content sections, checking if slots provided, migrating from legacy to runes, path: svelte/legacy-$$slots
- title: <svelte:fragment>, use_cases: named slots, component composition, layout systems, avoiding wrapper divs, legacy svelte projects, slot content organization, path: svelte/legacy-svelte-fragment
- title: <svelte:component>, use_cases: dynamic components, component switching, conditional rendering, legacy mode migration, tabbed interfaces, multi-step forms, path: svelte/legacy-svelte-component
- title: <svelte:self>, use_cases: recursive components, tree structures, nested menus, file explorers, comment threads, hierarchical data, path: svelte/legacy-svelte-self
- title: Imperative component API, use_cases: migration from svelte 3/4 to 5, legacy component api, maintaining old projects, understanding deprecated patterns, path: svelte/legacy-component-api
-
-</available-docs>
-
-These are the available documentation sections that `list-sections` will return, you do not need to call it again.
-
-Every time you write a Svelte component or a Svelte module you MUST invoke the `svelte-autofixer` tool providing the code. The tool will return a list of issues or suggestions. If there are any issues or suggestions you MUST fix them and call the tool again with the updated code. You MUST keep doing this until the tool returns no issues or suggestions. Only then you can return the code to the user.
-
-This is the task you will work on:
-
-<task>
-[YOUR TASK HERE]
-</task>
-
-If you are not writing the code into a file, once you have the final version of the code ask the user if it wants to generate a playground link to quickly check the code in it and if it answer yes call the `playground-link` tool and return the url to the user nicely formatted. The playground link MUST be generated only once you have the final version of the code and you are ready to share it, it MUST include an entry point file called `App.svelte` where the main component should live. If you have multiple files to include in the playground link you can include them all at the root.
-```
-
-</details>
+@include .generated/prompts.md
--- a/documentation/docs/40-claude-plugin/index.md
+++ b/documentation/docs/40-claude-plugin/index.md
@@ -0,0 +1,3 @@
+---
+title: Claude Code Plugin
+---
--- a/documentation/docs/40-claude-plugin/plugin.md
+++ b/documentation/docs/40-claude-plugin/plugin.md
@@ -0,0 +1,23 @@
+---
+title: Overview
+---
+
+The open source [repository](https://github.com/sveltejs/ai-tools) containing the code for the MCP server is also a Claude Code Marketplace plugin.
+
+The marketplace allows you to install the `svelte` plugin which will give you the remote MCP server, [skills](skills) to instruct the LLM on how to properly write Svelte 5 code, and a specialized agent for editing Svelte files.
+
+If possible, we recommend that you instruct the LLM to execute MCP calls with the agent (you can explicitly mention an agent in your message to delegate work to it) when creating or editing `.svelte` files or `.svelte.ts`/`.svelte.js` modules as it helps save context by handling Svelte-specific tasks more efficiently.
+
+## Installation
+
+To add the repository as a marketplace, launch Claude Code and type the following:
+
+```bash
+/plugin marketplace add sveltejs/ai-tools
+```
+
+Then, install the Svelte plugin:
+
+```bash
+/plugin install svelte
+```
--- a/documentation/docs/40-claude-plugin/subagent.md
+++ b/documentation/docs/40-claude-plugin/subagent.md
@@ -0,0 +1,11 @@
+---
+title: Subagent
+---
+
+The Svelte plugin includes a specialized subagent called `svelte-file-editor` designed for creating, editing, and reviewing Svelte files.
+
+## Benefits
+
+The subagent has access to its own context window, allowing it to fetch the documentation, iterate with the `svelte-autofixer` tool and write to the file system without wasting context in the main agent.
+
+The delegation should happen automatically when appropriate, but you can also explicitly request the subagent be used for Svelte-related tasks.
--- a/documentation/docs/50-opencode-plugin/index.md
+++ b/documentation/docs/50-opencode-plugin/index.md
@@ -0,0 +1,3 @@
+---
+title: OpenCode Plugin
+---
--- a/documentation/docs/50-opencode-plugin/opencode-plugin.md
+++ b/documentation/docs/50-opencode-plugin/opencode-plugin.md
@@ -0,0 +1,45 @@
+---
+title: Overview
+---
+
+OpenCode has a [plugin system](https://opencode.ai/docs/plugins/) that allows developers to add MCP servers, agents and commands programmatically. Svelte has an OpenCode plugin published under `@sveltejs/opencode`.
+
+## Installation
+
+To install the plugin in OpenCode you can edit your [OpenCode config]() (either the global or the local one), adding `@sveltejs/opencode` to the list of plugins.
+
+```json
+{
+	"$schema": "https://opencode.ai/config.json",
+	"plugin": ["@sveltejs/opencode"]
+}
+```
+
+That's it! You now have the Svelte MCP server, [skills](skills), and the [file editor subagent](opencode-subagent) configured for you.
+
+## Configuration
+
+The default configuration for the Svelte OpenCode plugin looks like this...
+
+```json
+{
+	"$schema": "https://raw.githubusercontent.com/sveltejs/ai-tools/refs/heads/main/packages/opencode/schema.json",
+	"mcp": {
+		"type": "remote",
+		"enabled": true
+	},
+	"subagent": {
+		"enabled": true
+	},
+	"skills": {
+		"enabled": true
+	},
+	"instructions": {
+		"enabled": true
+	}
+}
+```
+
+...but if you prefer, you can enable only the subagent, only the MCP, only the skills, or configure the kind of MCP server you want to use (`local` or `remote`).
+
+You can place this file in `./.opencode/svelte.json` (in your project), in `~/.config/opencode/svelte.json` or, if you have an `OPENCODE_CONFIG_DIR` environment variable specified, at `$OPENCODE_CONFIG_DIR/svelte.json`.
--- a/documentation/docs/50-opencode-plugin/opencode-subagent.md
+++ b/documentation/docs/50-opencode-plugin/opencode-subagent.md
@@ -0,0 +1,11 @@
+---
+title: Subagent
+---
+
+The Svelte plugin includes a specialized subagent called `svelte-file-editor` designed for creating, editing, and reviewing Svelte files.
+
+## Benefits
+
+The subagent has access to its own context window, allowing it to fetch the documentation, iterate with the `svelte-autofixer` tool and write to the file system without wasting context in the main agent.
+
+The delegation should happen automatically when appropriate, but you can also explicitly request the subagent be used for Svelte-related tasks.
--- a/documentation/docs/60-skills/.generated/skills.md
+++ b/documentation/docs/60-skills/.generated/skills.md
@@ -0,0 +1,76 @@
+## `svelte-code-writer`
+
+CLI tools for Svelte 5 documentation lookup and code analysis. MUST be used whenever creating, editing or analyzing any Svelte component (.svelte) or Svelte module (.svelte.ts/.svelte.js). If possible, this skill should be executed within the svelte-file-editor agent for optimal results.
+
+<a href="https://github.com/sveltejs/ai-tools/releases?q=svelte-code-writer" target="_blank" rel="noopener noreferrer">Open Releases page</a>
+
+<details>
+	<summary>View skill content</summary>
+
+<!-- prettier-ignore-start -->
+````markdown
+# Svelte 5 Code Writer
+
+## CLI Tools
+
+You have access to `@sveltejs/mcp` CLI for Svelte-specific assistance. Use these commands via `npx`:
+
+### List Documentation Sections
+
+```bash
+npx @sveltejs/mcp list-sections
+```
+
+Lists all available Svelte 5 and SvelteKit documentation sections with titles and paths.
+
+### Get Documentation
+
+```bash
+npx @sveltejs/mcp get-documentation "<section1>,<section2>,..."
+```
+
+Retrieves full documentation for specified sections. Use after `list-sections` to fetch relevant docs.
+
+**Example:**
+
+```bash
+npx @sveltejs/mcp get-documentation "$state,$derived,$effect"
+```
+
+### Svelte Autofixer
+
+```bash
+npx @sveltejs/mcp svelte-autofixer "<code_or_path>" [options]
+```
+
+Analyzes Svelte code and suggests fixes for common issues.
+
+**Options:**
+
+- `--async` - Enable async Svelte mode (default: false)
+- `--svelte-version` - Target version: 4 or 5 (default: 5)
+
+**Examples:**
+
+```bash
+# Analyze inline code (escape $ as \$)
+npx @sveltejs/mcp svelte-autofixer '<script>let count = \$state(0);</script>'
+
+# Analyze a file
+npx @sveltejs/mcp svelte-autofixer ./src/lib/Component.svelte
+
+# Target Svelte 4
+npx @sveltejs/mcp svelte-autofixer ./Component.svelte --svelte-version 4
+```
+
+**Important:** When passing code with runes (`$state`, `$derived`, etc.) via the terminal, escape the `$` character as `\$` to prevent shell variable substitution.
+
+## Workflow
+
+1. **Uncertain about syntax?** Run `list-sections` then `get-documentation` for relevant topics
+2. **Reviewing/debugging?** Run `svelte-autofixer` on the code to detect issues
+3. **Always validate** - Run `svelte-autofixer` before finalizing any Svelte component
+````
+<!-- prettier-ignore-end -->
+
+</details>
--- a/documentation/docs/60-skills/10-skills.md
+++ b/documentation/docs/60-skills/10-skills.md
@@ -0,0 +1,11 @@
+---
+title: Overview
+---
+
+This is the list of available skills provided by the Svelte MCP package. Skills are sets of instructions that AI agents can load on-demand to help with specific tasks.
+
+Skills are available in both the Claude Code plugin (installed via the marketplace) and the OpenCode plugin (`@sveltejs/opencode`). They can also be manually installed in your `.claude/skills/` or `.opencode/skills/` folder.
+
+You can download the latest skills from the [releases page](https://github.com/sveltejs/ai-tools/releases) or find them in the [`plugins/svelte/skills`](https://github.com/sveltejs/ai-tools/tree/main/plugins/svelte/skills) folder.
+
+@include .generated/skills.md
--- a/documentation/docs/60-skills/index.md
+++ b/documentation/docs/60-skills/index.md
@@ -0,0 +1,3 @@
+---
+title: Skills
+---
--- a/documentation/docs/index.md
+++ b/documentation/docs/index.md
@@ -1,3 +1,3 @@
 ---
-title: MCP
+title: AI
 ---
--- a/instructions/AGENTS.md
+++ b/instructions/AGENTS.md
@@ -0,0 +1,23 @@
+You are able to use the Svelte MCP server, where you have access to comprehensive Svelte 5 and SvelteKit documentation. Here's how to use the available tools effectively:
+
+## Available Svelte MCP Tools:
+
+### 1. list-sections
+
+Use this FIRST to discover all available documentation sections. Returns a structured list with titles, use_cases, and paths.
+When asked about Svelte or SvelteKit topics, ALWAYS use this tool at the start of the chat to find relevant sections.
+
+### 2. get-documentation
+
+Retrieves full documentation content for specific sections. Accepts single or multiple sections.
+After calling the list-sections tool, you MUST analyze the returned documentation sections (especially the use_cases field) and then use the get-documentation tool to fetch ALL documentation sections that are relevant for the user's task.
+
+### 3. svelte-autofixer
+
+Analyzes Svelte code and returns issues and suggestions.
+You MUST use this tool whenever writing Svelte code before sending it to the user. Keep calling it until no issues or suggestions are returned.
+
+### 4. playground-link
+
+Generates a Svelte Playground link with the provided code.
+After completing the code, ask the user if they want a playground link. Only call this tool after user confirmation and NEVER if code was written to files in their project.
--- a/package.json
+++ b/package.json
@@ -3,7 +3,7 @@
 	"version": "0.0.1",
 	"description": "The official Svelte MCP server implementation",
 	"type": "module",
-	"packageManager": "pnpm@10.26.1",
+	"packageManager": "pnpm@10.28.2",
 	"scripts": {
 		"build": "pnpm -r run build",
 		"dev": "pnpm --filter @sveltejs/mcp-remote run dev",
@@ -18,11 +18,16 @@
 		"test": "npm run test:unit -- --run",
 		"test:watch": "npm run test:unit -- --watch",
 		"inspect": "pnpm mcp-inspector",
+		"generate-opencode-jsonschema": "pnpm --filter @sveltejs/opencode run generate-schema",
 		"generate-summaries": "pnpm --filter @sveltejs/mcp-server run generate-summaries",
 		"generate-prompt-docs": "node --import node-resolve-ts/register scripts/update-docs-prompts.ts",
+		"generate-skill-docs": "node --import node-resolve-ts/register scripts/update-docs-skills.ts",
 		"debug:generate-summaries": "pnpm --filter @sveltejs/mcp-server run debug:generate-summaries",
 		"release": "pnpm --filter @sveltejs/mcp run build && changeset publish",
-		"changeset:version": "changeset version && pnpm --filter @sveltejs/mcp run update:version && git add --all"
+		"changeset:version": "changeset version && pnpm --filter @sveltejs/mcp run update:version && git add --all",
+		"sync-opencode-skills": "rm -rf packages/opencode/skills && cp -r plugins/svelte/skills packages/opencode/skills",
+		"sync-agents-md": "rm -f packages/opencode/instructions/opencode-agents.md && rm -f documentation/docs/10-introduction/.generated/agents.md && mkdir -p packages/opencode/instructions && mkdir -p documentation/docs/10-introduction/.generated && cp instructions/AGENTS.md packages/opencode/instructions/opencode-agents.md && cp instructions/AGENTS.md documentation/docs/10-introduction/.generated/agents.md",
+		"sync-cursor-plugin": "node scripts/sync-cursor-plugin.ts"
 	},
 	"keywords": [
 		"svelte",
--- a/packages/mcp-server/package.json
+++ b/packages/mcp-server/package.json
@@ -14,7 +14,8 @@
 		"debug:generate-summaries": "DEBUG_MODE=1 node scripts/generate-summaries.ts --experimental-strip-types"
 	},
 	"exports": {
-		".": "./src/index.ts"
+		".": "./src/index.ts",
+		"./handlers": "./src/mcp/handlers/tools/handlers.ts"
 	},
 	"peerDependencies": {
 		"drizzle-orm": "^0.45.0"
--- a/packages/mcp-server/src/mcp/autofixers/add-eslint-issues.ts
+++ b/packages/mcp-server/src/mcp/autofixers/add-eslint-issues.ts
@@ -35,6 +35,7 @@ function base_config(svelte_config: Config): ESLint.Options['baseConfig'] {
 				'svelte/prefer-writable-derived': 'warn',
 				'svelte/require-event-dispatcher-types': 'warn',
 				'svelte/require-store-reactive-access': 'warn',
+				'svelte/no-inspect': 'off',
 			},

 			languageOptions: {
--- a/packages/mcp-server/src/mcp/handlers/tools/get-documentation.ts
+++ b/packages/mcp-server/src/mcp/handlers/tools/get-documentation.ts
@@ -5,110 +5,137 @@ import { SECTIONS_LIST_INTRO, SECTIONS_LIST_OUTRO } from './prompts.js';
 import { icons } from '../../icons/index.js';
 import { tool } from 'tmcp/utils';

+const get_documentation_schema = v.object({
+	section: v.pipe(
+		v.union([v.string(), v.array(v.string())]),
+		v.description(
+			'The section name(s) to retrieve. Can search by title (e.g., "$state", "load functions") or file path (e.g., "cli/overview"). Supports single string and array of strings',
+		),
+	),
+});
+
+export async function get_documentation_handler({
+	section,
+}: v.InferInput<typeof get_documentation_schema>) {
+	let sections: string[];
+
+	if (Array.isArray(section)) {
+		sections = section.filter((s): s is string => typeof s === 'string');
+	} else if (
+		typeof section === 'string' &&
+		section.trim().startsWith('[') &&
+		section.trim().endsWith(']')
+	) {
+		try {
+			const parsed = JSON.parse(section);
+			if (Array.isArray(parsed)) {
+				sections = parsed.filter((s): s is string => typeof s === 'string');
+			} else {
+				sections = [section];
+			}
+		} catch {
+			sections = [section];
+		}
+	} else if (typeof section === 'string') {
+		sections = [section];
+	} else {
+		sections = [];
+	}
+
+	const available_sections = await get_sections();
+
+	const settled_results = await Promise.allSettled(
+		sections.map(async (requested_section) => {
+			const matched_section = available_sections.find(
+				(s) =>
+					s.title.toLowerCase() === requested_section.toLowerCase() ||
+					s.slug === requested_section ||
+					s.url === requested_section,
+			);
+
+			if (matched_section) {
+				try {
+					const response = await fetch_with_timeout(matched_section.url);
+					if (response.ok) {
+						const content = await response.text();
+						return { success: true, content: `## ${matched_section.title}\n\n${content}` };
+					} else {
+						return {
+							success: false,
+							content: `## ${matched_section.title}\n\nError: Could not fetch documentation (HTTP ${response.status})`,
+						};
+					}
+				} catch (error) {
+					return {
+						success: false,
+						content: `## ${matched_section.title}\n\nError: Failed to fetch documentation - ${error}`,
+					};
+				}
+			} else {
+				return {
+					success: false,
+					content: `## ${requested_section}\n\nError: Section not found.`,
+				};
+			}
+		}),
+	);
+
+	const results = settled_results.map((result) => {
+		if (result.status === 'fulfilled') {
+			return result.value;
+		} else {
+			return {
+				success: false,
+				content: `Error: Couldn't fetch - ${result.reason}`,
+			};
+		}
+	});
+
+	const has_any_success = results.some((result) => result.success);
+	let final_text = results.map((r) => r.content).join('\n\n---\n\n');
+
+	if (!has_any_success) {
+		const formatted_sections = await format_sections_list();
+
+		final_text += `\n\n---\n\n${SECTIONS_LIST_INTRO}\n\n${formatted_sections}\n\n${SECTIONS_LIST_OUTRO}`;
+	}
+
+	return final_text;
+}
+
 export function get_documentation(server: SvelteMcp) {
 	server.tool(
 		{
 			name: 'get-documentation',
 			description:
 				'Retrieves full documentation content for Svelte 5 or SvelteKit sections. Supports flexible search by title (e.g., "$state", "routing") or file path (e.g., "cli/overview"). Can accept a single section name or an array of sections. Before running this, make sure to analyze the users query, as well as the output from list-sections (which should be called first). Then ask for ALL relevant sections the user might require. For example, if the user asks to build anything interactive, you will need to fetch all relevant runes, and so on. Before calling this tool, try to implement Svelte components using your own knowledge and the `svelte-autofixer` tool, since calling this tool is token intensive.',
-			schema: v.object({
-				section: v.pipe(
-					v.union([v.string(), v.array(v.string())]),
-					v.description(
-						'The section name(s) to retrieve. Can search by title (e.g., "$state", "load functions") or file path (e.g., "cli/overview"). Supports single string and array of strings',
-					),
-				),
-			}),
+			schema: get_documentation_schema,
+			annotations: {
+				title: 'Get Documentation',
+				destructiveHint: false,
+				readOnlyHint: true,
+				openWorldHint: false,
+			},
 			icons,
 		},
 		async ({ section }) => {
 			if (server.ctx.sessionId && server.ctx.custom?.track) {
 				await server.ctx.custom?.track?.(server.ctx.sessionId, 'get-documentation');
 			}
-			let sections: string[];
-
-			if (Array.isArray(section)) {
-				sections = section.filter((s): s is string => typeof s === 'string');
-			} else if (
-				typeof section === 'string' &&
-				section.trim().startsWith('[') &&
-				section.trim().endsWith(']')
-			) {
-				try {
-					const parsed = JSON.parse(section);
-					if (Array.isArray(parsed)) {
-						sections = parsed.filter((s): s is string => typeof s === 'string');
-					} else {
-						sections = [section];
-					}
-				} catch {
-					sections = [section];
-				}
-			} else if (typeof section === 'string') {
-				sections = [section];
-			} else {
-				sections = [];
-			}
-
-			const available_sections = await get_sections();
-
-			const settled_results = await Promise.allSettled(
-				sections.map(async (requested_section) => {
-					const matched_section = available_sections.find(
-						(s) =>
-							s.title.toLowerCase() === requested_section.toLowerCase() ||
-							s.slug === requested_section ||
-							s.url === requested_section,
+			try {
+				const content = await get_documentation_handler({ section });
+				return tool.text(content);
+			} catch (e) {
+				const error = e as Error;
+				if (server.ctx.sessionId && server.ctx.custom?.track) {
+					await server.ctx.custom?.track?.(
+						server.ctx.sessionId,
+						'get-documentation-error',
+						error.message,
 					);
-
-					if (matched_section) {
-						try {
-							const response = await fetch_with_timeout(matched_section.url);
-							if (response.ok) {
-								const content = await response.text();
-								return { success: true, content: `## ${matched_section.title}\n\n${content}` };
-							} else {
-								return {
-									success: false,
-									content: `## ${matched_section.title}\n\nError: Could not fetch documentation (HTTP ${response.status})`,
-								};
-							}
-						} catch (error) {
-							return {
-								success: false,
-								content: `## ${matched_section.title}\n\nError: Failed to fetch documentation - ${error}`,
-							};
-						}
-					} else {
-						return {
-							success: false,
-							content: `## ${requested_section}\n\nError: Section not found.`,
-						};
-					}
-				}),
-			);
-
-			const results = settled_results.map((result) => {
-				if (result.status === 'fulfilled') {
-					return result.value;
-				} else {
-					return {
-						success: false,
-						content: `Error: Couldn't fetch - ${result.reason}`,
-					};
 				}
-			});
-
-			const has_any_success = results.some((result) => result.success);
-			let final_text = results.map((r) => r.content).join('\n\n---\n\n');
-
-			if (!has_any_success) {
-				const formatted_sections = await format_sections_list();
-
-				final_text += `\n\n---\n\n${SECTIONS_LIST_INTRO}\n\n${formatted_sections}\n\n${SECTIONS_LIST_OUTRO}`;
+				return tool.error(error.message);
 			}
-
-			return tool.text(final_text);
 		},
 	);
 }
--- a/packages/mcp-server/src/mcp/handlers/tools/handlers.ts
+++ b/packages/mcp-server/src/mcp/handlers/tools/handlers.ts
@@ -0,0 +1,4 @@
+export { get_documentation_handler } from './get-documentation.js';
+export { list_sections_handler } from './list-sections.js';
+export { svelte_autofixer_handler } from './svelte-autofixer.js';
+export { playground_link_handler } from './playground-link.js';
--- a/packages/mcp-server/src/mcp/handlers/tools/index.ts
+++ b/packages/mcp-server/src/mcp/handlers/tools/index.ts
@@ -1,4 +1,4 @@
-export * from './get-documentation.js';
-export * from './list-sections.js';
-export * from './svelte-autofixer.js';
-export * from './playground-link.js';
+export { get_documentation } from './get-documentation.js';
+export { list_sections } from './list-sections.js';
+export { svelte_autofixer } from './svelte-autofixer.js';
+export { playground_link } from './playground-link.js';
--- a/packages/mcp-server/src/mcp/handlers/tools/list-sections.ts
+++ b/packages/mcp-server/src/mcp/handlers/tools/list-sections.ts
@@ -4,21 +4,44 @@ import { SECTIONS_LIST_INTRO, SECTIONS_LIST_OUTRO } from './prompts.js';
 import { icons } from '../../icons/index.js';
 import { tool } from 'tmcp/utils';

+export async function list_sections_handler() {
+	const formatted_sections = await format_sections_list();
+
+	return `${SECTIONS_LIST_INTRO}\n\n${formatted_sections}\n\n${SECTIONS_LIST_OUTRO}`;
+}
+
 export function list_sections(server: SvelteMcp) {
 	server.tool(
 		{
 			name: 'list-sections',
 			description:
 				'Lists all available Svelte 5 and SvelteKit documentation sections in a structured format. Each section includes a "use_cases" field that describes WHEN this documentation would be useful. You should carefully analyze the use_cases field to determine which sections are relevant for the user\'s query. The use_cases contain comma-separated keywords describing project types (e.g., "e-commerce", "blog"), features (e.g., "authentication", "forms"), components (e.g., "slider", "modal"), development stages (e.g., "deployment", "testing"), or "always" for fundamental concepts. Match these use_cases against the user\'s intent - for example, if building an e-commerce site, fetch sections with use_cases containing "e-commerce", "product listings", "shopping cart", etc. If building a slider, look for "slider", "carousel", "animation", etc. Returns sections as "* title: [section_title], use_cases: [use_cases], path: [file_path]". Always run list-sections FIRST for any Svelte query, then analyze ALL use_cases to identify relevant sections, and finally use get_documentation to fetch ALL relevant sections at once.',
+			annotations: {
+				title: 'List Sections',
+				destructiveHint: false,
+				readOnlyHint: true,
+				openWorldHint: false,
+			},
 			icons,
 		},
 		async () => {
 			if (server.ctx.sessionId && server.ctx.custom?.track) {
 				await server.ctx.custom?.track?.(server.ctx.sessionId, 'list-sections');
 			}
-			const formatted_sections = await format_sections_list();
-
-			return tool.text(`${SECTIONS_LIST_INTRO}\n\n${formatted_sections}\n\n${SECTIONS_LIST_OUTRO}`);
+			try {
+				const content = await list_sections_handler();
+				return tool.text(content);
+			} catch (e) {
+				const error = e as Error;
+				if (server.ctx.sessionId && server.ctx.custom?.track) {
+					await server.ctx.custom?.track?.(
+						server.ctx.sessionId,
+						'list-sections-error',
+						error.message,
+					);
+				}
+				return tool.error(error.message);
+			}
 		},
 	);
 }
--- a/packages/mcp-server/src/mcp/handlers/tools/playground-link.test.ts
+++ b/packages/mcp-server/src/mcp/handlers/tools/playground-link.test.ts
@@ -58,7 +58,7 @@ describe('playground-link tool', () => {
 					type: 'resource',
 					resource: expect.objectContaining({
 						uri: 'ui://svelte/playground-link',
-						mimeType: 'text/uri-list',
+						mimeType: 'text/html;profile=mcp-app',
 						_meta: { 'mcpui.dev/ui-preferred-frame-size': ['100%', '1200px'] },
 						text: expect.stringMatching(/^https:\/\/svelte\.dev\/playground\/embed#H4sIA/),
 					}),
@@ -67,6 +67,24 @@ describe('playground-link tool', () => {
 		);
 	});

+	it('should have tool _meta with resource URI for MCP Apps hosts', async () => {
+		const tools = await session.listTools();
+		const playground_tool = tools.tools.find((t) => t.name === 'playground-link');
+		expect(playground_tool).toBeDefined();
+		expect(playground_tool?._meta).toStrictEqual({
+			ui: { resourceUri: 'ui://svelte/playground-link' },
+		});
+	});
+
+	it('should expose a resource for MCP Apps hosts', async () => {
+		const resources = await session.listResources();
+		const playground_resource = resources.resources.find(
+			(r) => r.uri === 'ui://svelte/playground-link',
+		);
+		expect(playground_resource).toBeDefined();
+		expect(playground_resource?.name).toBe('playground-link-ui');
+	});
+
 	it('should not create a playground link if App.svelte is missing', async () => {
 		const result = await session.callTool<{ url: string }>('playground-link', {
 			name: 'My Playground',
--- a/packages/mcp-server/src/mcp/handlers/tools/playground-link.ts
+++ b/packages/mcp-server/src/mcp/handlers/tools/playground-link.ts
@@ -1,8 +1,8 @@
-import type { SvelteMcp } from '../../index.js';
-import * as v from 'valibot';
-import { icons } from '../../icons/index.js';
 import { createUIResource } from '@mcp-ui/server';
 import { tool } from 'tmcp/utils';
+import * as v from 'valibot';
+import { icons } from '../../icons/index.js';
+import type { SvelteMcp } from '../../index.js';

 async function compress_and_encode_text(input: string) {
 	const reader = new Blob([input]).stream().pipeThrough(new CompressionStream('gzip')).getReader();
@@ -30,98 +30,232 @@ type File = {
 	text: boolean;
 };

+const playground_link_schema = v.object({
+	name: v.pipe(
+		v.string(),
+		v.description('The name of the Playground, it should reflect the user task'),
+	),
+	tailwind: v.pipe(
+		v.boolean(),
+		v.description(
+			"If the code requires Tailwind CSS to work...only send true if it it's using tailwind classes in the code",
+		),
+	),
+	files: v.pipe(
+		v.record(v.string(), v.string()),
+		v.description(
+			"An object where all the keys are the filenames (with extensions) and the values are the file content. For example: { 'Component.svelte': '<script>...</script>', 'utils.js': 'export function ...' }. The playground accept multiple files so if are importing from other files just include them all at the root level.",
+		),
+	),
+});
+
+const playground_link_output_schema = v.object({
+	url: v.string(),
+});
+
+export async function playground_link_handler({
+	files,
+	name,
+	tailwind,
+}: v.InferInput<typeof playground_link_schema>) {
+	const playground_base = new URL('https://svelte.dev/playground');
+	const playground_files: File[] = [];
+
+	let has_app_svelte = false;
+
+	for (const [filename, contents] of Object.entries(files)) {
+		if (filename === 'App.svelte') has_app_svelte = true;
+		playground_files.push({
+			type: 'file',
+			name: filename,
+			basename: filename.replace(/^.*[\\/]/, ''),
+			contents,
+			text: true,
+		});
+	}
+
+	if (!has_app_svelte) {
+		throw new Error('The files must contain an App.svelte file as the entry point');
+	}
+
+	const playground_config = {
+		name,
+		tailwind: tailwind ?? false,
+		files: playground_files,
+	};
+
+	playground_base.hash = await compress_and_encode_text(JSON.stringify(playground_config));
+
+	const url = playground_base.toString();
+
+	// use the embed path to have a cleaner UI for mcp-ui
+	playground_base.pathname = '/playground/embed';
+
+	return {
+		url,
+		iframe_url: playground_base.toString(),
+	};
+}
+
+// Create the UI resource for MCP Apps hosts (with adapter)
+// This will be registered as a resource that MCP Apps hosts can fetch
+const playground_ui_resource = createUIResource({
+	uri: 'ui://svelte/playground-link',
+	encoding: 'text',
+	resourceProps: {
+		_meta: {
+			ui: {
+				csp: {
+					connectDomains: ['https://svelte.dev'],
+					resourceDomains: ['https://svelte.dev'],
+					frameDomains: ['https://svelte.dev'],
+					baseUriDomains: ['https://svelte.dev'],
+				},
+			},
+		},
+	},
+	content: {
+		type: 'rawHtml',
+		// This is a placeholder HTML - the actual iframe URL will be set per-request
+		// MCP Apps hosts receive the tool input/output via postMessage
+		htmlString: `<!DOCTYPE html>
+<html>
+<head>
+	<meta charset="utf-8">
+	<meta name="viewport" content="width=device-width, initial-scale=1">
+	<style>
+		* { margin: 0; padding: 0; box-sizing: border-box; }
+		html, body { width: 100%; height: 100%; }
+		iframe { width: 100%; height: 100%; border: none; display: none; }
+		.loading { display: flex; align-items: center; justify-content: center; height: 100%; font-family: system-ui, sans-serif; color: #666; }
+	</style>
+</head>
+<body>
+	<div class="loading" id="loading">Loading playground...</div>
+	<iframe id="playground" allow="clipboard-write"></iframe>
+	<script>
+		function size_changed() {
+			const width = document.body.scrollWidth;
+			window.parent.postMessage({
+				jsonrpc: '2.0',
+				method: 'ui/notifications/size-changed',
+				params: {
+					width,
+					height: 800
+					}
+				}, '*');
+		}
+		// Signal that the widget is ready
+		window.parent.postMessage({ type: 'ui-lifecycle-iframe-ready' }, '*');
+		
+		// Listen for render data from the adapter (for MCP Apps hosts)
+		window.addEventListener('message', (event) => {
+			if (event.data.type === 'ui-lifecycle-iframe-render-data') {
+				const renderData = event.data.payload.renderData || {};
+				const toolOutput = renderData.toolOutput;
+				
+				// The tool output contains the iframe URL
+				if (toolOutput && toolOutput.structuredContent && toolOutput.structuredContent.url) {
+					const iframe = document.getElementById('playground');
+					const loading = document.getElementById('loading');
+					// Convert the URL to embed URL
+					const embedUrl = toolOutput.structuredContent.url.replace('/playground#', '/playground/embed#');
+					iframe.src = embedUrl;
+					iframe.style.display = 'block';
+					iframe.addEventListener("load", () => {
+						size_changed();
+					});
+					loading.style.display = 'none';
+				}
+			}
+		});
+	</script>
+</body>
+</html>`,
+	},
+	uiMetadata: {
+		'preferred-frame-size': ['100%', '1200px'],
+	},
+	adapters: {
+		mcpApps: { enabled: true },
+	},
+});
+
 export function playground_link(server: SvelteMcp) {
+	// Register the UI resource so MCP Apps hosts can fetch it
+	server.resource(
+		{
+			name: 'playground-link-ui',
+			description: 'UI resource for the Svelte Playground widget',
+			uri: playground_ui_resource.resource.uri,
+			icons,
+		},
+		() => {
+			return {
+				contents: [playground_ui_resource.resource],
+			};
+		},
+	);
+
 	server.tool(
 		{
 			name: 'playground-link',
 			description:
 				'Generates a Playground link given a Svelte code snippet. Once you have the final version of the code you want to send to the user, ALWAYS ask the user if it wants a playground link to allow it to quickly check the code in the playground before calling this tool. NEVER use this tool if you have written the component to a file in the user project. The playground accept multiple files so if are importing from other files just include them all at the root level.',
-			schema: v.object({
-				name: v.pipe(
-					v.string(),
-					v.description('The name of the Playground, it should reflect the user task'),
-				),
-				tailwind: v.pipe(
-					v.boolean(),
-					v.description(
-						"If the code requires Tailwind CSS to work...only send true if it it's using tailwind classes in the code",
-					),
-				),
-				files: v.pipe(
-					v.record(v.string(), v.string()),
-					v.description(
-						"An object where all the keys are the filenames (with extensions) and the values are the file content. For example: { 'Component.svelte': '<script>...</script>', 'utils.js': 'export function ...' }. The playground accept multiple files so if are importing from other files just include them all at the root level.",
-					),
-				),
-			}),
-			outputSchema: v.object({
-				url: v.string(),
-			}),
+			schema: playground_link_schema,
+			outputSchema: playground_link_output_schema,
+			annotations: {
+				title: 'Playground Link',
+				destructiveHint: false,
+				readOnlyHint: true,
+				openWorldHint: false,
+			},
 			icons,
+			// For MCP Apps hosts - points to the registered resource
+			_meta: {
+				ui: {
+					resourceUri: playground_ui_resource.resource.uri,
+				},
+			},
 		},
 		async ({ files, name, tailwind }) => {
 			if (server.ctx.sessionId && server.ctx.custom?.track) {
 				await server.ctx.custom?.track?.(server.ctx.sessionId, 'playground-link');
 			}
-			const playground_base = new URL('https://svelte.dev/playground');
-			const playground_files: File[] = [];
-
-			let has_app_svelte = false;
-
-			for (const [filename, contents] of Object.entries(files)) {
-				if (filename === 'App.svelte') has_app_svelte = true;
-				playground_files.push({
-					type: 'file',
-					name: filename,
-					basename: filename.replace(/^.*[\\/]/, ''),
-					contents,
-					text: true,
-				});
-			}
-
-			if (!has_app_svelte) {
+			try {
+				const result = await playground_link_handler({ files, name, tailwind });
+				return {
+					content: [
+						{
+							type: 'text',
+							text: JSON.stringify({ url: result.url }),
+						},
+						// Embedded resource for MCP-UI hosts (no adapter, uses externalUrl)
+						createUIResource({
+							uri: 'ui://svelte/playground-link',
+							content: {
+								type: 'externalUrl',
+								iframeUrl: result.iframe_url,
+							},
+							uiMetadata: {
+								'preferred-frame-size': ['100%', '1200px'],
+							},
+							encoding: 'text',
+						}),
+					],
+					structuredContent: { url: result.url },
+				};
+			} catch (e) {
+				const error = e as Error;
 				if (server.ctx.sessionId && server.ctx.custom?.track) {
-					await server.ctx.custom?.track?.(server.ctx.sessionId, 'playground-link-no-app-svelte');
+					await server.ctx.custom?.track?.(
+						server.ctx.sessionId,
+						'playground-link-error',
+						error.message,
+					);
 				}
-
-				return tool.error('The files must contain an App.svelte file as the entry point');
+				return tool.error(error.message);
 			}
-
-			const playground_config = {
-				name,
-				tailwind: tailwind ?? false,
-				files: playground_files,
-			};
-
-			playground_base.hash = await compress_and_encode_text(JSON.stringify(playground_config));
-
-			const content = {
-				url: playground_base.toString(),
-			};
-
-			// use the embed path to have a cleaner UI for mcp-ui
-			playground_base.pathname = '/playground/embed';
-
-			return {
-				content: [
-					{
-						type: 'text',
-						text: JSON.stringify(content),
-					},
-					createUIResource({
-						uri: 'ui://svelte/playground-link',
-						content: {
-							type: 'externalUrl',
-							iframeUrl: playground_base.toString(),
-						},
-						uiMetadata: {
-							'preferred-frame-size': ['100%', '1200px'],
-						},
-						encoding: 'text',
-					}),
-				],
-				structuredContent: content,
-			};
 		},
 	);
 }
--- a/packages/mcp-server/src/mcp/handlers/tools/svelte-autofixer.test.ts
+++ b/packages/mcp-server/src/mcp/handlers/tools/svelte-autofixer.test.ts
@@ -53,6 +53,18 @@ describe('svelte-autofixer tool', () => {
 		);
 	});

+	it('should add suggestions for snippets declared in script tag', async () => {
+		const content = await autofixer_tool_call(`<script>
+			{#snippet my_snippet()}
+				some content
+			{/snippet}
+		</script>`);
+		expect(content.issues.length).toBeGreaterThan(0);
+		expect(content.suggestions).toContain(
+			"The code can't be compiled because a Javascript parse error. The error suggests you have a `{#snippet ...}` block inside the `<script>` tag. Snippets are template syntax and should be declared in the markup section of the component, not in the script. Move the snippet outside of the `<script>` tag. Snippets declared in the markup can also be accessed in the script tag in case you need them.",
+		);
+	});
+
 	it('should error out if async is true with a version less than 5', async () => {
 		const content = await autofixer_tool_call(
 			`<script>
--- a/packages/mcp-server/src/mcp/handlers/tools/svelte-autofixer.ts
+++ b/packages/mcp-server/src/mcp/handlers/tools/svelte-autofixer.ts
@@ -7,6 +7,102 @@ import { add_autofixers_issues } from '../../autofixers/add-autofixers-issues.js
 import { icons } from '../../icons/index.js';
 import { tool } from 'tmcp/utils';

+const autofixer_schema = v.object({
+	code: v.string(),
+	desired_svelte_version: v.pipe(
+		v.union([v.string(), v.number()]),
+		v.description(
+			'The desired svelte version...if possible read this from the package.json of the user project, otherwise use some hint from the wording (if the user asks for runes it wants version 5). Default to 5 in case of doubt.',
+		),
+	),
+	async: v.pipe(
+		v.optional(v.boolean()),
+		v.description(
+			'If true the code is an async component/module and might use await in the markup or top-level awaits in the script tag. If possible check the svelte.config.js/svelte.config.ts to check if the option is enabled otherwise asks the user if they prefer using it or not. You can only use this option if the version is 5.',
+		),
+	),
+	filename: v.pipe(
+		v.optional(v.string()),
+		v.description(
+			'The filename of the component if available, it MUST be only the Component name with .svelte or .svelte.ts extension and not the entire path.',
+		),
+	),
+});
+
+const autofixer_output_schema = v.object({
+	issues: v.array(v.string()),
+	suggestions: v.array(v.string()),
+	require_another_tool_call_after_fixing: v.boolean(),
+});
+
+export async function svelte_autofixer_handler({
+	code,
+	desired_svelte_version: desired_svelte_version_unchecked,
+	async,
+	filename: filename_or_path,
+}: v.InferInput<typeof autofixer_schema>) {
+	// we validate manually because some clients don't support union in the input schema (looking at you cursor)
+	const parsed_version = v.safeParse(
+		v.union([v.literal(4), v.literal(5), v.literal('4'), v.literal('5')]),
+		desired_svelte_version_unchecked,
+	);
+	if (parsed_version.success === false) {
+		throw new Error(
+			`The desired_svelte_version MUST be either 4 or 5 but received "${desired_svelte_version_unchecked}"`,
+		);
+	}
+
+	const desired_svelte_version = parsed_version.output;
+
+	if (async && +desired_svelte_version < 5) {
+		throw new Error('The async option can only be used with Svelte version 5 or higher.');
+	}
+
+	const content: {
+		issues: string[];
+		suggestions: string[];
+		require_another_tool_call_after_fixing: boolean;
+	} = { issues: [], suggestions: [], require_another_tool_call_after_fixing: false };
+	try {
+		// just in case the LLM sends a full path we extract the filename...it's not really needed
+		// but it's nice to have a filename in the errors
+
+		const filename = filename_or_path ? basename(filename_or_path) : 'Component.svelte';
+
+		add_compile_issues(content, code, +desired_svelte_version, filename, async);
+
+		add_autofixers_issues(content, code, +desired_svelte_version, filename, async);
+
+		await add_eslint_issues(content, code, +desired_svelte_version, filename, async);
+	} catch (e: unknown) {
+		const error = e as Error & { start?: { line: number; column: number }; frame?: string };
+		content.issues.push(
+			`${error.message} at line ${error.start?.line}, column ${error.start?.column}`,
+		);
+		if (error.message.includes('js_parse_error')) {
+			// Check if the error frame contains template syntax that was incorrectly placed in the script tag
+			if (error.frame?.includes('{#snippet')) {
+				content.suggestions.push(
+					"The code can't be compiled because a Javascript parse error. The error suggests you have a `{#snippet ...}` block inside the `<script>` tag. Snippets are template syntax and should be declared in the markup section of the component, not in the script. Move the snippet outside of the `<script>` tag. Snippets declared in the markup can also be accessed in the script tag in case you need them.",
+				);
+			} else {
+				content.suggestions.push(
+					"The code can't be compiled because a Javascript parse error. In case you are using runes like this `$state variable_name = 3;` or `$derived variable_name = 3 * count` that's not how runes are used. You need to use them as function calls without importing them: `const variable_name = $state(3)` and `const variable_name = $derived(3 * count)`.",
+				);
+			}
+		} else if (error.message.includes('css_expected_identifier')) {
+			content.suggestions.push(
+				"The code can't be compiled because a valid CSS identifier is expected. This sometimes means you are trying to use a variable in CSS like this: `color: {my_color}` but Svelte doesn't support that. You can use inline CSS variables for that `<div style:--color={my_color}></div>` and then use the variable as usual in CSS with `color: var(--color)`.",
+			);
+		}
+	}
+
+	if (content.issues.length > 0 || content.suggestions.length > 0) {
+		content.require_another_tool_call_after_fixing = true;
+	}
+	return content;
+}
+
 export function svelte_autofixer(server: SvelteMcp) {
 	server.tool(
 		{
@@ -14,32 +110,8 @@ export function svelte_autofixer(server: SvelteMcp) {
 			title: 'Svelte Autofixer',
 			description:
 				'Given a svelte component or module returns a list of suggestions to fix any issues it has. This tool MUST be used whenever the user is asking to write svelte code before sending the code back to the user',
-			schema: v.object({
-				code: v.string(),
-				desired_svelte_version: v.pipe(
-					v.union([v.string(), v.number()]),
-					v.description(
-						'The desired svelte version...if possible read this from the package.json of the user project, otherwise use some hint from the wording (if the user asks for runes it wants version 5). Default to 5 in case of doubt.',
-					),
-				),
-				async: v.pipe(
-					v.optional(v.boolean()),
-					v.description(
-						'If true the code is an async component/module and might use await in the markup or top-level awaits in the script tag. If possible check the svelte.config.js/svelte.config.ts to check if the option is enabled otherwise asks the user if they prefer using it or not. You can only use this option if the version is 5.',
-					),
-				),
-				filename: v.pipe(
-					v.optional(v.string()),
-					v.description(
-						'The filename of the component if available, it MUST be only the Component name with .svelte or .svelte.ts extension and not the entire path.',
-					),
-				),
-			}),
-			outputSchema: v.object({
-				issues: v.array(v.string()),
-				suggestions: v.array(v.string()),
-				require_another_tool_call_after_fixing: v.boolean(),
-			}),
+			schema: autofixer_schema,
+			outputSchema: autofixer_output_schema,
 			annotations: {
 				title: 'Svelte Autofixer',
 				destructiveHint: false,
@@ -57,63 +129,25 @@ export function svelte_autofixer(server: SvelteMcp) {
 			if (server.ctx.sessionId && server.ctx.custom?.track) {
 				await server.ctx.custom?.track?.(server.ctx.sessionId, 'svelte-autofixer');
 			}
-			// we validate manually because some clients don't support union in the input schema (looking at you cursor)
-			const parsed_version = v.safeParse(
-				v.union([v.literal(4), v.literal(5), v.literal('4'), v.literal('5')]),
-				desired_svelte_version_unchecked,
-			);
-			if (parsed_version.success === false) {
-				if (server.ctx.sessionId && server.ctx.custom?.track) {
-					await server.ctx.custom?.track?.(server.ctx.sessionId, 'svelte-autofixer-wrong-version');
-				}
-				return tool.error(
-					`The desired_svelte_version MUST be either 4 or 5 but received "${desired_svelte_version_unchecked}"`,
-				);
-			}
-
-			const desired_svelte_version = parsed_version.output;
-
-			if (async && +desired_svelte_version < 5) {
-				return tool.error('The async option can only be used with Svelte version 5 or higher.');
-			}
-
-			const content: {
-				issues: string[];
-				suggestions: string[];
-				require_another_tool_call_after_fixing: boolean;
-			} = { issues: [], suggestions: [], require_another_tool_call_after_fixing: false };
 			try {
-				// just in case the LLM sends a full path we extract the filename...it's not really needed
-				// but it's nice to have a filename in the errors
-
-				const filename = filename_or_path ? basename(filename_or_path) : 'Component.svelte';
-
-				add_compile_issues(content, code, +desired_svelte_version, filename, async);
-
-				add_autofixers_issues(content, code, +desired_svelte_version, filename, async);
-
-				await add_eslint_issues(content, code, +desired_svelte_version, filename, async);
-			} catch (e: unknown) {
-				const error = e as Error & { start?: { line: number; column: number } };
-				content.issues.push(
-					`${error.message} at line ${error.start?.line}, column ${error.start?.column}`,
-				);
-				if (error.message.includes('js_parse_error')) {
-					content.suggestions.push(
-						"The code can't be compiled because a Javascript parse error. In case you are using runes like this `$state variable_name = 3;` or `$derived variable_name = 3 * count` that's not how runes are used. You need to use them as function calls without importing them: `const variable_name = $state(3)` and `const variable_name = $derived(3 * count)`.",
-					);
-				} else if (error.message.includes('css_expected_identifier')) {
-					content.suggestions.push(
-						"The code can't be compiled because a valid CSS identifier is expected. This sometimes means you are trying to use a variable in CSS like this: `color: {my_color}` but Svelte doesn't support that. You can use inline CSS variables for that `<div style:--color={my_color}></div>` and then use the variable as usual in CSS with `color: var(--color)`.",
+				const content = await svelte_autofixer_handler({
+					code,
+					desired_svelte_version: desired_svelte_version_unchecked,
+					async,
+					filename: filename_or_path,
+				});
+				return tool.structured(content);
+			} catch (e) {
+				const error = e as Error;
+				if (server.ctx.sessionId && server.ctx.custom?.track) {
+					await server.ctx.custom?.track?.(
+						server.ctx.sessionId,
+						'svelte-autofixer-error',
+						error.message,
 					);
 				}
+				return tool.error(error.message);
 			}
-
-			if (content.issues.length > 0 || content.suggestions.length > 0) {
-				content.require_another_tool_call_after_fixing = true;
-			}
-
-			return tool.structured(content);
 		},
 	);
 }
--- a/packages/mcp-stdio/CHANGELOG.md
+++ b/packages/mcp-stdio/CHANGELOG.md
@@ -1,145 +1,175 @@
 # @sveltejs/mcp

+## 0.1.20
+
+### Patch Changes
+
+- fix: turn off no-inspect in eslint for mcp ([`2245cb2`](https://github.com/sveltejs/ai-tools/commit/2245cb2dc9e2d217869b6a800795ce59ffb40c51))
+
+## 0.1.19
+
+### Patch Changes
+
+- chore: update svelte ([`7447744`](https://github.com/sveltejs/ai-tools/commit/74477448cea44ec21684ea4d39f2c5c7133b5150))
+
+## 0.1.18
+
+### Patch Changes
+
+- feat: expose playground link as MCP App ([#138](https://github.com/sveltejs/ai-tools/pull/138))
+
+## 0.1.17
+
+### Patch Changes
+
+- fix: add suggestion for snippets declared in script tag ([#132](https://github.com/sveltejs/ai-tools/pull/132))
+
+## 0.1.16
+
+### Patch Changes
+
+- feat: expose tools as JS api + cli ([#128](https://github.com/sveltejs/ai-tools/pull/128))
+
 ## 0.1.15

 ### Patch Changes

- fix: server.json version + update publisher ([`9dfb4de`](https://github.com/sveltejs/mcp/commit/9dfb4dedb42837c40c4e660f0f816d7cf9081fc4))
+- fix: server.json version + update publisher ([`9dfb4de`](https://github.com/sveltejs/ai-tools/commit/9dfb4dedb42837c40c4e660f0f816d7cf9081fc4))

 ## 0.1.14

 ### Patch Changes

- fix: improve prompt to reduce token usage ([#124](https://github.com/sveltejs/mcp/pull/124))
+- fix: improve prompt to reduce token usage ([#124](https://github.com/sveltejs/ai-tools/pull/124))

 ## 0.1.13

 ### Patch Changes

- fix: revert name change and add title ([`98efa1e`](https://github.com/sveltejs/mcp/commit/98efa1e09ebcca7827b10dc6bc8e1699fc1e5171))
+- fix: revert name change and add title ([`98efa1e`](https://github.com/sveltejs/ai-tools/commit/98efa1e09ebcca7827b10dc6bc8e1699fc1e5171))

 ## 0.1.12

 ### Patch Changes

- fix: update server name on mcp registry ([`60297b3`](https://github.com/sveltejs/mcp/commit/60297b3c49bf110b48908e61b5d5d902ea1bdf39))
+- fix: update server name on mcp registry ([`60297b3`](https://github.com/sveltejs/ai-tools/commit/60297b3c49bf110b48908e61b5d5d902ea1bdf39))

- chore: update tmcp ([#99](https://github.com/sveltejs/mcp/pull/99))
+- chore: update tmcp ([#99](https://github.com/sveltejs/ai-tools/pull/99))

 ## 0.1.11

 ### Patch Changes

- fix: add `async` parameter to `svelte-autofixer` ([#94](https://github.com/sveltejs/mcp/pull/94))
+- fix: add `async` parameter to `svelte-autofixer` ([#94](https://github.com/sveltejs/ai-tools/pull/94))

- fix: install latest eslint svelte packages to support `$state.eager` ([`f6ce89f`](https://github.com/sveltejs/mcp/commit/f6ce89ff34faabc3d746a350ea347298ecfed2ec))
+- fix: install latest eslint svelte packages to support `$state.eager` ([`f6ce89f`](https://github.com/sveltejs/ai-tools/commit/f6ce89ff34faabc3d746a350ea347298ecfed2ec))

 ## 0.1.10

 ### Patch Changes

- fix: add icons to `server.json` ([`02c951b`](https://github.com/sveltejs/mcp/commit/02c951baa86ac8103ffc158a202c06cfe6b15c01))
+- fix: add icons to `server.json` ([`02c951b`](https://github.com/sveltejs/ai-tools/commit/02c951baa86ac8103ffc158a202c06cfe6b15c01))

- fix: add `preferred-frame-size` to UI resource ([`3fabcc0`](https://github.com/sveltejs/mcp/commit/3fabcc0f9bfee916c0deb9c2ffa931ed2168af2d))
+- fix: add `preferred-frame-size` to UI resource ([`3fabcc0`](https://github.com/sveltejs/ai-tools/commit/3fabcc0f9bfee916c0deb9c2ffa931ed2168af2d))

- feat: support: `$state.eager` ([#90](https://github.com/sveltejs/mcp/pull/90))
+- feat: support: `$state.eager` ([#90](https://github.com/sveltejs/ai-tools/pull/90))

 ## 0.1.9

 ### Patch Changes

- feat: return `mcp-ui` resource from `playground-link` ([#84](https://github.com/sveltejs/mcp/pull/84))
+- feat: return `mcp-ui` resource from `playground-link` ([#84](https://github.com/sveltejs/ai-tools/pull/84))

- feat: suggest against js variables in css ([#78](https://github.com/sveltejs/mcp/pull/78))
+- feat: suggest against js variables in css ([#78](https://github.com/sveltejs/ai-tools/pull/78))

 ## 0.1.8

 ### Patch Changes

- fix: upgrade registry publisher cli ([`5fa2baa`](https://github.com/sveltejs/mcp/commit/5fa2baa27009f01e0e4e91cee7984b81a81c1c29))
+- fix: upgrade registry publisher cli ([`5fa2baa`](https://github.com/sveltejs/ai-tools/commit/5fa2baa27009f01e0e4e91cee7984b81a81c1c29))

 ## 0.1.7

 ### Patch Changes

- fix: use correct server schema version ([`579be87`](https://github.com/sveltejs/mcp/commit/579be877fa9f87f7f173450ca5bc918824d68282))
+- fix: use correct server schema version ([`579be87`](https://github.com/sveltejs/ai-tools/commit/579be877fa9f87f7f173450ca5bc918824d68282))

 ## 0.1.6

 ### Patch Changes

- fix: prevent `imported_runes` suggestion from being added for libs that are not svelte ([`87af64f`](https://github.com/sveltejs/mcp/commit/87af64f4bc6d07b75640eb987a33655654363997))
+- fix: prevent `imported_runes` suggestion from being added for libs that are not svelte ([`87af64f`](https://github.com/sveltejs/ai-tools/commit/87af64f4bc6d07b75640eb987a33655654363997))

- feat: add svelte icon and website url for mcp server ([#75](https://github.com/sveltejs/mcp/pull/75))
+- feat: add svelte icon and website url for mcp server ([#75](https://github.com/sveltejs/ai-tools/pull/75))

- fix: use `data:` uri for local icon & add icons to tools + resources + prompts ([`cf62286`](https://github.com/sveltejs/mcp/commit/cf622869129382a97ad059bb1389f115907adc8e))
+- fix: use `data:` uri for local icon & add icons to tools + resources + prompts ([`cf62286`](https://github.com/sveltejs/ai-tools/commit/cf622869129382a97ad059bb1389f115907adc8e))

 ## 0.1.5

 ### Patch Changes

- fix: widen `desired_svelte_version` validation to accommodate some clients ([`3b301d7`](https://github.com/sveltejs/mcp/commit/3b301d7d9c2f49758023408f505bc4ca79caaff4))
+- fix: widen `desired_svelte_version` validation to accommodate some clients ([`3b301d7`](https://github.com/sveltejs/ai-tools/commit/3b301d7d9c2f49758023408f505bc4ca79caaff4))

- fix: minor tweaks to the prompt to allow for automatic sync ([#63](https://github.com/sveltejs/mcp/pull/63))
+- fix: minor tweaks to the prompt to allow for automatic sync ([#63](https://github.com/sveltejs/ai-tools/pull/63))

- feat: `read_state_with_dollar` autofixer ([#66](https://github.com/sveltejs/mcp/pull/66))
+- feat: `read_state_with_dollar` autofixer ([#66](https://github.com/sveltejs/ai-tools/pull/66))

 ## 0.1.4

 ### Patch Changes

- fix: pass secrets in action and update `mcpName` ([`044f098`](https://github.com/sveltejs/mcp/commit/044f0988b935fff39911a861a648dfb276f5831a))
+- fix: pass secrets in action and update `mcpName` ([`044f098`](https://github.com/sveltejs/ai-tools/commit/044f0988b935fff39911a861a648dfb276f5831a))

 ## 0.1.3

 ### Patch Changes

- fix: use DNS to publish MCP ([#59](https://github.com/sveltejs/mcp/pull/59))
+- fix: use DNS to publish MCP ([#59](https://github.com/sveltejs/ai-tools/pull/59))

 ## 0.1.2

 ### Patch Changes

- fix: publish to MCP registry (I really hope this time for real) ([`ef5241c`](https://github.com/sveltejs/mcp/commit/ef5241cbc204ad8bb84bde27db7c9d0a08280245))
+- fix: publish to MCP registry (I really hope this time for real) ([`ef5241c`](https://github.com/sveltejs/ai-tools/commit/ef5241cbc204ad8bb84bde27db7c9d0a08280245))

 ## 0.1.1

 ### Patch Changes

- feat: publish mcp to registry (maybe for real this time) ([`132943d`](https://github.com/sveltejs/mcp/commit/132943db3b04dbbd322d08926c0880c990a61f5f))
+- feat: publish mcp to registry (maybe for real this time) ([`132943d`](https://github.com/sveltejs/ai-tools/commit/132943db3b04dbbd322d08926c0880c990a61f5f))

 ## 0.1.0

 ### Minor Changes

- feat: publish to registry ([#45](https://github.com/sveltejs/mcp/pull/45))
+- feat: publish to registry ([#45](https://github.com/sveltejs/ai-tools/pull/45))

 ### Patch Changes

- feat: add autofixer to tell the LLM to check if some function called in effect is assigning state #26 ([`73d7625`](https://github.com/sveltejs/mcp/commit/73d7625b3ca6a812ba91883ea668d80ff1e7c703))
+- feat: add autofixer to tell the LLM to check if some function called in effect is assigning state #26 ([`73d7625`](https://github.com/sveltejs/ai-tools/commit/73d7625b3ca6a812ba91883ea668d80ff1e7c703))

- feat: add bind:this -> attachment and action -> attachment autofixer #20 ([`73d7625`](https://github.com/sveltejs/mcp/commit/73d7625b3ca6a812ba91883ea668d80ff1e7c703))
+- feat: add bind:this -> attachment and action -> attachment autofixer #20 ([`73d7625`](https://github.com/sveltejs/ai-tools/commit/73d7625b3ca6a812ba91883ea668d80ff1e7c703))

 ## 0.0.4

 ### Patch Changes

- fix: allow TS `.svelte.ts` modules ([#49](https://github.com/sveltejs/mcp/pull/49))
+- fix: allow TS `.svelte.ts` modules ([#49](https://github.com/sveltejs/ai-tools/pull/49))

 ## 0.0.3

 ### Patch Changes

- fix: check effect.pre in assign-in-effect ([#41](https://github.com/sveltejs/mcp/pull/41))
+- fix: check effect.pre in assign-in-effect ([#41](https://github.com/sveltejs/ai-tools/pull/41))

- feat: `use_cases` documentation metadata ([#29](https://github.com/sveltejs/mcp/pull/29))
+- feat: `use_cases` documentation metadata ([#29](https://github.com/sveltejs/ai-tools/pull/29))

- fix: change title names to allow for claude code to use the prompt ([`725f785`](https://github.com/sveltejs/mcp/commit/725f785766d04e9ed810a7c3f6bcfdb2e2b8234c))
+- fix: change title names to allow for claude code to use the prompt ([`725f785`](https://github.com/sveltejs/ai-tools/commit/725f785766d04e9ed810a7c3f6bcfdb2e2b8234c))

- fix: enable doc tools ([`cb316c5`](https://github.com/sveltejs/mcp/commit/cb316c5b3ebc712946969d2d57236d159e796d58))
+- fix: enable doc tools ([`cb316c5`](https://github.com/sveltejs/ai-tools/commit/cb316c5b3ebc712946969d2d57236d159e796d58))

 ## 0.0.2

 ### Patch Changes

- feat: latest version ([#25](https://github.com/sveltejs/mcp/pull/25))
+- feat: latest version ([#25](https://github.com/sveltejs/ai-tools/pull/25))
--- a/packages/mcp-stdio/package.json
+++ b/packages/mcp-stdio/package.json
@@ -1,24 +1,30 @@
 {
 	"name": "@sveltejs/mcp",
-	"version": "0.1.15",
+	"version": "0.1.20",
 	"type": "module",
 	"license": "MIT",
 	"mcpName": "dev.svelte/mcp",
-	"homepage": "https://github.com/sveltejs/mcp#readme",
+	"homepage": "https://github.com/sveltejs/ai-tools#readme",
 	"bugs": {
-		"url": "https://github.com/sveltejs/mcp/issues"
+		"url": "https://github.com/sveltejs/ai-tools/issues"
 	},
 	"bin": {
 		"svelte-mcp": "./dist/index.mjs"
 	},
 	"repository": {
 		"type": "git",
-		"url": "git+https://github.com/sveltejs/mcp.git",
+		"url": "git+https://github.com/sveltejs/ai-tools.git",
 		"path": "packages/mcp-stdio"
 	},
 	"files": [
 		"dist"
 	],
+	"exports": {
+		".": {
+			"types": "./dist/handlers.d.mts",
+			"import": "./dist/handlers.mjs"
+		}
+	},
 	"publishConfig": {
 		"access": "public"
 	},
@@ -41,6 +47,7 @@
 	},
 	"dependencies": {
 		"eslint": "catalog:lint",
+		"sade": "catalog:tooling",
 		"tmcp": "catalog:tmcp"
 	}
 }
--- a/packages/mcp-stdio/server.json
+++ b/packages/mcp-stdio/server.json
@@ -5,11 +5,11 @@
 	"description": "The official Svelte MCP server providing docs and autofixing tools for Svelte development",
 	"repository": {
 		"id": "1054419133",
-		"url": "https://github.com/sveltejs/mcp",
+		"url": "https://github.com/sveltejs/ai-tools",
 		"subfolder": "packages/mcp-stdio",
 		"source": "github"
 	},
-	"version": "0.1.15",
+	"version": "0.1.20",
 	"websiteUrl": "https://svelte.dev/docs/mcp/overview",
 	"icons": [
 		{
@@ -25,7 +25,7 @@
 		{
 			"registryType": "npm",
 			"identifier": "@sveltejs/mcp",
-			"version": "0.1.15",
+			"version": "0.1.20",
 			"runtimeHint": "npx",
 			"transport": {
 				"type": "stdio"
--- a/packages/mcp-stdio/src/handlers.ts
+++ b/packages/mcp-stdio/src/handlers.ts
@@ -0,0 +1,6 @@
+export {
+	list_sections_handler as listSections,
+	get_documentation_handler as getDocumentation,
+	svelte_autofixer_handler as svelteAutofixer,
+	playground_link_handler as playgroundLink,
+} from '@sveltejs/mcp-server/handlers';
--- a/packages/mcp-stdio/src/index.ts
+++ b/packages/mcp-stdio/src/index.ts
@@ -1,7 +1,65 @@
 #! /usr/bin/env node
 import { server } from '@sveltejs/mcp-server';
+import {
+	list_sections_handler,
+	get_documentation_handler,
+	svelte_autofixer_handler,
+} from '@sveltejs/mcp-server/handlers';
+import { readFile } from 'node:fs/promises';
+import { existsSync } from 'node:fs';
 import { StdioTransport } from '@tmcp/transport-stdio';
+import sade from 'sade';

-const transport = new StdioTransport(server);
+const cli = sade('svelte-mcp');

-transport.listen();
+cli.command('__mcp', '', { default: true }).action(() => {
+	const transport = new StdioTransport(server);
+	transport.listen();
+});
+
+cli
+	.command('list-sections')
+	.describe('List all the available documentation sections')
+	.action(async () => {
+		console.log(await list_sections_handler());
+	});
+
+cli
+	.command('get-documentation <sections>')
+	.describe('Get documentation for specified sections, separated by commas')
+	.action(async (sections) => {
+		console.log(await get_documentation_handler({ section: sections.split(',') }));
+	});
+
+cli
+	.command('svelte-autofixer <code_or_path>')
+	.describe(
+		'Detect and suggest fixes for Svelte code issues, because the terminal will substitute variables `$` should be correctly escaped',
+	)
+	.option('--async', 'Wether the project is using async svelte or not', false)
+	.option('--svelte-version', 'Which version of svelte to use...it can be 4 or 5', 5)
+	.action(async (code_or_path, { async, 'svelte-version': version }) => {
+		let code = code_or_path;
+
+		let is_path = false;
+
+		if (existsSync(code_or_path)) {
+			console.log('Detected file path, reading file...');
+			code = await readFile(code_or_path, 'utf-8');
+			is_path = true;
+		} else {
+			console.log('File not found, treating input as code...');
+		}
+
+		const desired_svelte_version = +version;
+
+		const result = await svelte_autofixer_handler({
+			code,
+			async: Boolean(async),
+			desired_svelte_version,
+			filename: is_path ? code_or_path : undefined,
+		});
+		console.log(result);
+	});
+
+cli.parse(process.argv);
--- a/packages/mcp-stdio/tsdown.config.ts
+++ b/packages/mcp-stdio/tsdown.config.ts
@@ -2,7 +2,7 @@ import { defineConfig } from 'tsdown';

 export default defineConfig([
 	{
-		entry: ['./src/index.ts'],
+		entry: ['./src/index.ts', './src/handlers.ts'],
 		platform: 'node',
 		define: {
 			// some eslint-plugin-svelte code expects __filename to exists but in an ESM environment it does not.
@@ -13,9 +13,12 @@ export default defineConfig([
 		// the require would fail once executed in a project without eslint installed.
 		external: ['eslint'],
 		publint: true,
-		dts: false,
+		dts: {
+			eager: true,
+		},
 		treeshake: true,
 		clean: true,
 		target: 'esnext',
+		inlineOnly: false,
 	},
 ]);
--- a/packages/opencode/CHANGELOG.md
+++ b/packages/opencode/CHANGELOG.md
@@ -0,0 +1,37 @@
+# @sveltejs/opencode
+
+## 0.1.3
+
+### Patch Changes
+
+- fix: better subagent instructions to use MCP or skill ([#163](https://github.com/sveltejs/ai-tools/pull/163))
+
+## 0.1.2
+
+### Patch Changes
+
+- feat: allow for local opencode config ([#156](https://github.com/sveltejs/ai-tools/pull/156))
+
+## 0.1.1
+
+### Patch Changes
+
+- fix: actually push skills to right config path ([`c2c1b3e`](https://github.com/sveltejs/ai-tools/commit/c2c1b3e5e788b14eea17cd37a83ca55433cc4072))
+
+## 0.1.0
+
+### Minor Changes
+
+- feat: distribute skills through opencode plugin ([#151](https://github.com/sveltejs/ai-tools/pull/151))
+
+## 0.0.3
+
+### Patch Changes
+
+- chore: add README to opencode plugin ([`71295bc`](https://github.com/sveltejs/ai-tools/commit/71295bc11fb7bac6703e655f5fddead29967353c))
+
+## 0.0.2
+
+### Patch Changes
+
+- fix: show toast after a few seconds to avoid race condition ([`57e2d1d`](https://github.com/sveltejs/ai-tools/commit/57e2d1def1f5590d0a3dd6d269ac39f6397ffecf))
--- a/packages/opencode/README.md
+++ b/packages/opencode/README.md
@@ -0,0 +1,75 @@
+# @sveltejs/opencode
+
+OpenCode plugin for Svelte that provides the Svelte MCP server, a specialized file editor subagent and instruction files.
+
+## Installation
+
+Add `@sveltejs/opencode` to your OpenCode config (either global or local):
+
+```json
+{
+	"$schema": "https://opencode.ai/config.json",
+	"plugin": ["@sveltejs/opencode"]
+}
+```
+
+That's it! You now have the Svelte MCP server and the file editor subagent configured automatically.
+
+## Features
+
+### Svelte MCP Server
+
+The plugin automatically configures the [Svelte MCP server](https://mcp.svelte.dev) which provides:
+
+- **list-sections** - Discover available Svelte 5 and SvelteKit documentation sections
+- **get-documentation** - Retrieve full documentation content for specific sections
+- **svelte-autofixer** - Analyze Svelte code and get issues/suggestions
+- **playground-link** - Generate Svelte Playground links with provided code
+
+### Svelte File Editor Subagent
+
+A specialized subagent (`svelte-file-editor`) that is automatically used when creating, editing, or reviewing `.svelte`, `.svelte.ts`, or `.svelte.js` files. It fetches relevant documentation and validates code using the Svelte MCP server tools.
+
+### Agent Instructions
+
+The plugin injects instructions that teach the agent how to effectively use the Svelte MCP tools.
+
+## Configuration
+
+The default configuration:
+
+```json
+{
+	"$schema": "https://raw.githubusercontent.com/sveltejs/ai-tools/refs/heads/main/packages/opencode/schema.json",
+	"mcp": {
+		"type": "remote",
+		"enabled": true
+	},
+	"subagent": {
+		"enabled": true
+	},
+	"instructions": {
+		"enabled": true
+	}
+}
+```
+
+### Configuration Options
+
+| Option                 | Type                    | Default    | Description                                                                      |
+| ---------------------- | ----------------------- | ---------- | -------------------------------------------------------------------------------- |
+| `mcp.type`             | `"remote"` \| `"local"` | `"remote"` | Use the remote server at `mcp.svelte.dev` or run locally via `npx @sveltejs/mcp` |
+| `mcp.enabled`          | `boolean`               | `true`     | Enable/disable the MCP server                                                    |
+| `subagent.enabled`     | `boolean`               | `true`     | Enable/disable the Svelte file editor subagent                                   |
+| `instructions.enabled` | `boolean`               | `true`     | Enable/disable agent instructions injection                                      |
+
+### Config File Location
+
+Place your configuration at one of these locations:
+
+- `~/.config/opencode/svelte.json` (global)
+- `$OPENCODE_CONFIG_DIR/svelte.json` (if `OPENCODE_CONFIG_DIR` is set, takes priority)
+
+## License
+
+MIT
--- a/packages/opencode/config.ts
+++ b/packages/opencode/config.ts
@@ -0,0 +1,174 @@
+import type { PluginInput } from '@opencode-ai/plugin';
+import { existsSync, readFileSync } from 'fs';
+import { homedir } from 'os';
+import { join } from 'path';
+import * as v from 'valibot';
+
+const default_config = {
+	mcp: {
+		type: 'remote' as 'remote' | 'local',
+		enabled: true,
+	},
+	subagent: {
+		enabled: true,
+	},
+	instructions: {
+		enabled: true,
+	},
+	skills: {
+		enabled: true,
+	},
+};
+
+export const config_schema = v.object({
+	mcp: v.optional(
+		v.object({
+			type: v.optional(v.picklist(['remote', 'local'])),
+			enabled: v.optional(v.boolean()),
+		}),
+	),
+	subagent: v.optional(
+		v.object({
+			enabled: v.optional(v.boolean()),
+		}),
+	),
+	instructions: v.optional(
+		v.object({
+			enabled: v.optional(v.boolean()),
+		}),
+	),
+	skills: v.optional(
+		v.object({
+			enabled: v.optional(v.boolean()),
+		}),
+	),
+});
+
+export type McpConfig = v.InferInput<typeof config_schema>;
+
+const GLOBAL_CONFIG_DIR = join(homedir(), '.config', 'opencode');
+const GLOBAL_CONFIG_PATH = join(GLOBAL_CONFIG_DIR, 'svelte.json');
+
+interface ConfigLoadResult {
+	data: Record<string, unknown> | null;
+	parse_error?: string;
+}
+
+function get_config_paths() {
+	// Global: ~/.config/opencode/svelte.json
+	let global_path: string | null = null;
+	if (existsSync(GLOBAL_CONFIG_PATH)) {
+		global_path = GLOBAL_CONFIG_PATH;
+	}
+
+	// Custom config directory: $OPENCODE_CONFIG_DIR/svelte.json
+	let config_dir_path: string | null = null;
+	const opencode_config_dir = process.env.OPENCODE_CONFIG_DIR;
+	if (opencode_config_dir) {
+		const config_json = join(opencode_config_dir, 'svelte.json');
+		if (existsSync(config_json)) {
+			config_dir_path = config_json;
+		}
+	}
+
+	// Project-local: ./.opencode/svelte.json (cwd)
+	let project_path: string | null = null;
+	const project_config = join(process.cwd(), '.opencode', 'svelte.json');
+	if (existsSync(project_config)) {
+		project_path = project_config;
+	}
+
+	// Lowest priority first, highest priority last (project overrides global)
+	return [global_path, config_dir_path, project_path];
+}
+
+function load_config_file(config_path: string): ConfigLoadResult {
+	let file_content: string;
+	try {
+		file_content = readFileSync(config_path, 'utf-8');
+	} catch {
+		// File doesn't exist or can't be read
+		return { data: null };
+	}
+
+	try {
+		const parsed = JSON.parse(file_content);
+		if (parsed === undefined || parsed === null) {
+			return { data: null, parse_error: 'Config file is empty or invalid' };
+		}
+		return { data: parsed };
+	} catch (error: unknown) {
+		return {
+			data: null,
+			parse_error: error instanceof Error ? error.message : 'Failed to parse config',
+		};
+	}
+}
+
+function merge_with_defaults(user_config: Partial<McpConfig>): McpConfig {
+	return {
+		mcp: {
+			...default_config.mcp,
+			...user_config.mcp,
+		},
+		subagent: {
+			...default_config.subagent,
+			...user_config.subagent,
+		},
+		instructions: {
+			...default_config.instructions,
+			...user_config.instructions,
+		},
+		skills: {
+			...default_config.skills,
+			...user_config.skills,
+		},
+	};
+}
+
+export function get_mcp_config(ctx: PluginInput) {
+	const config_paths = get_config_paths();
+	let merged: Partial<McpConfig> = {};
+
+	// Iterate from lowest to highest priority, merging as we go
+	for (const path of config_paths) {
+		if (path && existsSync(path)) {
+			const result = load_config_file(path);
+			if (result.parse_error) {
+				setTimeout(() => {
+					ctx.client.tui.showToast({
+						body: {
+							title: 'Svelte: Invalid opencode plugin config',
+							message: `${result.parse_error} (${path})\nSkipping this config file`,
+							variant: 'warning',
+							duration: 7000,
+						},
+					});
+				}, 7000);
+				continue;
+			}
+			const parsed = v.safeParse(config_schema, result.data);
+			if (parsed.success) {
+				merged = {
+					mcp: { ...merged.mcp, ...parsed.output.mcp },
+					subagent: { ...merged.subagent, ...parsed.output.subagent },
+					instructions: { ...merged.instructions, ...parsed.output.instructions },
+					skills: { ...merged.skills, ...parsed.output.skills },
+				};
+			} else {
+				setTimeout(() => {
+					ctx.client.tui.showToast({
+						body: {
+							title: 'Svelte: Invalid opencode plugin config',
+							message: `Invalid config schema (${path})\nSkipping this config file`,
+							variant: 'warning',
+							duration: 7000,
+						},
+					});
+				}, 7000);
+			}
+		}
+	}
+
+	return merge_with_defaults(merged);
+}
--- a/packages/opencode/index.ts
+++ b/packages/opencode/index.ts
@@ -0,0 +1,144 @@
+import type { Plugin } from '@opencode-ai/plugin';
+import { readdir } from 'node:fs/promises';
+import { dirname, join } from 'node:path';
+import { fileURLToPath } from 'node:url';
+import { get_mcp_config } from './config.js';
+
+const current_dir = dirname(fileURLToPath(import.meta.url));
+
+export const svelte_plugin: Plugin = async (ctx) => {
+	return {
+		async config(input) {
+			input.agent ??= {};
+			input.mcp ??= {};
+			input.instructions ??= [];
+			// @ts-expect-error -- types are wrong in the opencode package...will fix there and remove this
+			input.skills ??= {};
+			// @ts-expect-error -- types are wrong in the opencode package...will fix there and remove this
+			input.skills.paths ??= [];
+			// by default we use svelte as the name for the svelte MCP server
+			let svelte_mcp_name = 'svelte';
+			// we loop over every mcp server to see if any of them is already the svelte MCP server
+			for (const name in input.mcp) {
+				const mcp = input.mcp[name];
+				if (
+					(mcp?.type === 'remote' && mcp.url.includes('https://mcp.svelte.dev/mcp')) ||
+					(mcp?.type === 'local' &&
+						mcp.command.some((cmd: string) => cmd.includes('@sveltejs/mcp')))
+				) {
+					// if we found the svelte MCP server, we store its name and break
+					svelte_mcp_name = name;
+					break;
+				}
+			}
+			const mcp_config = get_mcp_config(ctx);
+
+			if (mcp_config.instructions?.enabled !== false) {
+				const instructions_dir = join(current_dir, 'instructions');
+				const instructions_paths = await readdir(instructions_dir);
+				input.instructions.push(...instructions_paths.map((file) => join(instructions_dir, file)));
+			}
+
+			if (mcp_config.skills?.enabled !== false) {
+				const skills_dir = join(current_dir, 'skills');
+				// @ts-expect-error -- skills is a new opencode feature
+				input.skills.paths.push(skills_dir);
+			}
+
+			// if the user doesn't have the MCP server already we add one based on config
+			if (!input.mcp[svelte_mcp_name] && mcp_config.mcp?.enabled !== false) {
+				if (mcp_config.mcp?.type === 'remote') {
+					input.mcp[svelte_mcp_name] = {
+						type: 'remote',
+						url: 'https://mcp.svelte.dev/mcp',
+					};
+				} else {
+					input.mcp[svelte_mcp_name] = {
+						type: 'local',
+						command: ['npx', '-y', '@sveltejs/mcp'],
+					};
+				}
+			}
+			if (mcp_config.subagent?.enabled !== false) {
+				// we add the editor subagent that will be used when editing Svelte files to prevent wasting context on the main agent
+				input.agent['svelte-file-editor'] = {
+					color: '#ff3e00',
+					mode: 'subagent',
+					prompt: `You are a Svelte 5 expert responsible for writing, editing, and validating Svelte components and modules. You have access to the Svelte MCP server which provides documentation and code analysis tools. Always use the tools from the svelte MCP server to fetch documentation with \`get_documentation\` and validating the code with \`svelte_autofixer\`. If the autofixer returns any issue or suggestions try to solve them.
+
+If the MCP tools are not available you can use the \`svelte-code-editor\` skill to learn how to use the \`@sveltejs/mcp\` cli to access the same tools.
+
+If the skill is not available you can run \`npx @sveltejs/mcp@latest -y --help\` to learn how to use it.
+
+## Available MCP Tools
+
+### 1. list-sections
+
+Lists all available Svelte 5 and SvelteKit documentation sections with titles and paths. Use this first to discover what documentation is available.
+
+### 2. get-documentation
+
+Retrieves full documentation for specified sections. Accepts a single section name or an array of section names. Use after \`list-sections\` to fetch relevant docs for the task at hand.
+
+**Example sections:** \`$state\`, \`$derived\`, \`$effect\`, \`$props\`, \`$bindable\`, \`snippets\`, \`routing\`, \`load functions\`
+
+### 3. svelte-autofixer
+
+Analyzes Svelte code and returns suggestions to fix issues. Pass the component code directly to this tool. It will detect common mistakes like:
+
+- Using \`$effect\` instead of \`$derived\` for computations
+- Missing cleanup in effects
+- Svelte 4 syntax (\`on:click\`, \`export let\`, \`<slot>\`)
+- Missing keys in \`{#each}\` blocks
+- And more
+
+## Workflow
+
+When invoked to work on a Svelte file:
+
+### 1. Gather Context (if needed)
+
+If you're uncertain about Svelte 5 syntax or patterns, use the MCP tools:
+
+1. Call \`list-sections\` to see available documentation
+2. Call \`get-documentation\` with relevant section names
+
+### 2. Read the Target File
+
+Read the file to understand the current implementation.
+
+### 3. Make Changes
+
+Apply edits following Svelte 5 best practices:
+
+### 4. Validate Changes
+
+After editing, ALWAYS call \`svelte-autofixer\` with the updated code to check for issues.
+
+### 5. Fix Any Issues
+
+If the autofixer reports problems, fix them and re-validate until no issues remain.
+
+## Output Format
+
+After completing your work, provide:
+
+1. Summary of changes made
+2. Any issues found and fixed by the autofixer
+3. Recommendations for further improvements (if any)
+`,
+					description:
+						'Specialized Svelte 5 code editor. MUST BE USED PROACTIVELY when creating, editing, or reviewing any .svelte file or .svelte.ts/.svelte.js module and MUST use the tools from the MCP server or the `svelte-code-writer` skill if they are available. Fetches relevant documentation and validates code using the Svelte MCP server tools.',
+					permission: {
+						bash: 'ask',
+						edit: 'allow',
+						webfetch: 'ask',
+					},
+					tools: {
+						[`${svelte_mcp_name}_*`]: true,
+					},
+				};
+			}
+		},
+	};
+};
--- a/packages/opencode/instructions/opencode-agents.md
+++ b/packages/opencode/instructions/opencode-agents.md
@@ -0,0 +1,23 @@
+You are able to use the Svelte MCP server, where you have access to comprehensive Svelte 5 and SvelteKit documentation. Here's how to use the available tools effectively:
+
+## Available Svelte MCP Tools:
+
+### 1. list-sections
+
+Use this FIRST to discover all available documentation sections. Returns a structured list with titles, use_cases, and paths.
+When asked about Svelte or SvelteKit topics, ALWAYS use this tool at the start of the chat to find relevant sections.
+
+### 2. get-documentation
+
+Retrieves full documentation content for specific sections. Accepts single or multiple sections.
+After calling the list-sections tool, you MUST analyze the returned documentation sections (especially the use_cases field) and then use the get-documentation tool to fetch ALL documentation sections that are relevant for the user's task.
+
+### 3. svelte-autofixer
+
+Analyzes Svelte code and returns issues and suggestions.
+You MUST use this tool whenever writing Svelte code before sending it to the user. Keep calling it until no issues or suggestions are returned.
+
+### 4. playground-link
+
+Generates a Svelte Playground link with the provided code.
+After completing the code, ask the user if they want a playground link. Only call this tool after user confirmation and NEVER if code was written to files in their project.
--- a/packages/opencode/package.json
+++ b/packages/opencode/package.json
@@ -0,0 +1,36 @@
+{
+	"name": "@sveltejs/opencode",
+	"version": "0.1.3",
+	"type": "module",
+	"license": "MIT",
+	"homepage": "https://github.com/sveltejs/ai-tools#readme",
+	"bugs": {
+		"url": "https://github.com/sveltejs/ai-tools/issues"
+	},
+	"scripts": {
+		"check": "tsc --noEmit",
+		"generate-schema": "node --import node-resolve-ts/register scripts/generate-schema.ts"
+	},
+	"files": [
+		"index.ts",
+		"config.ts",
+		"instructions",
+		"skills"
+	],
+	"repository": {
+		"type": "git",
+		"url": "git+https://github.com/sveltejs/ai-tools.git",
+		"path": "packages/opencode"
+	},
+	"publishConfig": {
+		"access": "public"
+	},
+	"dependencies": {
+		"valibot": "catalog:tooling"
+	},
+	"devDependencies": {
+		"@opencode-ai/plugin": "catalog:ai",
+		"@valibot/to-json-schema": "catalog:tooling",
+		"@types/node": "catalog:tooling"
+	}
+}
--- a/packages/opencode/schema.json
+++ b/packages/opencode/schema.json
@@ -0,0 +1,49 @@
+{
+	"type": "object",
+	"properties": {
+		"mcp": {
+			"type": "object",
+			"properties": {
+				"type": {
+					"enum": [
+						"remote",
+						"local"
+					]
+				},
+				"enabled": {
+					"type": "boolean"
+				}
+			},
+			"required": []
+		},
+		"subagent": {
+			"type": "object",
+			"properties": {
+				"enabled": {
+					"type": "boolean"
+				}
+			},
+			"required": []
+		},
+		"instructions": {
+			"type": "object",
+			"properties": {
+				"enabled": {
+					"type": "boolean"
+				}
+			},
+			"required": []
+		},
+		"skills": {
+			"type": "object",
+			"properties": {
+				"enabled": {
+					"type": "boolean"
+				}
+			},
+			"required": []
+		}
+	},
+	"required": [],
+	"$schema": "http://json-schema.org/draft-07/schema#"
+}
--- a/packages/opencode/scripts/generate-schema.ts
+++ b/packages/opencode/scripts/generate-schema.ts
@@ -0,0 +1,8 @@
+import { toJsonSchema } from '@valibot/to-json-schema';
+import { config_schema } from '../config.js';
+import fs from 'node:fs';
+import path from 'node:path';
+
+const json_schema = toJsonSchema(config_schema);
+
+fs.writeFileSync(path.resolve('./schema.json'), JSON.stringify(json_schema, null, '\t'));
--- a/packages/opencode/skills/svelte-code-writer/SKILL.md
+++ b/packages/opencode/skills/svelte-code-writer/SKILL.md
@@ -0,0 +1,66 @@
+---
+name: svelte-code-writer
+description: CLI tools for Svelte 5 documentation lookup and code analysis. MUST be used whenever creating, editing or analyzing any Svelte component (.svelte) or Svelte module (.svelte.ts/.svelte.js). If possible, this skill should be executed within the svelte-file-editor agent for optimal results.
+---
+
+# Svelte 5 Code Writer
+
+## CLI Tools
+
+You have access to `@sveltejs/mcp` CLI for Svelte-specific assistance. Use these commands via `npx`:
+
+### List Documentation Sections
+
+```bash
+npx @sveltejs/mcp list-sections
+```
+
+Lists all available Svelte 5 and SvelteKit documentation sections with titles and paths.
+
+### Get Documentation
+
+```bash
+npx @sveltejs/mcp get-documentation "<section1>,<section2>,..."
+```
+
+Retrieves full documentation for specified sections. Use after `list-sections` to fetch relevant docs.
+
+**Example:**
+
+```bash
+npx @sveltejs/mcp get-documentation "$state,$derived,$effect"
+```
+
+### Svelte Autofixer
+
+```bash
+npx @sveltejs/mcp svelte-autofixer "<code_or_path>" [options]
+```
+
+Analyzes Svelte code and suggests fixes for common issues.
+
+**Options:**
+
+- `--async` - Enable async Svelte mode (default: false)
+- `--svelte-version` - Target version: 4 or 5 (default: 5)
+
+**Examples:**
+
+```bash
+# Analyze inline code (escape $ as \$)
+npx @sveltejs/mcp svelte-autofixer '<script>let count = \$state(0);</script>'
+
+# Analyze a file
+npx @sveltejs/mcp svelte-autofixer ./src/lib/Component.svelte
+
+# Target Svelte 4
+npx @sveltejs/mcp svelte-autofixer ./Component.svelte --svelte-version 4
+```
+
+**Important:** When passing code with runes (`$state`, `$derived`, etc.) via the terminal, escape the `$` character as `\$` to prevent shell variable substitution.
+
+## Workflow
+
+1. **Uncertain about syntax?** Run `list-sections` then `get-documentation` for relevant topics
+2. **Reviewing/debugging?** Run `svelte-autofixer` on the code to detect issues
+3. **Always validate** - Run `svelte-autofixer` before finalizing any Svelte component
--- a/packages/opencode/tsconfig.json
+++ b/packages/opencode/tsconfig.json
@@ -0,0 +1,5 @@
+{
+	"extends": "../../tsconfig.json",
+	"include": ["index.ts", "config.ts", "scripts/*"],
+	"exclude": ["node_modules"]
+}
--- a/plugins/svelte/.claude-plugin/plugin.json
+++ b/plugins/svelte/.claude-plugin/plugin.json
@@ -0,0 +1,17 @@
+{
+	"name": "svelte",
+	"description": "A plugin for all things related to Svelte development, MCP, skills, and more.",
+	"version": "1.0.1",
+	"author": {
+		"name": "Svelte"
+	},
+	"lspServers": {
+		"svelte": {
+			"command": "svelteserver",
+			"args": ["--stdio"],
+			"extensionToLanguage": {
+				".svelte": "svelte"
+			}
+		}
+	}
+}
--- a/plugins/svelte/.mcp.json
+++ b/plugins/svelte/.mcp.json
@@ -0,0 +1,8 @@
+{
+	"mcpServers": {
+		"svelte": {
+			"type": "http",
+			"url": "https://mcp.svelte.dev/mcp"
+		}
+	}
+}
--- a/plugins/svelte/agents/svelte-file-editor.md
+++ b/plugins/svelte/agents/svelte-file-editor.md
@@ -0,0 +1,68 @@
+---
+name: svelte-file-editor
+description: Specialized Svelte 5 code editor. MUST BE USED PROACTIVELY when creating, editing, or reviewing any .svelte file or .svelte.ts/.svelte.js module and MUST use the tools from the MCP server or the `svelte-file-editor` skill if they are available. Fetches relevant documentation and validates code using the Svelte MCP server tools.
+permissionMode: acceptEdits
+---
+
+You are a Svelte 5 expert responsible for writing, editing, and validating Svelte components and modules. You have access to the Svelte MCP server which provides documentation and code analysis tools. Always use the tools from the svelte MCP server to fetch documentation with `get_documentation` and validating the code with `svelte_autofixer`. If the autofixer returns any issue or suggestions try to solve them.
+
+If the MCP tools are not available you can use the `svelte-code-editor` skill to learn how to use the `@sveltejs/mcp` cli to access the same tools.
+
+If the skill is not available you can run `npx @sveltejs/mcp@latest -y --help` to learn how to use it.
+
+## Available MCP Tools
+
+### 1. list-sections
+
+Lists all available Svelte 5 and SvelteKit documentation sections with titles and paths. Use this first to discover what documentation is available.
+
+### 2. get-documentation
+
+Retrieves full documentation for specified sections. Accepts a single section name or an array of section names. Use after `list-sections` to fetch relevant docs for the task at hand.
+
+**Example sections:** `$state`, `$derived`, `$effect`, `$props`, `$bindable`, `snippets`, `routing`, `load functions`
+
+### 3. svelte-autofixer
+
+Analyzes Svelte code and returns suggestions to fix issues. Pass the component code directly to this tool. It will detect common mistakes like:
+
+- Using `$effect` instead of `$derived` for computations
+- Missing cleanup in effects
+- Svelte 4 syntax (`on:click`, `export let`, `<slot>`)
+- Missing keys in `{#each}` blocks
+- And more
+
+## Workflow
+
+When invoked to work on a Svelte file:
+
+### 1. Gather Context (if needed)
+
+If you're uncertain about Svelte 5 syntax or patterns, use the MCP tools:
+
+1. Call `list-sections` to see available documentation
+2. Call `get-documentation` with relevant section names
+
+### 2. Read the Target File
+
+Read the file to understand the current implementation.
+
+### 3. Make Changes
+
+Apply edits following Svelte 5 best practices:
+
+### 4. Validate Changes
+
+After editing, ALWAYS call `svelte-autofixer` with the updated code to check for issues.
+
+### 5. Fix Any Issues
+
+If the autofixer reports problems, fix them and re-validate until no issues remain.
+
+## Output Format
+
+After completing your work, provide:
+
+1. Summary of changes made
+2. Any issues found and fixed by the autofixer
+3. Recommendations for further improvements (if any)
--- a/plugins/svelte/skills/svelte-code-writer/SKILL.md
+++ b/plugins/svelte/skills/svelte-code-writer/SKILL.md
@@ -0,0 +1,66 @@
+---
+name: svelte-code-writer
+description: CLI tools for Svelte 5 documentation lookup and code analysis. MUST be used whenever creating, editing or analyzing any Svelte component (.svelte) or Svelte module (.svelte.ts/.svelte.js). If possible, this skill should be executed within the svelte-file-editor agent for optimal results.
+---
+
+# Svelte 5 Code Writer
+
+## CLI Tools
+
+You have access to `@sveltejs/mcp` CLI for Svelte-specific assistance. Use these commands via `npx`:
+
+### List Documentation Sections
+
+```bash
+npx @sveltejs/mcp list-sections
+```
+
+Lists all available Svelte 5 and SvelteKit documentation sections with titles and paths.
+
+### Get Documentation
+
+```bash
+npx @sveltejs/mcp get-documentation "<section1>,<section2>,..."
+```
+
+Retrieves full documentation for specified sections. Use after `list-sections` to fetch relevant docs.
+
+**Example:**
+
+```bash
+npx @sveltejs/mcp get-documentation "$state,$derived,$effect"
+```
+
+### Svelte Autofixer
+
+```bash
+npx @sveltejs/mcp svelte-autofixer "<code_or_path>" [options]
+```
+
+Analyzes Svelte code and suggests fixes for common issues.
+
+**Options:**
+
+- `--async` - Enable async Svelte mode (default: false)
+- `--svelte-version` - Target version: 4 or 5 (default: 5)
+
+**Examples:**
+
+```bash
+# Analyze inline code (escape $ as \$)
+npx @sveltejs/mcp svelte-autofixer '<script>let count = \$state(0);</script>'
+
+# Analyze a file
+npx @sveltejs/mcp svelte-autofixer ./src/lib/Component.svelte
+
+# Target Svelte 4
+npx @sveltejs/mcp svelte-autofixer ./Component.svelte --svelte-version 4
+```
+
+**Important:** When passing code with runes (`$state`, `$derived`, etc.) via the terminal, escape the `$` character as `\$` to prevent shell variable substitution.
+
+## Workflow
+
+1. **Uncertain about syntax?** Run `list-sections` then `get-documentation` for relevant topics
+2. **Reviewing/debugging?** Run `svelte-autofixer` on the code to detect issues
+3. **Always validate** - Run `svelte-autofixer` before finalizing any Svelte component
--- a/pnpm-lock.yaml
+++ b/pnpm-lock.yaml
--- a/pnpm-workspace.yaml
+++ b/pnpm-workspace.yaml
@@ -5,8 +5,9 @@ packages:
 catalogs:
  ai:
    '@anthropic-ai/sdk': ^0.71.0
-    '@mcp-ui/server': ^5.12.0
-    '@modelcontextprotocol/inspector': ^0.18.0
+    '@mcp-ui/server': ^6.0.0
+    '@modelcontextprotocol/inspector': ^0.19.0
+    '@opencode-ai/plugin': ^1.1.44
  lint:
    '@eslint/compat': ^2.0.0
    '@eslint/js': ^9.36.0
@@ -18,24 +19,24 @@ catalogs:
    eslint-plugin-import: ^2.32.0
    eslint-plugin-pnpm: ^1.3.0
    eslint-plugin-svelte: ^3.12.5
-    globals: ^16.0.0
+    globals: ^17.0.0
    prettier: ^3.4.2
    prettier-plugin-svelte: ^3.3.3
    svelte-eslint-parser: ^1.4.0
    typescript-eslint: ^8.44.0
  orm:
-    '@libsql/client': ^0.15.0
+    '@libsql/client': ^0.17.0
    drizzle-kit: ^0.31.0
    drizzle-orm: ^0.45.0
  svelte:
    '@sveltejs/adapter-vercel': ^6.0.0
    '@sveltejs/kit': ^2.42.2
    '@sveltejs/vite-plugin-svelte': ^6.0.0
-    svelte: ^5.39.2
+    svelte: ^5.47.0
    svelte-check: ^4.0.0
  tmcp:
    '@tmcp/adapter-valibot': ^0.1.4
-    '@tmcp/transport-http': ^0.8.3
+    '@tmcp/transport-http': ^0.8.4
    '@tmcp/transport-in-memory': ^0.0.5
    '@tmcp/transport-stdio': ^0.4.0
    tmcp: ^1.19.0
@@ -44,14 +45,16 @@ catalogs:
    '@svitejs/changesets-changelog-github-compact': ^1.2.0
    '@types/estree': ^1.0.8
    '@types/node': ^24.3.1
+    '@valibot/to-json-schema': ^1.5.0
    '@vercel/analytics': ^1.5.0
    dotenv: ^17.2.3
    node-resolve-ts: ^1.0.2
    publint: ^0.3.13
-    ts-blank-space: ^0.6.2
-    tsdown: ^0.18.0
+    sade: 1.8.1
+    ts-blank-space: ^0.7.0
+    tsdown: ^0.20.0
    typescript: ^5.0.0
-    valibot: ^1.1.0
+    valibot: ^1.2.0
    vite: ^7.0.4
    vite-plugin-devtools-json: ^1.0.0
    vitest: ^4.0.0
--- a/scripts/sync-cursor-plugin.ts
+++ b/scripts/sync-cursor-plugin.ts
@@ -0,0 +1,85 @@
+import fs from 'node:fs/promises';
+import path from 'node:path';
+
+const CURSOR_PLUGIN_DIR = './svelte-cursor';
+const CLAUDE_PLUGIN_DIR = './plugins/svelte';
+const AGENTS_MD_PATH = './instructions/AGENTS.md';
+
+/**
+ * Sync skills from Claude plugin to Cursor plugin (direct copy)
+ */
+async function sync_skills() {
+	const source = path.join(CLAUDE_PLUGIN_DIR, 'skills');
+	const dest = path.join(CURSOR_PLUGIN_DIR, 'skills');
+
+	await fs.rm(dest, { recursive: true, force: true });
+	await fs.cp(source, dest, { recursive: true });
+
+	console.log('Synced skills to Cursor plugin');
+}
+
+/**
+ * Sync agent definition from Claude plugin to Cursor plugin,
+ * stripping Claude-specific frontmatter fields (permissionMode)
+ */
+async function sync_agents() {
+	const source = path.join(CLAUDE_PLUGIN_DIR, 'agents');
+	const dest = path.join(CURSOR_PLUGIN_DIR, 'agents');
+
+	await fs.rm(dest, { recursive: true, force: true });
+	await fs.mkdir(dest, { recursive: true });
+
+	const files = await fs.readdir(source);
+
+	for (const file of files) {
+		if (!file.endsWith('.md')) continue;
+
+		const content = await fs.readFile(path.join(source, file), 'utf-8');
+
+		// Strip Claude-specific frontmatter fields
+		const transformed = content.replace(
+			/^(---\n)([\s\S]*?)(---\n)/m,
+			(_match, open, frontmatter, close) => {
+				const filtered_lines = (frontmatter as string)
+					.split('\n')
+					.filter((line: string) => !line.startsWith('permissionMode:'))
+					.join('\n');
+				return `${open}${filtered_lines}${close}`;
+			},
+		);
+
+		await fs.writeFile(path.join(dest, file), transformed);
+	}
+
+	console.log('Synced agents to Cursor plugin');
+}
+
+/**
+ * Sync AGENTS.md instructions as a Cursor rule (.mdc file with frontmatter)
+ */
+async function sync_rules() {
+	const dest = path.join(CURSOR_PLUGIN_DIR, 'rules');
+
+	await fs.rm(dest, { recursive: true, force: true });
+	await fs.mkdir(dest, { recursive: true });
+
+	const agents_content = await fs.readFile(AGENTS_MD_PATH, 'utf-8');
+
+	const rule_content = `---
+description: Instructions for using the Svelte MCP server tools for documentation lookup, code analysis, and validation
+alwaysApply: true
+---
+
+${agents_content.trim()}
+`;
+
+	await fs.writeFile(path.join(dest, 'svelte-mcp-tools.mdc'), rule_content);
+
+	console.log('Synced rules to Cursor plugin');
+}
+
+await sync_skills();
+await sync_agents();
+await sync_rules();
+
+console.log('Cursor plugin sync complete');
--- a/scripts/update-docs-prompts.ts
+++ b/scripts/update-docs-prompts.ts
@@ -1,13 +1,7 @@
 import fs from 'node:fs/promises';
 import path from 'node:path';

-let content = `---
-title: Prompts
---
-
-This is the list of available prompts provided by the MCP server. Prompts are selected by the user and are sent as a user message. They can be useful to write repetitive instructions for the LLM on how to properly use the MCP server.
-
-`;
+let content = '';

 const prompts_generators = fs.glob('./packages/mcp-server/src/mcp/handlers/prompts/*.ts');

@@ -33,4 +27,6 @@ ${await module.generate_for_docs()}
 `;
 }

-await fs.writeFile('./documentation/docs/30-capabilities/30-prompts.md', content.trim() + '\n');
+const generated_dir = './documentation/docs/30-capabilities/.generated';
+await fs.mkdir(generated_dir, { recursive: true });
+await fs.writeFile(path.join(generated_dir, 'prompts.md'), content.trim() + '\n');
--- a/scripts/update-docs-skills.ts
+++ b/scripts/update-docs-skills.ts
@@ -0,0 +1,92 @@
+import fs from 'node:fs/promises';
+import path from 'node:path';
+
+interface SkillFrontmatter {
+	name: string;
+	description: string;
+}
+
+function get_backtick_fence(content: string): string {
+	const backtick_pattern = /`{3,}/g;
+	let max_backticks = 3;
+
+	let match;
+	while ((match = backtick_pattern.exec(content)) !== null) {
+		max_backticks = Math.max(max_backticks, match[0].length);
+	}
+
+	return '`'.repeat(max_backticks + 1);
+}
+
+function parse_frontmatter(
+	content: string,
+): { frontmatter: SkillFrontmatter; body: string } | null {
+	const match = content.match(/^---\n([\s\S]*?)\n---\n([\s\S]*)$/);
+	if (!match) return null;
+
+	const frontmatter_str = match[1];
+	const body = match[2];
+
+	if (!frontmatter_str || body === undefined) return null;
+
+	const frontmatter: Record<string, string> = {};
+
+	for (const line of frontmatter_str.split('\n')) {
+		const [key, ...value_parts] = line.split(':');
+		if (key && value_parts.length > 0) {
+			frontmatter[key.trim()] = value_parts.join(':').trim();
+		}
+	}
+
+	return {
+		frontmatter: frontmatter as unknown as SkillFrontmatter,
+		body: body.trim(),
+	};
+}
+
+let content = '';
+
+const skills_dir = './plugins/svelte/skills';
+const skill_dirs = (await fs.readdir(skills_dir)).filter((name) => !name.startsWith('.'));
+
+for (const skill_name of skill_dirs) {
+	const skill_path = path.join(skills_dir, skill_name, 'SKILL.md');
+
+	try {
+		const skill_content = await fs.readFile(skill_path, 'utf-8');
+		const parsed = parse_frontmatter(skill_content);
+
+		if (!parsed) {
+			console.warn(`Warning: Could not parse frontmatter for ${skill_name}`);
+			continue;
+		}
+
+		const { frontmatter, body } = parsed;
+		const fence = get_backtick_fence(body);
+
+		content += `## \`${frontmatter.name}\`
+
+${frontmatter.description}
+
+<a href="https://github.com/sveltejs/ai-tools/releases?q=${frontmatter.name}" target="_blank" rel="noopener noreferrer">Open Releases page</a>
+
+<details>
+	<summary>View skill content</summary>
+
+<!-- prettier-ignore-start -->
+${fence}markdown
+${body}
+${fence}
+<!-- prettier-ignore-end -->
+
+</details>
+
+`;
+	} catch {
+		console.warn(`Warning: Could not read skill at ${skill_path}`);
+	}
+}
+
+const generated_dir = './documentation/docs/60-skills/.generated';
+await fs.mkdir(generated_dir, { recursive: true });
+await fs.writeFile(path.join(generated_dir, 'skills.md'), content.trim() + '\n');
--- a/svelte-cursor/.cursor-plugin/plugin.json
+++ b/svelte-cursor/.cursor-plugin/plugin.json
@@ -0,0 +1,9 @@
+{
+	"name": "svelte",
+	"description": "A plugin for all things related to Svelte development, MCP, skills, and more.",
+	"version": "1.0.0",
+	"author": {
+		"name": "Svelte"
+	},
+	"keywords": ["svelte", "sveltekit", "mcp", "autofixer"]
+}
--- a/svelte-cursor/.mcp.json
+++ b/svelte-cursor/.mcp.json
@@ -0,0 +1,8 @@
+{
+	"mcpServers": {
+		"svelte": {
+			"type": "http",
+			"url": "https://mcp.svelte.dev/mcp"
+		}
+	}
+}
--- a/svelte-cursor/agents/svelte-file-editor.md
+++ b/svelte-cursor/agents/svelte-file-editor.md
@@ -0,0 +1,67 @@
+---
+name: svelte-file-editor
+description: Specialized Svelte 5 code editor. MUST BE USED PROACTIVELY when creating, editing, or reviewing any .svelte file or .svelte.ts/.svelte.js module and MUST use the tools from the MCP server or the `svelte-file-editor` skill if they are available. Fetches relevant documentation and validates code using the Svelte MCP server tools.
+---
+
+You are a Svelte 5 expert responsible for writing, editing, and validating Svelte components and modules. You have access to the Svelte MCP server which provides documentation and code analysis tools. Always use the tools from the svelte MCP server to fetch documentation with `get_documentation` and validating the code with `svelte_autofixer`. If the autofixer returns any issue or suggestions try to solve them.
+
+If the MCP tools are not available you can use the `svelte-code-editor` skill to learn how to use the `@sveltejs/mcp` cli to access the same tools.
+
+If the skill is not available you can run `npx @sveltejs/mcp@latest -y --help` to learn how to use it.
+
+## Available MCP Tools
+
+### 1. list-sections
+
+Lists all available Svelte 5 and SvelteKit documentation sections with titles and paths. Use this first to discover what documentation is available.
+
+### 2. get-documentation
+
+Retrieves full documentation for specified sections. Accepts a single section name or an array of section names. Use after `list-sections` to fetch relevant docs for the task at hand.
+
+**Example sections:** `$state`, `$derived`, `$effect`, `$props`, `$bindable`, `snippets`, `routing`, `load functions`
+
+### 3. svelte-autofixer
+
+Analyzes Svelte code and returns suggestions to fix issues. Pass the component code directly to this tool. It will detect common mistakes like:
+
+- Using `$effect` instead of `$derived` for computations
+- Missing cleanup in effects
+- Svelte 4 syntax (`on:click`, `export let`, `<slot>`)
+- Missing keys in `{#each}` blocks
+- And more
+
+## Workflow
+
+When invoked to work on a Svelte file:
+
+### 1. Gather Context (if needed)
+
+If you're uncertain about Svelte 5 syntax or patterns, use the MCP tools:
+
+1. Call `list-sections` to see available documentation
+2. Call `get-documentation` with relevant section names
+
+### 2. Read the Target File
+
+Read the file to understand the current implementation.
+
+### 3. Make Changes
+
+Apply edits following Svelte 5 best practices:
+
+### 4. Validate Changes
+
+After editing, ALWAYS call `svelte-autofixer` with the updated code to check for issues.
+
+### 5. Fix Any Issues
+
+If the autofixer reports problems, fix them and re-validate until no issues remain.
+
+## Output Format
+
+After completing your work, provide:
+
+1. Summary of changes made
+2. Any issues found and fixed by the autofixer
+3. Recommendations for further improvements (if any)
--- a/svelte-cursor/rules/svelte-mcp-tools.mdc
+++ b/svelte-cursor/rules/svelte-mcp-tools.mdc
@@ -0,0 +1,28 @@
+---
+description: Instructions for using the Svelte MCP server tools for documentation lookup, code analysis, and validation
+alwaysApply: true
+---
+
+You are able to use the Svelte MCP server, where you have access to comprehensive Svelte 5 and SvelteKit documentation. Here's how to use the available tools effectively:
+
+## Available Svelte MCP Tools:
+
+### 1. list-sections
+
+Use this FIRST to discover all available documentation sections. Returns a structured list with titles, use_cases, and paths.
+When asked about Svelte or SvelteKit topics, ALWAYS use this tool at the start of the chat to find relevant sections.
+
+### 2. get-documentation
+
+Retrieves full documentation content for specific sections. Accepts single or multiple sections.
+After calling the list-sections tool, you MUST analyze the returned documentation sections (especially the use_cases field) and then use the get-documentation tool to fetch ALL documentation sections that are relevant for the user's task.
+
+### 3. svelte-autofixer
+
+Analyzes Svelte code and returns issues and suggestions.
+You MUST use this tool whenever writing Svelte code before sending it to the user. Keep calling it until no issues or suggestions are returned.
+
+### 4. playground-link
+
+Generates a Svelte Playground link with the provided code.
+After completing the code, ask the user if they want a playground link. Only call this tool after user confirmation and NEVER if code was written to files in their project.
--- a/svelte-cursor/skills/svelte-code-writer/SKILL.md
+++ b/svelte-cursor/skills/svelte-code-writer/SKILL.md
@@ -0,0 +1,66 @@
+---
+name: svelte-code-writer
+description: CLI tools for Svelte 5 documentation lookup and code analysis. MUST be used whenever creating, editing or analyzing any Svelte component (.svelte) or Svelte module (.svelte.ts/.svelte.js). If possible, this skill should be executed within the svelte-file-editor agent for optimal results.
+---
+
+# Svelte 5 Code Writer
+
+## CLI Tools
+
+You have access to `@sveltejs/mcp` CLI for Svelte-specific assistance. Use these commands via `npx`:
+
+### List Documentation Sections
+
+```bash
+npx @sveltejs/mcp list-sections
+```
+
+Lists all available Svelte 5 and SvelteKit documentation sections with titles and paths.
+
+### Get Documentation
+
+```bash
+npx @sveltejs/mcp get-documentation "<section1>,<section2>,..."
+```
+
+Retrieves full documentation for specified sections. Use after `list-sections` to fetch relevant docs.
+
+**Example:**
+
+```bash
+npx @sveltejs/mcp get-documentation "$state,$derived,$effect"
+```
+
+### Svelte Autofixer
+
+```bash
+npx @sveltejs/mcp svelte-autofixer "<code_or_path>" [options]
+```
+
+Analyzes Svelte code and suggests fixes for common issues.
+
+**Options:**
+
+- `--async` - Enable async Svelte mode (default: false)
+- `--svelte-version` - Target version: 4 or 5 (default: 5)
+
+**Examples:**
+
+```bash
+# Analyze inline code (escape $ as \$)
+npx @sveltejs/mcp svelte-autofixer '<script>let count = \$state(0);</script>'
+
+# Analyze a file
+npx @sveltejs/mcp svelte-autofixer ./src/lib/Component.svelte
+
+# Target Svelte 4
+npx @sveltejs/mcp svelte-autofixer ./Component.svelte --svelte-version 4
+```
+
+**Important:** When passing code with runes (`$state`, `$derived`, etc.) via the terminal, escape the `$` character as `\$` to prevent shell variable substitution.
+
+## Workflow
+
+1. **Uncertain about syntax?** Run `list-sections` then `get-documentation` for relevant topics
+2. **Reviewing/debugging?** Run `svelte-autofixer` on the code to detect issues
+3. **Always validate** - Run `svelte-autofixer` before finalizing any Svelte component
Author	SHA1	Message	Date
paoloricciuti	6ab8ecd9fd	fix: rename title	2026-02-27 19:53:47 +01:00
paoloricciuti	db78f6c230	fix: rename repos in file	2026-02-27 19:35:02 +01:00
github-actions[bot]	02935b00a6	Version Packages (#164 ) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>	2026-02-22 15:05:33 +01:00
Paolo Ricciuti	1ea98adacd	feat: cursor plugin (#166 )	2026-02-22 15:02:31 +01:00
Paolo Ricciuti	494409cc42	fix: better subagent instructions to use MCP or skill (#163 )	2026-02-11 22:57:09 +01:00
Paolo Ricciuti	46d8f6cce8	fix: only run "Publish to MCP registry" when MCP is published (#160 )	2026-02-07 22:50:08 +01:00
github-actions[bot]	8dc63dca08	chore: sync skills and update documentation (#158 ) Co-authored-by: paoloricciuti <26281609+paoloricciuti@users.noreply.github.com>	2026-02-06 18:41:18 +01:00
paoloricciuti	19fedcd35f	docs: add `instructions` to default schema`	2026-02-06 18:40:55 +01:00
István Pató	b4eb5cc960	Update description for svelte-code-writer skill (#149 )	2026-02-06 18:37:40 +01:00
paoloricciuti	6676fd8116	docs: add local opencode configuration	2026-02-06 18:37:03 +01:00
github-actions[bot]	a755a33a5f	Version Packages (#157 ) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>	2026-02-06 17:30:56 +01:00
Paolo Ricciuti	556f96cfaf	feat: allow for local opencode config (#156 )	2026-02-06 17:25:33 +01:00
github-actions[bot]	77a3340c2f	chore: sync AGENTS.md to opencode package and documentation (#155 ) Co-authored-by: paoloricciuti <26281609+paoloricciuti@users.noreply.github.com>	2026-02-06 17:11:38 +01:00
Paolo Ricciuti	9ac8fd51e7	chore: sync `AGENTS.md` with opencode and docs (#154 ) Co-authored-by: jyc.dev <jycouet@gmail.com>	2026-02-06 17:10:42 +01:00
paoloricciuti	c764308d79	fix: update version of claude plugin	2026-01-31 10:02:31 +01:00
paoloricciuti	01a7e6a8d3	fix: correct command for svelte language server	2026-01-31 09:52:57 +01:00
Paolo Ricciuti	d8ed686e3a	chore: use `@include` in docs (#152 )	2026-01-30 16:30:52 -05:00
github-actions[bot]	6f0390d0a9	Version Packages (#153 ) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>	2026-01-30 16:23:09 +01:00
paoloricciuti	c2c1b3e5e7	fix: actually push skills to right config path	2026-01-30 16:20:36 +01:00
github-actions[bot]	cdfbb907b6	Version Packages (#147 ) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>	2026-01-30 16:03:12 +01:00
Paolo Ricciuti	2eb2b18008	feat: distribute skills through opencode plugin (#151 )	2026-01-30 15:52:35 +01:00
renovate[bot]	e8554f3d8f	chore(deps): update all non-major dependencies (#137 ) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: paoloricciuti <ricciutipaolo@gmail.com>	2026-01-27 22:19:34 +01:00
Christopher Harrison	0213bd951f	Add Copilot CLI setup instructions (#148 )	2026-01-27 22:05:30 +01:00
paoloricciuti	2245cb2dc9	fix: turn off no-inspect in eslint for mcp	2026-01-27 16:25:30 +01:00
renovate[bot]	2a5f7d6314	chore(deps): update dependency @mcp-ui/server to v6 (#146 ) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: paoloricciuti <ricciutipaolo@gmail.com>	2026-01-27 16:11:09 +01:00
paoloricciuti	8518e627d3	chore: remove logs	2026-01-23 18:41:14 +01:00
paoloricciuti	9e824da9e2	chore: better debug logs	2026-01-23 18:32:54 +01:00
paoloricciuti	b38f2c11da	fix: debug log	2026-01-23 18:28:37 +01:00
paoloricciuti	ea37c7120c	chore: use new `disableSee` option in `tmcp`	2026-01-23 07:58:36 +01:00
paoloricciuti	099e939f79	fix: remove log duh	2026-01-22 23:50:37 +01:00
paoloricciuti	69b36eefdc	fix: return 405 for SSE stream instead of closing immediately	2026-01-22 23:47:59 +01:00
github-actions[bot]	15ad554f53	Version Packages (#145 ) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>	2026-01-19 15:56:05 +01:00
paoloricciuti	74477448ce	chore: update svelte	2026-01-19 15:52:46 +01:00
github-actions[bot]	6f538265d1	Version Packages (#144 ) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>	2026-01-17 15:21:24 +01:00
paoloricciuti	71295bc11f	chore: add README to opencode plugin	2026-01-17 15:20:11 +01:00
Rich Harris	b5040ff5cf	docs: tweak Claude Code documentation (#143 ) Co-authored-by: Paolo Ricciuti <ricciutipaolo@gmail.com>	2026-01-17 01:04:32 +01:00
github-actions[bot]	45c961417f	Version Packages (#141 ) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>	2026-01-16 19:26:42 +01:00
paoloricciuti	57e2d1def1	fix: show toast after a few seconds to avoid race condition	2026-01-16 19:21:42 +01:00
Paolo Ricciuti	398a703580	feat: opencode plugin (#142 ) Co-authored-by: Rich Harris <hello@rich-harris.dev>	2026-01-16 12:41:02 -05:00
Paolo Ricciuti	75c802a115	feat: add lsp config for claude plugin (#140 )	2026-01-15 15:00:38 +01:00
Paolo Ricciuti	53a634cdb0	feat: expose playground link as MCP App (#138 )	2026-01-15 14:59:46 +01:00
paoloricciuti	bcdc33e7a5	fix: automatically accept edits in the svelte file editor agent	2026-01-05 22:18:46 +01:00
github-actions[bot]	825ae33427	Version Packages (#136 ) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>	2026-01-05 09:43:10 +01:00
Paolo Ricciuti	ccf940cc45	feat: claude skill + marketplace (#110 ) Co-authored-by: Stanislav Khromov <stanislav.khromov+github@gmail.com>	2026-01-04 23:00:03 +01:00
Paolo Ricciuti	b2f195fb7b	fix: add suggestion for snippets declared in script tag (#132 )	2026-01-04 12:00:33 +01:00
renovate[bot]	d8e4b18bff	chore(deps): update pnpm to v10.27.0 (#133 ) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>	2026-01-03 15:40:19 +01:00
renovate[bot]	6a2198b433	chore(deps): update dependency globals to v17 (#134 ) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>	2026-01-03 15:40:10 +01:00
renovate[bot]	2ce60c6110	chore(deps): update pnpm to v10.26.2 (#131 ) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>	2025-12-30 14:26:52 +01:00
github-actions[bot]	0f8987fdcf	Version Packages (#130 ) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>	2025-12-22 00:18:38 +01:00
Paolo Ricciuti	42911e2631	feat: expose tools as JS api + cli (#128 )	2025-12-22 00:16:36 +01:00