repro

AGENTS.md

@@ -0,0 +1,56 @@
+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.
+
+## Development Commands
+
+**From project root:**
+
+- `pnpm dev` - Start SvelteKit dev server with hot reload (port 5173)
+- `pnpm build` - Build production assets
+- `pnpm preview` - Preview production build locally
+- `pnpm docker:build` - Build unified Docker container (Python 3.11 + Node 24 + beets)
+- `pnpm docker:run` - Start Docker container with `docker-compose up -d`
+- `pnpm docker:down` - Stop Docker container with `docker-compose down`
+
+**Development setup:**
+
+1. Install Python dependencies: `pip install uv && uv pip install -r requirements.txt`
+2. Beets CLI available for local development
+3. SvelteKit development server runs locally with hot reload
+
+**Beets integration:**
+
+Use `src/lib/beets.ts` helpers to call beets CLI:
+
+- `importMusic(directory)` - Import music from directory
+- `queryBeets(query)` - Query music library
+- Config: `config/beets.yaml` (mounted/configured for Docker)
+
+**Production Docker:**
+
+Unified container running both SvelteKit and beets:
+
+- Port 3000 for SvelteKit app
+- Volumes: `.data/` (music library), `.appdata/` (beets state)
+- SvelteKit calls beets via `child_process` with config path