diff --git a/firmware/website/.gemini/settings.json b/firmware/website/.gemini/settings.json new file mode 100644 index 0000000..74e4040 --- /dev/null +++ b/firmware/website/.gemini/settings.json @@ -0,0 +1,8 @@ +{ + "$schema": "https://raw.githubusercontent.com/google-gemini/gemini-cli/main/schemas/settings.schema.json", + "mcpServers": { + "svelte": { + "url": "https://mcp.svelte.dev/mcp" + } + } +} diff --git a/firmware/website/.mcp.json b/firmware/website/.mcp.json new file mode 100644 index 0000000..0b7b5c6 --- /dev/null +++ b/firmware/website/.mcp.json @@ -0,0 +1,8 @@ +{ + "mcpServers": { + "svelte": { + "type": "http", + "url": "https://mcp.svelte.dev/mcp" + } + } +} diff --git a/firmware/website/.vscode/mcp.json b/firmware/website/.vscode/mcp.json new file mode 100644 index 0000000..5182f3a --- /dev/null +++ b/firmware/website/.vscode/mcp.json @@ -0,0 +1,7 @@ +{ + "servers": { + "svelte": { + "url": "https://mcp.svelte.dev/mcp" + } + } +} diff --git a/firmware/website/AGENTS.md b/firmware/website/AGENTS.md new file mode 100644 index 0000000..a6e66ff --- /dev/null +++ b/firmware/website/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 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. diff --git a/firmware/website/CLAUDE.md b/firmware/website/CLAUDE.md new file mode 100644 index 0000000..a6e66ff --- /dev/null +++ b/firmware/website/CLAUDE.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 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. diff --git a/firmware/website/GEMINI.md b/firmware/website/GEMINI.md new file mode 100644 index 0000000..a6e66ff --- /dev/null +++ b/firmware/website/GEMINI.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 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. diff --git a/firmware/website/public/captive.html b/firmware/website/public/captive.html new file mode 100644 index 0000000..371a9f8 --- /dev/null +++ b/firmware/website/public/captive.html @@ -0,0 +1,53 @@ + + +
+ + +Gib die Daten deines Heimnetzwerks ein.
+ + +