docs: setup kiro hook and update steering docs (#69)

Author: DaxServer

.kiro/hooks/test-after-conversation.json

@@ -0,0 +1,14 @@
+{
+  "name": "Run Tests After Conversation",
+  "description": "Automatically run `bun test` from root after Kiro finishes a conversation to ensure tests pass",
+  "trigger": {
+    "type": "conversationEnd"
+  },
+  "action": {
+    "type": "command",
+    "command": "bun test",
+    "workingDirectory": ".",
+    "requireSuccess": true
+  },
+  "enabled": true
+}

.kiro/steering/tech.md

@@ -27,6 +27,46 @@
 - **Auto-imports**: Automatic imports for Vue composables and PrimeVue components
 - **TypeScript**: Strict type checking across the stack
 
+## Auto-Import Configuration (Frontend)
+
+The frontend uses `unplugin-auto-import` and `unplugin-vue-components` for automatic imports:
+
+### Auto-Import Rules
+- **Framework APIs**: All Vue, Vue Router, and Pinia APIs are automatically imported
+- **Third-party Libraries**: VueUse composables and PrimeVue utilities are auto-imported
+- **Custom Code**: All files in `src/**` (all subdirectories under src) are auto-imported
+- **Components**: All PrimeVue components and custom components in `src/*` (direct subdirectories) are auto-imported
+
+### Usage Guidelines
+- No need to import Vue APIs, VueUse composables, or PrimeVue components
+- All exported functions from any file under `src/` are automatically available
+- Components from direct subdirectories of `src/` are automatically available
+- Type definitions are generated in `auto-imports.d.ts` and `components.d.ts`
+- ESLint configuration is automatically updated for auto-imports
+- Avoid manual imports for auto-imported items to prevent conflicts
+
+## Path Aliasing
+
+The project uses TypeScript path mapping for clean imports across the monorepo.
+
+### Configuration
+- **Base Config**: `tsconfig.base.json` defines all path mappings
+- **Frontend**: Uses `vite-tsconfig-paths` plugin for Vite compatibility
+- **Backend**: Inherits paths from base configuration
+- **Root Level**: Paths resolve from project root directory
+
+### Path Mapping Rules
+- `@backend` → `./backend/src`
+- `@backend/*` → `./backend/src/*`
+- `@backend/tests/*` → `./backend/tests/*`
+- `@frontend` → `./frontend/src`
+- `@frontend/*` → `./frontend/src/*`
+
+### Best Practices
+- Always use path aliases `@frontend/` and `@backend/` but not relative paths
+- Use aliases consistently across both TypeScript and test files
+- Path aliases work in both development and build environments
+
 ## Common Commands
 
 ### Development