From ce4f473946b83e7dcbbab25f52c8cde85452dee2 Mon Sep 17 00:00:00 2001
From: Thilo Maier <git@maier.asia>
Date: Sun, 21 Sep 2025 20:56:35 +0200
Subject: [PATCH 1/3] Move `copilot-instructions.md` to `AGENTS.md`

---
 .github/copilot-instructions.md => AGENTS.md | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 rename .github/copilot-instructions.md => AGENTS.md (100%)

diff --git a/.github/copilot-instructions.md b/AGENTS.md
similarity index 100%
rename from .github/copilot-instructions.md
rename to AGENTS.md

From 27075861578335526dc0603e8c429f74c3a88aad Mon Sep 17 00:00:00 2001
From: Thilo Maier <git@maier.asia>
Date: Sat, 4 Oct 2025 23:58:47 +0200
Subject: [PATCH 2/3] Add instructions for MCP server

---
 .vscode/mcp.json |  9 ++++++
 AGENTS.md        | 80 +++++++++++++++++++++++++++++++++---------------
 2 files changed, 64 insertions(+), 25 deletions(-)
 create mode 100644 .vscode/mcp.json

diff --git a/.vscode/mcp.json b/.vscode/mcp.json
new file mode 100644
index 00000000..7cc49d4b
--- /dev/null
+++ b/.vscode/mcp.json
@@ -0,0 +1,9 @@
+{
+	"servers": {
+		"svelte-mcp-server": {
+			"url": "https://mcp.svelte.dev/mcp",
+			"type": "http"
+		}
+	},
+	"inputs": []
+}
diff --git a/AGENTS.md b/AGENTS.md
index 87a6c377..ee0e40ef 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -1,39 +1,69 @@
-# @maiertech/website
+# AGENTS.md
 
-## Overview
+## Description
 
-This is my personal website with posts and notes.
+This is a content-driven website with three types of content:
 
-## Tech stack
+1. Post: An article that dives deeper into a topic.
+2. Note: A brief observation or thought.
+3. Video: A YouTube video instead of a post.
 
-- PNPM.
-- SvelteKit v2.
+## Stack
+
+- SvelteKit v2 with `adapter-node`.
+- Deployment to Railway.com with their zero configuration deployments.
 - Svelte v5.
 - TypeScript.
-- Zod for schema validation and type inference.
-- TailwindCSS v4 and tailwind-merge.
+- Zod schemas.
+- TailwindCSS v4 and `tailwind-merge`.
 - Mdsvex for authoring posts and notes.
-- It imports reusable components, Zod schemas and TypeScript types from the private package
-  `@maiertech/sveltekit-helpers`.
-
-## Repository structure
+- Package `@maiertech/sveltekit-helpers` to import reusable components, Zod schemas and TypeScript
+  types.
+- PNPM as package manager.
 
-- `src/lib/components`: Svelte components.
-- `src/lib/schemas`: Zod schemas.
-- `src/lib/mdsvex/layouts`: Layouts for mdsvex.
-- `src/routes`: File system router.
+## Conventions
 
-## Code style
+- Use CamelCase for both component names and their file names.
+- Always use Svelte v5, never v4.
+- Prefer TailwindCSS in combination with tailwind-merge for styling, but you can use plain CSS
+  inside Svelte's `<style>` tag for complex styles.
+- Use `$env/dynamic/private` runtime variables in SvelteKit.
+- Don't return or throw SvelteKit's `error` function. It knows what to do.
+- Comments always end with a period.
 
-- Always use Svelte v5 syntax.
-- Do not use self-closing tags for Svelte components and HTML elements.
-- Use TailwindCSS for styling and tailwind-merge for class merging.
-- Comments use proper punctuation and end with a period.
-
-## Writing style
+## Written Content
 
 - Use American English.
 - Be concise and clear in your explanations.
 - Use active voice and present tense.
-- Write a tad informal, but not too casual.
-- Don't use em dashes.
+- Write in a conversational but professional tone.
+
+## svelte-mcp-server
+
+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:
+
+### 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.

From cf6561d0c20d5b70e5a85d5cbf3d48fbe3e481db Mon Sep 17 00:00:00 2001
From: Thilo Maier <git@maier.asia>
Date: Sun, 5 Oct 2025 00:10:58 +0200
Subject: [PATCH 3/3] Address review comments

---
 AGENTS.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/AGENTS.md b/AGENTS.md
index ee0e40ef..7a0b4b1f 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -11,7 +11,7 @@ This is a content-driven website with three types of content:
 ## Stack
 
 - SvelteKit v2 with `adapter-node`.
-- Deployment to Railway.com with their zero configuration deployments.
+- Deployment to Railway.com with their zero-configuration deployments.
 - Svelte v5.
 - TypeScript.
 - Zod schemas.
@@ -23,7 +23,7 @@ This is a content-driven website with three types of content:
 
 ## Conventions
 
-- Use CamelCase for both component names and their file names.
+- Use PascalCase for both Svelte component names and their file names (e.g., PostCard.svelte).
 - Always use Svelte v5, never v4.
 - Prefer TailwindCSS in combination with tailwind-merge for styling, but you can use plain CSS
   inside Svelte's `<style>` tag for complex styles.