Add AI coding tool configuration files

.cursorrules

@@ -0,0 +1,22 @@
+You are working on root, a Svelte project.
+<img style="max-width: 100%" alt="hero" src="https://github.com/user-attachments/assets/19cac792-6a93-4289-b9c7-647794a7de79" />
+
+Tech stack: SvelteKit, Vite.
+
+## Project Structure
+
+Key directories: .github, bundle-analyzer, docs, packages, tests
+
+## Testing
+
+- 144 test files in the project
+- Write tests for new functionality
+- Follow existing test patterns and naming conventions
+
+## Style
+
+- Follow the existing linter/formatter configuration
+- Do not disable linting rules without good reason
+
+# Generated by ai-ready (https://github.com/lunacompsia-oss/ai-ready)
+# Customize this file to match your project's specific conventions.

.github/copilot-instructions.md

@@ -0,0 +1,23 @@
+# GitHub Copilot Instructions for root
+
+<img style="max-width: 100%" alt="hero" src="https://github.com/user-attachments/assets/19cac792-6a93-4289-b9c7-647794a7de79" />
+
+This is a Svelte project using SvelteKit, Vite.
+
+## General Guidelines
+
+- Follow existing code patterns and conventions in this repository
+- Use Svelte idioms and best practices
+- Always include type annotations
+- Include tests for new functionality
+- Keep functions small and focused
+- Use meaningful variable and function names
+
+## Frameworks
+
+This project uses: SvelteKit, Vite
+- Follow framework conventions and patterns
+- Use framework-provided utilities over custom implementations
+
+---
+*Generated by [ai-ready](https://github.com/lunacompsia-oss/ai-ready) — customize to match your project.*

.windsurfrules

@@ -0,0 +1,22 @@
+You are working on root, a Svelte project.
+<img style="max-width: 100%" alt="hero" src="https://github.com/user-attachments/assets/19cac792-6a93-4289-b9c7-647794a7de79" />
+
+Tech stack: SvelteKit, Vite.
+
+## Project Structure
+
+Key directories: .github, bundle-analyzer, docs, packages, tests
+
+## Testing
+
+- 144 test files in the project
+- Write tests for new functionality
+- Follow existing test patterns and naming conventions
+
+## Style
+
+- Follow the existing linter/formatter configuration
+- Do not disable linting rules without good reason
+
+# Generated by ai-ready (https://github.com/lunacompsia-oss/ai-ready)
+# Customize this file to match your project's specific conventions.

CLAUDE.md

@@ -0,0 +1,56 @@
+# root
+
+<img style="max-width: 100%" alt="hero" src="https://github.com/user-attachments/assets/19cac792-6a93-4289-b9c7-647794a7de79" />
+
+## Project Overview
+
+- **Primary Language:** Svelte
+- **Other Languages:** TypeScript, JavaScript
+- **Frameworks:** SvelteKit, Vite
+- **Package Manager:** pnpm
+
+## Project Structure
+
+```
+.github/
+bundle-analyzer/
+docs/
+packages/
+tests/
+```
+
+## Key Commands
+
+- **Install:** `pnpm install`
+- **Dev:** `pnpm run dev`
+- **Build:** `pnpm run build`
+- **Test:** `pnpm test`
+- **Lint:** `pnpm run lint`
+
+## Code Style
+
+- Adhere to the project linter/formatter configuration
+
+## Conventions
+
+- All PRs must pass CI before merging
+- Write tests for new features and bug fixes
+- Read CONTRIBUTING.md before making changes
+- Update documentation when changing public APIs
+- Keep commits focused and atomic
+- Write clear commit messages describing the "why"
+
+## Architecture
+
+- Appears to be a monorepo — check workspace configuration
+
+## Important Notes
+
+- Read existing code before making changes to understand patterns
+- Follow the existing project structure and naming conventions
+- Run tests after making changes to verify nothing is broken
+- Ensure code passes linting before committing
+- All changes must pass CI checks
+
+---
+*Generated by [ai-ready](https://github.com/lunacompsia-oss/ai-ready) — customize this file to match your project's specific conventions.*