feat: scaffold SvelteKit project with Tailwind, TypeScript, ESLint, Prettier

Initialize the llm-multiverse-ui project with:
- SvelteKit + Svelte 5 (runes mode enabled)
- Tailwind CSS v4 via @tailwindcss/vite plugin
- TypeScript strict mode
- ESLint 9 flat config with svelte and typescript-eslint plugins
- Prettier with svelte plugin
- Directory structure: src/lib/components/, src/lib/services/
- All required scripts: dev, build, preview, lint, format, check

Closes #1

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

.claude/agents/implement-story.md

@@ -23,6 +23,7 @@ An implementation plan MUST exist at `implementation-plans/issue-<NUMBER>.md` wi
 ### 1. Read the Plan and Context
 
 Read these files:
+
 - `implementation-plans/issue-<NUMBER>.md` -- the implementation plan
 - `CLAUDE.md` -- coding standards (if it exists)
 - `package.json` -- project dependencies and scripts
@@ -61,6 +62,7 @@ Follow the plan's implementation steps in order:
 ### 5. Code Quality Standards
 
 **General:**
+
 - TypeScript strict mode -- no `any` types without justification
 - Use the project's established patterns for component structure
 - Follow the project's naming conventions (check existing code)
@@ -68,17 +70,20 @@ Follow the plan's implementation steps in order:
 - Accessible markup (semantic HTML, ARIA attributes where needed)
 
 **Components:**
+
 - Keep components focused -- single responsibility
 - Extract reusable logic into custom hooks
 - Use proper prop typing with TypeScript interfaces
 - Handle loading, error, and empty states
 
 **State Management:**
+
 - Follow the project's chosen state management approach
 - Keep state as local as possible
 - Avoid prop drilling -- use context or state management when appropriate
 
 **Styling:**
+
 - Follow the project's established styling approach
 - Ensure responsive design
 - Support dark/light themes if the project uses them
@@ -86,6 +91,7 @@ Follow the plan's implementation steps in order:
 ### 6. Log Deviations
 
 If you deviate from the plan (different approach, additional files, skipped steps), document each deviation in the plan's **Deviation Log** section with:
+
 - What changed
 - Why it changed
 
@@ -115,6 +121,7 @@ Adapt commands based on what's available in `package.json`. Fix any failures bef
 ### 8. Commit
 
 Stage all changed files and commit with a descriptive message:
+
 ```
 feat: <short description of what was implemented> (issue #<NUMBER>)
 ```
@@ -124,6 +131,7 @@ Use conventional commit prefixes: `feat:`, `fix:`, `chore:`, `refactor:`, `test:
 ### 9. Output
 
 **standalone mode:** Display:
+
 - Files created and modified (with counts)
 - Tests added (count and coverage percentage)
 - Deviations from plan (if any)
@@ -136,23 +144,23 @@ Use conventional commit prefixes: `feat:`, `fix:`, `chore:`, `refactor:`, `test:
 
 ```json
 {
-  "status": "success | failed",
-  "summary": "Implemented issue #N on branch feature/issue-N-desc",
-  "artifacts": ["list of files created/modified"],
-  "phase_data": {
-    "issue_number": 28,
-    "branch_name": "feature/issue-28-dashboard-page",
-    "files_created": ["src/pages/Dashboard.tsx"],
-    "files_modified": ["src/App.tsx"],
-    "quality_gates": {
-      "build": "pass",
-      "lint": "pass",
-      "typecheck": "pass",
-      "tests": "pass"
-    },
-    "deviations": []
-  },
-  "failure_reason": null
+	"status": "success | failed",
+	"summary": "Implemented issue #N on branch feature/issue-N-desc",
+	"artifacts": ["list of files created/modified"],
+	"phase_data": {
+		"issue_number": 28,
+		"branch_name": "feature/issue-28-dashboard-page",
+		"files_created": ["src/pages/Dashboard.tsx"],
+		"files_modified": ["src/App.tsx"],
+		"quality_gates": {
+			"build": "pass",
+			"lint": "pass",
+			"typecheck": "pass",
+			"tests": "pass"
+		},
+		"deviations": []
+	},
+	"failure_reason": null
 }
 ```