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/refactor-review.md

@@ -12,6 +12,7 @@ Mode is specified in Dynamic Context below. Default: standalone.
 ## Trigger
 
 This agent is invoked:
+
 - Periodically (every ~5 completed stories) by the auto-dev pipeline
 - Manually by the user via `/project:refactor-review`
 
@@ -26,6 +27,7 @@ This agent is invoked:
 ### 2. Survey the Codebase
 
 Explore all source directories:
+
 - Use Glob to find all source files (`src/**/*.ts`, `src/**/*.tsx`, `src/**/*.css`, `src/**/*.vue`, `src/**/*.svelte`, etc.)
 - Use Grep to find patterns of concern (see checklist below)
 - Read key files to understand current state
@@ -35,17 +37,20 @@ Explore all source directories:
 Evaluate the project against these dimensions:
 
 **Code Duplication:**
+
 - Shared logic duplicated across components instead of extracted to hooks/utilities
 - Similar UI patterns that should be abstracted into shared components
 - Repeated API call patterns that should use a shared data fetching layer
 
 **Modularity:**
+
 - Components longer than ~100 lines that should be split
 - Components with too many responsibilities (God components)
 - Tight coupling between feature modules
 - Missing abstractions (e.g., a custom hook for behavior used in multiple places)
 
 **Consistency:**
+
 - Inconsistent error handling patterns across components
 - Inconsistent state management approaches
 - Inconsistent API call patterns
@@ -53,23 +58,27 @@ Evaluate the project against these dimensions:
 - Inconsistent styling approaches
 
 **Architecture Drift:**
+
 - Components bypassing the established API layer
 - State management inconsistencies
 - Routing pattern violations
 - Feature boundaries not respected
 
 **Dependency Health:**
+
 - Unused dependencies in package.json
 - Outdated dependencies with known vulnerabilities
 - Lock file hygiene
 
 **Test Quality:**
+
 - Tests that only test happy paths
 - Missing component tests for interactive features
 - Missing E2E tests for critical user flows
 - Test code duplication (shared fixtures/helpers needed)
 
 **Accessibility:**
+
 - Missing ARIA attributes on interactive elements
 - Missing keyboard navigation
 - Color contrast issues
@@ -79,11 +88,11 @@ Evaluate the project against these dimensions:
 
 Categorize each finding:
 
-| Priority | Description |
-|---|---|
-| **High** | Architecture drift, security concern, significant duplication causing bugs, accessibility blockers |
-| **Medium** | Modularity issues, inconsistencies, test quality gaps |
-| **Low** | Style issues, minor duplication, documentation gaps |
+| Priority   | Description                                                                                        |
+| ---------- | -------------------------------------------------------------------------------------------------- |
+| **High**   | Architecture drift, security concern, significant duplication causing bugs, accessibility blockers |
+| **Medium** | Modularity issues, inconsistencies, test quality gaps                                              |
+| **Low**    | Style issues, minor duplication, documentation gaps                                                |
 
 ### 5. Create Refactoring Issues
 
@@ -140,15 +149,15 @@ Check existing open issues with `type:refactor` and `priority:low` labels. If an
 
 ```json
 {
-  "status": "success",
-  "summary": "Refactoring review complete",
-  "artifacts": [],
-  "phase_data": {
-    "project_health": "GOOD",
-    "issues_created": [{"number": 42, "title": "Refactor: ...", "priority": "medium"}],
-    "issues_closed": [{"number": 30, "title": "Tech debt: ...", "reason": "resolved"}]
-  },
-  "failure_reason": null
+	"status": "success",
+	"summary": "Refactoring review complete",
+	"artifacts": [],
+	"phase_data": {
+		"project_health": "GOOD",
+		"issues_created": [{ "number": 42, "title": "Refactor: ...", "priority": "medium" }],
+		"issues_closed": [{ "number": 30, "title": "Tech debt: ...", "reason": "resolved" }]
+	},
+	"failure_reason": null
 }
 ```