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/commands/plan-story.md

@@ -20,6 +20,7 @@ Use `mcp__gitea__issue_read` to get the full issue (title, body, labels, milesto
 ### 2. Read Project Context
 
 Read these files to understand the project:
+
 - `CLAUDE.md` — coding standards and workflow (if it exists)
 - `package.json` — project dependencies and scripts
 - `implementation-plans/_index.md` — existing plans index (if it exists)
@@ -27,6 +28,7 @@ Read these files to understand the project:
 ### 3. Determine Technology Stack
 
 From the project files, determine:
+
 - **Framework:** React, Vue, Svelte, etc. (check package.json)
 - **Language:** TypeScript or JavaScript
 - **Build tool:** Vite, Next.js, Webpack, etc.
@@ -37,6 +39,7 @@ From the project files, determine:
 ### 4. Find Related Plans
 
 From the index (if it exists), identify plans that share:
+
 - The same feature area or component
 - Overlapping affected files
 - Dependency relationships (blocked-by / blocks)
@@ -46,6 +49,7 @@ Read those related plan files to understand prior decisions and patterns.
 ### 5. Explore the Codebase
 
 Based on the issue's scope, explore relevant code:
+
 - Use Glob to find files in affected directories
 - Use Grep to find existing patterns, interfaces, types, and components
 - Use Read to examine specific files mentioned in the issue or related plans
@@ -56,6 +60,7 @@ Based on the issue's scope, explore relevant code:
 The plan MUST include:
 
 **Metadata:**
+
 - Issue link, number, title
 - Milestone and labels
 - Status: `PLANNED`
@@ -64,9 +69,11 @@ The plan MUST include:
 - Blocked-by references
 
 **Acceptance Criteria:**
+
 - Copy directly from the issue body
 
 **Architecture Analysis:**
+
 - Which components/pages are affected
 - Which API endpoints are involved
 - Which state/stores are affected
@@ -74,6 +81,7 @@ The plan MUST include:
 - Existing patterns to follow (with file references)
 
 **Implementation Steps (phase by phase):**
+
 1. **Types & Configuration** — TypeScript types/interfaces, config constants, API types
 2. **Core Logic** — Business logic, hooks, utilities, state management
 3. **Components** — UI components, layouts, pages
@@ -81,9 +89,11 @@ The plan MUST include:
 5. **Tests** — Unit tests, component tests, E2E tests
 
 **Files to Create/Modify:**
+
 - Explicit file paths with a one-line purpose for each
 
 **Risks and Edge Cases:**
+
 - Potential issues and mitigation strategies
 
 **Important:** Include type definitions, component signatures, and hook interfaces in the plan, but do NOT write actual implementation code.
@@ -95,6 +105,7 @@ Write the plan to `implementation-plans/issue-$ARGUMENTS.md`.
 ### 8. Update the Index
 
 Create or update `implementation-plans/_index.md`:
+
 - Add the new plan to the master table
 - Add cross-references in the appropriate feature area section