Add skills guide and update skills

.prettierignore

@@ -1,4 +1,6 @@
+# Ignore files for skills
 /.agents/skills
+skills-lock.json
 
 # Ignore files for PNPM, NPM and YARN
 pnpm-lock.yaml

.zed/settings.json

@@ -0,0 +1,8 @@
+{
+	"context_servers": {
+		"Svelte": {
+			"command": "npx",
+			"args": ["-y", "@sveltejs/mcp"]
+		}
+	}
+}

package.json

@@ -17,7 +17,7 @@
 	"devDependencies": {
 		"@content-collections/core": "^0.15.0",
 		"@content-collections/vite": "^0.3.0",
-		"@eslint/compat": "^2.0.5",
+		"@eslint/compat": "^2.1.0",
 		"@eslint/js": "^10.0.1",
 		"@fontsource/roboto": "^5.2.10",
 		"@fontsource/spectral": "^5.2.8",
@@ -29,8 +29,8 @@
 		"@sveltejs/enhanced-img": "^0.10.4",
 		"@sveltejs/kit": "^2.59.1",
 		"@sveltejs/vite-plugin-svelte": "^7.1.2",
-		"@tailwindcss/vite": "^4.2.4",
-		"@types/node": "^25.6.1",
+		"@tailwindcss/vite": "^4.3.0",
+		"@types/node": "^25.6.2",
 		"d3-array": "^3.2.4",
 		"dotenv": "^17.4.2",
 		"eslint": "^10.3.0",
@@ -48,7 +48,7 @@
 		"svelte-check": "^4.4.8",
 		"sveltekit-embed": "^0.0.22",
 		"tailwind-merge": "^3.5.0",
-		"tailwindcss": "^4.2.4",
+		"tailwindcss": "^4.3.0",
 		"typescript": "^6.0.3",
 		"typescript-eslint": "^8.59.2",
 		"vite": "^8.0.11",

skills-lock.json

@@ -1,15 +1,17 @@
 {
-	"version": 1,
-	"skills": {
-		"svelte-code-writer": {
-			"source": "sveltejs/ai-tools",
-			"sourceType": "github",
-			"computedHash": "c0e2cce9855f8e312cbb0a05aef164b4659c672d7723e4e598ffa6bc94890542"
-		},
-		"svelte-core-bestpractices": {
-			"source": "sveltejs/ai-tools",
-			"sourceType": "github",
-			"computedHash": "bec11e369679027edf9d4acbe6d9788f8da33dc14b48b874f231d3ba13705324"
-		}
-	}
+  "version": 1,
+  "skills": {
+    "svelte-code-writer": {
+      "source": "sveltejs/ai-tools",
+      "sourceType": "github",
+      "skillPath": "plugins/claude/svelte/skills/svelte-code-writer/SKILL.md",
+      "computedHash": "c0e2cce9855f8e312cbb0a05aef164b4659c672d7723e4e598ffa6bc94890542"
+    },
+    "svelte-core-bestpractices": {
+      "source": "sveltejs/ai-tools",
+      "sourceType": "github",
+      "skillPath": "plugins/claude/svelte/skills/svelte-core-bestpractices/SKILL.md",
+      "computedHash": "bec11e369679027edf9d4acbe6d9788f8da33dc14b48b874f231d3ba13705324"
+    }
+  }
 }

src/routes/guides/skills/+page.md

@@ -0,0 +1,79 @@
+---
+title: Skills guide
+description: How to manage agentic skills.
+---
+
+## Install skills
+
+You can install skills from [skills.sh](https://skills.sh) with `npx skills add`. You need to be
+mindful that skills can be malicious. Your first instinct should be to distrust any skill for which
+you cannot corroborate that it is legit. You should also always read the skill to verify that it
+does not do anything fishy. There is no harm in installing a skill, but before letting it loose on
+your AI, you really need to verify that it is safe to use.
+
+Let's take the [official Svelte skills](https://svelte.dev/docs/ai/skills) as an example. On the
+[Svelte skills page on skills.sh](https://skills.sh/sveltejs/ai-tools) you can double check from
+which repository the skills will be installed. Since the
+[repository is managed by the Svelte team](https://skills.sh/sveltejs/ai-tools), you can be
+confident that these skills are legit and you can use the command from skills.sh to install them.
+
+## Installation directory
+
+Directories in which agents look for skills are a mess:
+
+| Directory              | Type    | Description                                           |
+| :--------------------- | :------ | :---------------------------------------------------- |
+| `.agents/skills`       | project | Visible by Zed agent and other agents but not Claude. |
+| `~/.agents/skills`     | global  | Neither visible by Zed agent nor Claude.              |
+| `.claude/skills`       | project | Visible by Claude Code only.                          |
+| `~/.claude/skills`     | global  | Visible by Claude Code only.                          |
+| `~/.config/zed/skills` | global  | Visible by Zed agent only.                            |
+
+As a workaround, you can install skills globally into `~/.agents/skills` and create the following
+symbolic links:
+
+- `ln -s ~/.agents/skills ~/.config/zed/skills`
+- `ln -s ~/.agents/skills ~/.claude/skills`
+
+## List skills
+
+Use `npx skills` to manage agent skills. Run
+
+```bash
+npx skills list
+```
+
+to list installed project skills. Run
+
+```bash
+npx skills list -g
+```
+
+to list globally installed skills.
+
+## Update skills
+
+Run
+
+```bash
+npx skills update
+```
+
+to update installed skills. You will be prompted if you would like to update project skills or
+global skills.
+
+## Remove skills
+
+Run
+
+```bash
+npx skills remove
+```
+
+to remove a project skill. Run
+
+```bash
+npx skills remove -g
+```
+
+to remove a global skill.

src/routes/guides/zed/+page.md

@@ -33,8 +33,7 @@ project with above shortcut. This creates a multi-root workspace.
 ## Agent panel
 
 The agent panel is where you interact with the agent. Agent integration varies across providers. For
-example, not all agents support code reviews in which you can acceppt or reject changes
-individually.
+example, not all agents support code reviews in which you can accept or reject changes individually.
 
 | Shortcut | Description                     |
 | :------- | :------------------------------ |
@@ -45,9 +44,9 @@ individually.
 
 ## Worktrees
 
-Since v1, worktree support in Zed is usable. Using Git [worktrees](/guides/worktrees) to isolate
-workspaces within the same project works seamless. Click the branch name at the top to create a
-headless worktree. Then add a branch.
+Since v1, worktree support in Zed is actually usable. Using Git worktrees to isolate workspaces
+within the same project is seamless. Click the branch name at the top to create a headless worktree.
+Then add a branch.
 
 Zed keeps all worktrees in a configurable folder. However, it is opinionated about how worktrees are
 organized within that folder. But since you can switch between worktrees in the UI, you don't need
@@ -82,7 +81,7 @@ This is useful for pull request reviews. Zed does not let you choose a different
 diff.
 
 If the default branch is `origin/main` but you always target `origin/develop` in pull requests, you
-can configure `origin/develop` as the local branch in you local Git configuration. To find out the
+can configure `origin/develop` as the local branch in your local Git configuration. To find out the
 default branch, look for `remotes/origin/HEAD` in
 
 ```bash
@@ -100,8 +99,8 @@ this config.
 
 Make use of these features for PR reviews:
 
-- You can send the diff to your current agent for review. Unfortunatley, you cannot establish
-  context before adding the diff tho the agent session.
+- You can send the diff to your current agent for review. Unfortunately, you cannot establish
+  context before adding the diff to the agent session.
 - Use the Git graph to look at the PR's commit history.
 - Use the file history to see how a file has changed over time.
 - Add review comments to individual files via your Git provider's PR website.