diff --git a/.agents/skills/playwright-generate-test/SKILL.md b/.agents/skills/playwright-generate-test/SKILL.md
deleted file mode 100644
index 5d80435..0000000
--- a/.agents/skills/playwright-generate-test/SKILL.md
+++ /dev/null
@@ -1,17 +0,0 @@
----
-name: playwright-generate-test
-description: 'Generate a Playwright test based on a scenario using Playwright MCP'
----
-
-# Test Generation with Playwright MCP
-
-Your goal is to generate a Playwright test based on the provided scenario after completing all prescribed steps.
-
-## Specific Instructions
-
-- You are given a scenario, and you need to generate a playwright test for it. If the user does not provide a scenario, you will ask them to provide one.
-- DO NOT generate test code prematurely or based solely on the scenario without completing all prescribed steps.
-- DO run steps one by one using the tools provided by the Playwright MCP.
-- Only after all steps are completed, emit a Playwright TypeScript test that uses `@playwright/test` based on message history
-- Save generated test file in the tests directory
-- Execute the test file and iterate until the test passes
diff --git a/.agents/skills/playwright/LICENSE.txt b/.agents/skills/playwright/LICENSE.txt
deleted file mode 100644
index b5ed4ec..0000000
--- a/.agents/skills/playwright/LICENSE.txt
+++ /dev/null
@@ -1,201 +0,0 @@
-                                 Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
-
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-   1. Definitions.
-
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
-
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
-
-      "Legal Entity" shall mean the union of the acting entity and all
-      other entities that control, are controlled by, or are under common
-      control with that entity. For the purposes of this definition,
-      "control" means (i) the power, direct or indirect, to cause the
-      direction or management of such entity, whether by contract or
-      otherwise, or (ii) ownership of fifty percent (50%) or more of the
-      outstanding shares, or (iii) beneficial ownership of such entity.
-
-      "You" (or "Your") shall mean an individual or Legal Entity
-      exercising permissions granted by this License.
-
-      "Source" form shall mean the preferred form for making modifications,
-      including but not limited to software source code, documentation
-      source, and configuration files.
-
-      "Object" form shall mean any form resulting from mechanical
-      transformation or translation of a Source form, including but
-      not limited to compiled object code, generated documentation,
-      and conversions to other media types.
-
-      "Work" shall mean the work of authorship, whether in Source or
-      Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work
-      (an example is provided in the Appendix below).
-
-      "Derivative Works" shall mean any work, whether in Source or Object
-      form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship. For the purposes
-      of this License, Derivative Works shall not include works that remain
-      separable from, or merely link (or bind by name) to the interfaces of,
-      the Work and Derivative Works thereof.
-
-      "Contribution" shall mean any work of authorship, including
-      the original version of the Work and any modifications or additions
-      to that Work or Derivative Works thereof, that is intentionally
-      submitted to Licensor for inclusion in the Work by the copyright owner
-      or by an individual or Legal Entity authorized to submit on behalf of
-      the copyright owner. For the purposes of this definition, "submitted"
-      means any form of electronic, verbal, or written communication sent
-      to the Licensor or its representatives, including but not limited to
-      communication on electronic mailing lists, source code control systems,
-      and issue tracking systems that are managed by, or on behalf of, the
-      Licensor for the purpose of discussing and improving the Work, but
-      excluding communication that is conspicuously marked or otherwise
-      designated in writing by the copyright owner as "Not a Contribution."
-
-      "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by Licensor and
-      subsequently incorporated within the Work.
-
-   2. Grant of Copyright License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      copyright license to reproduce, prepare Derivative Works of,
-      publicly display, publicly perform, sublicense, and distribute the
-      Work and such Derivative Works in Source or Object form.
-
-   3. Grant of Patent License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      (except as stated in this section) patent license to make, have made,
-      use, offer to sell, sell, import, and otherwise transfer the Work,
-      where such license applies only to those patent claims licensable
-      by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by combination of their Contribution(s)
-      with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a
-      cross-claim or counterclaim in a lawsuit) alleging that the Work
-      or a Contribution incorporated within the Work constitutes direct
-      or contributory patent infringement, then any patent licenses
-      granted to You under this License for that Work shall terminate
-      as of the date such litigation is filed.
-
-   4. Redistribution. You may reproduce and distribute copies of the
-      Work or Derivative Works thereof in any medium, with or without
-      modifications, and in Source or Object form, provided that You
-      meet the following conditions:
-
-      (a) You must give any other recipients of the Work or
-          Derivative Works a copy of this License; and
-
-      (b) You must cause any modified files to carry prominent notices
-          stating that You changed the files; and
-
-      (c) You must retain, in the Source form of any Derivative Works
-          that You distribute, all copyright, patent, trademark, and
-          attribution notices from the Source form of the Work,
-          excluding those notices that do not pertain to any part of
-          the Derivative Works; and
-
-      (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, then any Derivative Works that You distribute must
-          include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding those notices that do not
-          pertain to any part of the Derivative Works, in at least one
-          of the following places: within a NOTICE text file distributed
-          as part of the Derivative Works; within the Source form or
-          documentation, if provided along with the Derivative Works; or,
-          within a display generated by the Derivative Works, if and
-          wherever such third-party notices normally appear. The contents
-          of the NOTICE file are for informational purposes only and
-          do not modify the License. You may add Your own attribution
-          notices within Derivative Works that You distribute, alongside
-          or as an addendum to the NOTICE text from the Work, provided
-          that such additional attribution notices cannot be construed
-          as modifying the License.
-
-      You may add Your own copyright statement to Your modifications and
-      may provide additional or different license terms and conditions
-      for use, reproduction, or distribution of Your modifications, or
-      for any such Derivative Works as a whole, provided Your use,
-      reproduction, and distribution of the Work otherwise complies with
-      the conditions stated in this License.
-
-   5. Submission of Contributions. Unless You explicitly state otherwise,
-      any Contribution intentionally submitted for inclusion in the Work
-      by You to the Licensor shall be under the terms and conditions of
-      this License, without any additional terms or conditions.
-      Notwithstanding the above, nothing herein shall supersede or modify
-      the terms of any separate license agreement you may have executed
-      with Licensor regarding such Contributions.
-
-   6. Trademarks. This License does not grant permission to use the trade
-      names, trademarks, service marks, or product names of the Licensor,
-      except as required for reasonable and customary use in describing the
-      origin of the Work and reproducing the content of the NOTICE file.
-
-   7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work (and each
-      Contributor provides its Contributions) on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any warranties or conditions
-      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-      PARTICULAR PURPOSE. You are solely responsible for determining the
-      appropriateness of using or redistributing the Work and assume any
-      risks associated with Your exercise of permissions under this License.
-
-   8. Limitation of Liability. In no event and under no legal theory,
-      whether in tort (including negligence), contract, or otherwise,
-      unless required by applicable law (such as deliberate and grossly
-      negligent acts) or agreed to in writing, shall any Contributor be
-      liable to You for damages, including any direct, indirect, special,
-      incidental, or consequential damages of any character arising as a
-      result of this License or out of the use or inability to use the
-      Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or any and all
-      other commercial damages or losses), even if such Contributor
-      has been advised of the possibility of such damages.
-
-   9. Accepting Warranty or Additional Liability. While redistributing
-      the Work or Derivative Works thereof, You may choose to offer,
-      and charge a fee for, acceptance of support, warranty, indemnity,
-      or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may act only
-      on Your own behalf and on Your sole responsibility, not on behalf
-      of any other Contributor, and only if You agree to indemnify,
-      defend, and hold each Contributor harmless for any liability
-      incurred by, or claims asserted against, such Contributor by reason
-      of your accepting any such warranty or additional liability.
-
-   END OF TERMS AND CONDITIONS
-
-   APPENDIX: How to apply the Apache License to your work.
-
-      To apply the Apache License to your work, attach the following
-      boilerplate notice, with the fields enclosed by brackets "[]"
-      replaced with your own identifying information. (Don't include
-      the brackets!)  The text should be enclosed in the appropriate
-      comment syntax for the file format. We also recommend that a
-      file or class name and description of purpose be included on the
-      same "printed page" as the copyright notice for easier
-      identification within third-party archives.
-
-   Copyright (c) Microsoft Corporation.
-
-   Licensed under the Apache License, Version 2.0 (the "License");
-   you may not use this file except in compliance with the License.
-   You may obtain a copy of the License at
-
-       http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing, software
-   distributed under the License is distributed on an "AS IS" BASIS,
-   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-   See the License for the specific language governing permissions and
-   limitations under the License.
diff --git a/.agents/skills/playwright/NOTICE.txt b/.agents/skills/playwright/NOTICE.txt
deleted file mode 100644
index f3a1933..0000000
--- a/.agents/skills/playwright/NOTICE.txt
+++ /dev/null
@@ -1,14 +0,0 @@
-This skill includes material derived from the Microsoft playwright-cli repository.
-
-Source:
-- Repository: microsoft/playwright-cli
-- Path: skills/playwright-cli/SKILL.md
-
-Copyright (c) Microsoft Corporation.
-
-Licensed under the Apache License, Version 2.0.
-See LICENSE.txt in this directory.
-
-Modifications:
-- Adapted for the Codex skill collection.
-- Added a wrapper script and local reference guides.
diff --git a/.agents/skills/playwright/SKILL.md b/.agents/skills/playwright/SKILL.md
deleted file mode 100644
index 77c01af..0000000
--- a/.agents/skills/playwright/SKILL.md
+++ /dev/null
@@ -1,147 +0,0 @@
----
-name: "playwright"
-description: "Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script."
----
-
-
-# Playwright CLI Skill
-
-Drive a real browser from the terminal using `playwright-cli`. Prefer the bundled wrapper script so the CLI works even when it is not globally installed.
-Treat this skill as CLI-first automation. Do not pivot to `@playwright/test` unless the user explicitly asks for test files.
-
-## Prerequisite check (required)
-
-Before proposing commands, check whether `npx` is available (the wrapper depends on it):
-
-```bash
-command -v npx >/dev/null 2>&1
-```
-
-If it is not available, pause and ask the user to install Node.js/npm (which provides `npx`). Provide these steps verbatim:
-
-```bash
-# Verify Node/npm are installed
-node --version
-npm --version
-
-# If missing, install Node.js/npm, then:
-npm install -g @playwright/cli@latest
-playwright-cli --help
-```
-
-Once `npx` is present, proceed with the wrapper script. A global install of `playwright-cli` is optional.
-
-## Skill path (set once)
-
-```bash
-export CODEX_HOME="${CODEX_HOME:-$HOME/.codex}"
-export PWCLI="$CODEX_HOME/skills/playwright/scripts/playwright_cli.sh"
-```
-
-User-scoped skills install under `$CODEX_HOME/skills` (default: `~/.codex/skills`).
-
-## Quick start
-
-Use the wrapper script:
-
-```bash
-"$PWCLI" open https://playwright.dev --headed
-"$PWCLI" snapshot
-"$PWCLI" click e15
-"$PWCLI" type "Playwright"
-"$PWCLI" press Enter
-"$PWCLI" screenshot
-```
-
-If the user prefers a global install, this is also valid:
-
-```bash
-npm install -g @playwright/cli@latest
-playwright-cli --help
-```
-
-## Core workflow
-
-1. Open the page.
-2. Snapshot to get stable element refs.
-3. Interact using refs from the latest snapshot.
-4. Re-snapshot after navigation or significant DOM changes.
-5. Capture artifacts (screenshot, pdf, traces) when useful.
-
-Minimal loop:
-
-```bash
-"$PWCLI" open https://example.com
-"$PWCLI" snapshot
-"$PWCLI" click e3
-"$PWCLI" snapshot
-```
-
-## When to snapshot again
-
-Snapshot again after:
-
-- navigation
-- clicking elements that change the UI substantially
-- opening/closing modals or menus
-- tab switches
-
-Refs can go stale. When a command fails due to a missing ref, snapshot again.
-
-## Recommended patterns
-
-### Form fill and submit
-
-```bash
-"$PWCLI" open https://example.com/form
-"$PWCLI" snapshot
-"$PWCLI" fill e1 "user@example.com"
-"$PWCLI" fill e2 "password123"
-"$PWCLI" click e3
-"$PWCLI" snapshot
-```
-
-### Debug a UI flow with traces
-
-```bash
-"$PWCLI" open https://example.com --headed
-"$PWCLI" tracing-start
-# ...interactions...
-"$PWCLI" tracing-stop
-```
-
-### Multi-tab work
-
-```bash
-"$PWCLI" tab-new https://example.com
-"$PWCLI" tab-list
-"$PWCLI" tab-select 0
-"$PWCLI" snapshot
-```
-
-## Wrapper script
-
-The wrapper script uses `npx --package @playwright/cli playwright-cli` so the CLI can run without a global install:
-
-```bash
-"$PWCLI" --help
-```
-
-Prefer the wrapper unless the repository already standardizes on a global install.
-
-## References
-
-Open only what you need:
-
-- CLI command reference: `references/cli.md`
-- Practical workflows and troubleshooting: `references/workflows.md`
-
-## Guardrails
-
-- Always snapshot before referencing element ids like `e12`.
-- Re-snapshot when refs seem stale.
-- Prefer explicit commands over `eval` and `run-code` unless needed.
-- When you do not have a fresh snapshot, use placeholder refs like `eX` and say why; do not bypass refs with `run-code`.
-- Use `--headed` when a visual check will help.
-- When capturing artifacts in this repo, use `output/playwright/` and avoid introducing new top-level artifact folders.
-- Default to CLI commands and workflows, not Playwright test specs.
diff --git a/.agents/skills/playwright/agents/openai.yaml b/.agents/skills/playwright/agents/openai.yaml
deleted file mode 100644
index e74575e..0000000
--- a/.agents/skills/playwright/agents/openai.yaml
+++ /dev/null
@@ -1,6 +0,0 @@
-interface:
-  display_name: "Playwright CLI Skill"
-  short_description: "Automate real browsers from the terminal"
-  icon_small: "./assets/playwright-small.svg"
-  icon_large: "./assets/playwright.png"
-  default_prompt: "Automate this browser workflow with Playwright and produce a reliable script with run steps."
diff --git a/.agents/skills/playwright/assets/playwright-small.svg b/.agents/skills/playwright/assets/playwright-small.svg
deleted file mode 100644
index bf694d6..0000000
--- a/.agents/skills/playwright/assets/playwright-small.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="16" height="16" fill="currentColor" viewBox="0 0 16 16">
-  <path d="m8.55 7.568.124.028 5.16 1.548.137.054c.606.294.645 1.165.068 1.512l-.133.066-2.236.894-.894 2.236c-.285.713-1.263.714-1.578.065l-.054-.138-1.548-5.16a.866.866 0 0 1 .954-1.105ZM10 12.983l.715-1.787.037-.08a.865.865 0 0 1 .445-.402L12.983 10 8.721 8.72l1.278 4.262ZM4.723 10.38a.532.532 0 0 1 .752.752l-1.414 1.414a.532.532 0 1 1-.752-.752l1.414-1.414ZM2.27 5.86l1.932.517.1.039a.533.533 0 0 1-.269 1.007l-.106-.018-1.932-.517-.101-.039a.532.532 0 0 1 .27-1.006l.106.017Zm9.608-2.62a.532.532 0 0 1 .668.82l-1.414 1.414a.532.532 0 1 1-.752-.752l1.414-1.414.084-.068ZM6.237 1.618a.532.532 0 0 1 .652.377l.518 1.932.017.106a.533.533 0 0 1-1.007.27l-.039-.101-.517-1.932-.017-.106a.532.532 0 0 1 .393-.546Z"/>
-</svg>
diff --git a/.agents/skills/playwright/assets/playwright.png b/.agents/skills/playwright/assets/playwright.png
deleted file mode 100644
index c651868..0000000
Binary files a/.agents/skills/playwright/assets/playwright.png and /dev/null differ
diff --git a/.agents/skills/playwright/references/cli.md b/.agents/skills/playwright/references/cli.md
deleted file mode 100644
index ec0b4e1..0000000
--- a/.agents/skills/playwright/references/cli.md
+++ /dev/null
@@ -1,116 +0,0 @@
-# Playwright CLI Reference
-
-Use the wrapper script unless the CLI is already installed globally:
-
-```bash
-export CODEX_HOME="${CODEX_HOME:-$HOME/.codex}"
-export PWCLI="$CODEX_HOME/skills/playwright/scripts/playwright_cli.sh"
-"$PWCLI" --help
-```
-
-User-scoped skills install under `$CODEX_HOME/skills` (default: `~/.codex/skills`).
-
-Optional convenience alias:
-
-```bash
-alias pwcli="$PWCLI"
-```
-
-## Core
-
-```bash
-pwcli open https://example.com
-pwcli close
-pwcli snapshot
-pwcli click e3
-pwcli dblclick e7
-pwcli type "search terms"
-pwcli press Enter
-pwcli fill e5 "user@example.com"
-pwcli drag e2 e8
-pwcli hover e4
-pwcli select e9 "option-value"
-pwcli upload ./document.pdf
-pwcli check e12
-pwcli uncheck e12
-pwcli eval "document.title"
-pwcli eval "el => el.textContent" e5
-pwcli dialog-accept
-pwcli dialog-accept "confirmation text"
-pwcli dialog-dismiss
-pwcli resize 1920 1080
-```
-
-## Navigation
-
-```bash
-pwcli go-back
-pwcli go-forward
-pwcli reload
-```
-
-## Keyboard
-
-```bash
-pwcli press Enter
-pwcli press ArrowDown
-pwcli keydown Shift
-pwcli keyup Shift
-```
-
-## Mouse
-
-```bash
-pwcli mousemove 150 300
-pwcli mousedown
-pwcli mousedown right
-pwcli mouseup
-pwcli mouseup right
-pwcli mousewheel 0 100
-```
-
-## Save as
-
-```bash
-pwcli screenshot
-pwcli screenshot e5
-pwcli pdf
-```
-
-## Tabs
-
-```bash
-pwcli tab-list
-pwcli tab-new
-pwcli tab-new https://example.com/page
-pwcli tab-close
-pwcli tab-close 2
-pwcli tab-select 0
-```
-
-## DevTools
-
-```bash
-pwcli console
-pwcli console warning
-pwcli network
-pwcli run-code "await page.waitForTimeout(1000)"
-pwcli tracing-start
-pwcli tracing-stop
-```
-
-## Sessions
-
-Use a named session to isolate work:
-
-```bash
-pwcli --session todo open https://demo.playwright.dev/todomvc
-pwcli --session todo snapshot
-```
-
-Or set an environment variable once:
-
-```bash
-export PLAYWRIGHT_CLI_SESSION=todo
-pwcli open https://demo.playwright.dev/todomvc
-```
diff --git a/.agents/skills/playwright/references/workflows.md b/.agents/skills/playwright/references/workflows.md
deleted file mode 100644
index ffd45c0..0000000
--- a/.agents/skills/playwright/references/workflows.md
+++ /dev/null
@@ -1,95 +0,0 @@
-# Playwright CLI Workflows
-
-Use the wrapper script and snapshot often.
-Assume `PWCLI` is set and `pwcli` is an alias for `"$PWCLI"`.
-In this repo, run commands from `output/playwright/<label>/` to keep artifacts contained.
-
-## Standard interaction loop
-
-```bash
-pwcli open https://example.com
-pwcli snapshot
-pwcli click e3
-pwcli snapshot
-```
-
-## Form submission
-
-```bash
-pwcli open https://example.com/form --headed
-pwcli snapshot
-pwcli fill e1 "user@example.com"
-pwcli fill e2 "password123"
-pwcli click e3
-pwcli snapshot
-pwcli screenshot
-```
-
-## Data extraction
-
-```bash
-pwcli open https://example.com
-pwcli snapshot
-pwcli eval "document.title"
-pwcli eval "el => el.textContent" e12
-```
-
-## Debugging and inspection
-
-Capture console messages and network activity after reproducing an issue:
-
-```bash
-pwcli console warning
-pwcli network
-```
-
-Record a trace around a suspicious flow:
-
-```bash
-pwcli tracing-start
-# reproduce the issue
-pwcli tracing-stop
-pwcli screenshot
-```
-
-## Sessions
-
-Use sessions to isolate work across projects:
-
-```bash
-pwcli --session marketing open https://example.com
-pwcli --session marketing snapshot
-pwcli --session checkout open https://example.com/checkout
-```
-
-Or set the session once:
-
-```bash
-export PLAYWRIGHT_CLI_SESSION=checkout
-pwcli open https://example.com/checkout
-```
-
-## Configuration file
-
-By default, the CLI reads `playwright-cli.json` from the current directory. Use `--config` to point at a specific file.
-
-Minimal example:
-
-```json
-{
-  "browser": {
-    "launchOptions": {
-      "headless": false
-    },
-    "contextOptions": {
-      "viewport": { "width": 1280, "height": 720 }
-    }
-  }
-}
-```
-
-## Troubleshooting
-
-- If an element ref fails, run `pwcli snapshot` again and retry.
-- If the page looks wrong, re-open with `--headed` and resize the window.
-- If a flow depends on prior state, use a named `--session`.
diff --git a/.agents/skills/playwright/scripts/playwright_cli.sh b/.agents/skills/playwright/scripts/playwright_cli.sh
deleted file mode 100755
index 51fabc6..0000000
--- a/.agents/skills/playwright/scripts/playwright_cli.sh
+++ /dev/null
@@ -1,25 +0,0 @@
-#!/usr/bin/env bash
-set -euo pipefail
-
-if ! command -v npx >/dev/null 2>&1; then
-  echo "Error: npx is required but not found on PATH." >&2
-  exit 1
-fi
-
-has_session_flag="false"
-for arg in "$@"; do
-  case "$arg" in
-    --session|--session=*)
-      has_session_flag="true"
-      break
-      ;;
-  esac
-done
-
-cmd=(npx --yes --package @playwright/cli playwright-cli)
-if [[ "${has_session_flag}" != "true" && -n "${PLAYWRIGHT_CLI_SESSION:-}" ]]; then
-  cmd+=(--session "${PLAYWRIGHT_CLI_SESSION}")
-fi
-cmd+=("$@")
-
-exec "${cmd[@]}"
diff --git a/.agents/skills/vue-best-practices/LICENSE.md b/.agents/skills/vue-best-practices/LICENSE.md
deleted file mode 100644
index 3f08a54..0000000
--- a/.agents/skills/vue-best-practices/LICENSE.md
+++ /dev/null
@@ -1,21 +0,0 @@
-MIT License
-
-Copyright (c) 2025 hyf0, SerKo <https://github.com/serkodev>
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
diff --git a/.agents/skills/vue-best-practices/SKILL.md b/.agents/skills/vue-best-practices/SKILL.md
deleted file mode 100644
index feacd70..0000000
--- a/.agents/skills/vue-best-practices/SKILL.md
+++ /dev/null
@@ -1,154 +0,0 @@
----
-name: vue-best-practices
-description: MUST be used for Vue.js tasks. Strongly recommends Composition API with `<script setup>` and TypeScript as the standard approach. Covers Vue 3, SSR, Volar, vue-tsc. Load for any Vue, .vue files, Vue Router, Pinia, or Vite with Vue work. ALWAYS use Composition API unless the project explicitly requires Options API.
-license: MIT
-metadata:
-  author: github.com/vuejs-ai
-  version: "18.0.0"
----
-
-# Vue Best Practices Workflow
-
-Use this skill as an instruction set. Follow the workflow in order unless the user explicitly asks for a different order.
-
-## Core Principles
-- **Keep state predictable:** one source of truth, derive everything else.
-- **Make data flow explicit:** Props down, Events up for most cases.
-- **Favor small, focused components:** easier to test, reuse, and maintain.
-- **Avoid unnecessary re-renders:** use computed properties and watchers wisely.
-- **Readability counts:** write clear, self-documenting code.
-
-## 1) Confirm architecture before coding (required)
-
-- Default stack: Vue 3 + Composition API + `<script setup lang="ts">`.
-- If the project explicitly uses Options API, load `vue-options-api-best-practices` skill if available.
-- If the project explicitly uses JSX, load `vue-jsx-best-practices` skill if available.
-
-### 1.1 Must-read core references (required)
-
-- Before implementing any Vue task, make sure to read and apply these core references:
-  - `references/reactivity.md`
-  - `references/sfc.md`
-  - `references/component-data-flow.md`
-  - `references/composables.md`
-- Keep these references in active working context for the entire task, not only when a specific issue appears.
-
-### 1.2 Plan component boundaries before coding (required)
-
-Create a brief component map before implementation for any non-trivial feature.
-
-- Define each component's single responsibility in one sentence.
-- Keep entry/root and route-level view components as composition surfaces by default.
-- Move feature UI and feature logic out of entry/root/view components unless the task is intentionally a tiny single-file demo.
-- Define props/emits contracts for each child component in the map.
-- Prefer a feature folder layout (`components/<feature>/...`, `composables/use<Feature>.ts`) when adding more than one component.
-
-## 2) Apply essential Vue foundations (required)
-
-These are essential, must-know foundations. Apply all of them in every Vue task using the core references already loaded in section `1.1`.
-
-### Reactivity
-
-- Must-read reference from `1.1`: [reactivity](references/reactivity.md)
-- Keep source state minimal (`ref`/`reactive`), derive everything possible with `computed`.
-- Use watchers for side effects if needed.
-- Avoid recomputing expensive logic in templates.
-
-### SFC structure and template safety
-
-- Must-read reference from `1.1`: [sfc](references/sfc.md)
-- Keep SFC sections in this order: `<script>` → `<template>` → `<style>`.
-- Keep SFC responsibilities focused; split large components.
-- Keep templates declarative; move branching/derivation to script.
-- Apply Vue template safety rules (`v-html`, list rendering, conditional rendering choices).
-
-### Keep components focused
-
-Split a component when it has **more than one clear responsibility** (e.g. data orchestration + UI, or multiple independent UI sections).
-
-- Prefer **smaller components + composables** over one “mega component”
-- Move **UI sections** into child components (props in, events out).
-- Move **state/side effects** into composables (`useXxx()`).
-
-Apply objective split triggers. Split the component if **any** condition is true:
-
-- It owns both orchestration/state and substantial presentational markup for multiple sections.
-- It has 3+ distinct UI sections (for example: form, filters, list, footer/status).
-- A template block is repeated or could become reusable (item rows, cards, list entries).
-
-Entry/root and route view rule:
-
-- Keep entry/root and route view components thin: app shell/layout, provider wiring, and feature composition.
-- Do not place full feature implementations in entry/root/view components when those features contain independent parts.
-- For CRUD/list features (todo, table, catalog, inbox), split at least into:
-  - feature container component
-  - input/form component
-  - list (and/or item) component
-  - footer/actions or filter/status component
-- Allow a single-file implementation only for very small throwaway demos; if chosen, explicitly justify why splitting is unnecessary.
-
-### Component data flow
-
-- Must-read reference from `1.1`: [component-data-flow](references/component-data-flow.md)
-- Use props down, events up as the primary model.
-- Use `v-model` only for true two-way component contracts.
-- Use provide/inject only for deep-tree dependencies or shared context.
-- Keep contracts explicit and typed with `defineProps`, `defineEmits`, and `InjectionKey` as needed.
-
-### Composables
-
-- Must-read reference from `1.1`: [composables](references/composables.md)
-- Extract logic into composables when it is reused, stateful, or side-effect heavy.
-- Keep composable APIs small, typed, and predictable.
-- Separate feature logic from presentational components.
-
-## 3) Consider optional features only when requirements call for them
-
-### 3.1 Standard optional features
-
-Do not add these by default. Load the matching reference only when the requirement exists.
-
-- Slots: parent needs to control child content/layout -> [component-slots](references/component-slots.md)
-- Fallthrough attributes: wrapper/base components must forward attrs/events safely -> [component-fallthrough-attrs](references/component-fallthrough-attrs.md)
-- Built-in component `<KeepAlive>` for stateful view caching -> [component-keep-alive](references/component-keep-alive.md)
-- Built-in component `<Teleport>` for overlays/portals -> [component-teleport](references/component-teleport.md)
-- Built-in component `<Suspense>` for async subtree fallback boundaries -> [component-suspense](references/component-suspense.md)
-- Animation-related features: pick the simplest approach that matches the required motion behavior.
-  - Built-in component `<Transition>` for enter/leave effects -> [transition](references/component-transition.md)
-  - Built-in component `<TransitionGroup>` for animated list mutations -> [transition-group](references/component-transition-group.md)
-  - Class-based animation for non-enter/leave effects -> [animation-class-based-technique](references/animation-class-based-technique.md)
-  - State-driven animation for user-input-driven animation -> [animation-state-driven-technique](references/animation-state-driven-technique.md)
-
-### 3.2 Less-common optional features
-
-Use these only when there is explicit product or technical need.
-
-- Directives: behavior is DOM-specific and not a good composable/component fit -> [directives](references/directives.md)
-- Async components: heavy/rarely-used UI should be lazy loaded -> [component-async](references/component-async.md)
-- Render functions only when templates cannot express the requirement -> [render-functions](references/render-functions.md)
-- Plugins when behavior must be installed app-wide -> [plugins](references/plugins.md)
-- State management patterns: app-wide shared state crosses feature boundaries -> [state-management](references/state-management.md)
-
-## 4) Run performance optimization after behavior is correct
-
-Performance work is a post-functionality pass. Do not optimize before core behavior is implemented and verified.
-
-- Large list rendering bottlenecks -> [perf-virtualize-large-lists](references/perf-virtualize-large-lists.md)
-- Static subtrees re-rendering unnecessarily -> [perf-v-once-v-memo-directives](references/perf-v-once-v-memo-directives.md)
-- Over-abstraction in hot list paths -> [perf-avoid-component-abstraction-in-lists](references/perf-avoid-component-abstraction-in-lists.md)
-- Expensive updates triggered too often -> [updated-hook-performance](references/updated-hook-performance.md)
-
-## 5) Final self-check before finishing
-
-- Core behavior works and matches requirements.
-- All must-read references were read and applied.
-- Reactivity model is minimal and predictable.
-- SFC structure and template rules are followed.
-- Components are focused and well-factored, splitting when needed.
-- Entry/root and route view components remain composition surfaces unless there is an explicit small-demo exception.
-- Component split decisions are explicit and defensible (responsibility boundaries are clear).
-- Data flow contracts are explicit and typed.
-- Composables are used where reuse/complexity justifies them.
-- Moved state/side effects into composables if applicable
-- Optional features are used only when requirements demand them.
-- Performance changes were applied only after functionality was complete.
diff --git a/.agents/skills/vue-best-practices/SYNC.md b/.agents/skills/vue-best-practices/SYNC.md
deleted file mode 100644
index e82170d..0000000
--- a/.agents/skills/vue-best-practices/SYNC.md
+++ /dev/null
@@ -1,5 +0,0 @@
-# Sync Info
-
-- **Source:** `vendor/vuejs-ai/skills/vue-best-practices`
-- **Git SHA:** `f3dd1bf4d3ac78331bdc903e4519d561c538ca6a`
-- **Synced:** 2026-03-16
diff --git a/.agents/skills/vue-best-practices/references/animation-class-based-technique.md b/.agents/skills/vue-best-practices/references/animation-class-based-technique.md
deleted file mode 100644
index 316e090..0000000
--- a/.agents/skills/vue-best-practices/references/animation-class-based-technique.md
+++ /dev/null
@@ -1,254 +0,0 @@
----
-title: Use Class-based Animations for Non-Enter/Leave Effects
-impact: LOW
-impactDescription: Class-based animations are simpler and more performant for elements that remain in the DOM
-type: best-practice
-tags: [vue3, animation, css, class-binding, state]
----
-
-# Use Class-based Animations for Non-Enter/Leave Effects
-
-**Impact: LOW** - For animations on elements that are not entering or leaving the DOM, use CSS class-based animations triggered by Vue's reactive state. This is simpler than `<Transition>` and more appropriate for feedback animations like shake, pulse, or highlight effects.
-
-## Task List
-
-- Use class-based animations for elements staying in the DOM
-- Use `<Transition>` only for enter/leave animations
-- Combine CSS animations with Vue's class bindings (`:class`)
-- Consider using `setTimeout` to auto-remove animation classes
-
-**When to Use Class-based Animations:**
-- User feedback (shake on error, pulse on success)
-- Attention-grabbing effects (highlight changes)
-- Hover/focus states that need more than CSS transitions
-- Any animation where the element stays mounted
-
-**When to Use Transition Component:**
-- Elements entering/leaving the DOM (v-if/v-show)
-- Route transitions
-- List item additions/removals
-
-## Basic Pattern
-
-```vue
-<template>
-  <div :class="{ shake: showError }">
-    <button @click="submitForm">Submit</button>
-    <span v-if="showError">This feature is disabled!</span>
-  </div>
-</template>
-
-<script setup>
-import { ref } from 'vue'
-
-const showError = ref(false)
-
-function submitForm() {
-  if (!isValid()) {
-    // Trigger shake animation
-    showError.value = true
-
-    // Auto-remove class after animation completes
-    setTimeout(() => {
-      showError.value = false
-    }, 820)  // Match animation duration
-  }
-}
-</script>
-
-<style>
-.shake {
-  animation: shake 0.82s cubic-bezier(0.36, 0.07, 0.19, 0.97) both;
-  transform: translate3d(0, 0, 0);  /* Enable GPU acceleration */
-}
-
-@keyframes shake {
-  10%, 90% { transform: translate3d(-1px, 0, 0); }
-  20%, 80% { transform: translate3d(2px, 0, 0); }
-  30%, 50%, 70% { transform: translate3d(-4px, 0, 0); }
-  40%, 60% { transform: translate3d(4px, 0, 0); }
-}
-</style>
-```
-
-## Common Animation Patterns
-
-### Pulse on Success
-
-```vue
-<template>
-  <button
-    @click="save"
-    :class="{ pulse: saved }"
-  >
-    {{ saved ? 'Saved!' : 'Save' }}
-  </button>
-</template>
-
-<script setup>
-import { ref } from 'vue'
-
-const saved = ref(false)
-
-async function save() {
-  await saveData()
-  saved.value = true
-  setTimeout(() => saved.value = false, 1000)
-}
-</script>
-
-<style>
-.pulse {
-  animation: pulse 0.5s ease-in-out;
-}
-
-@keyframes pulse {
-  0%, 100% { transform: scale(1); }
-  50% { transform: scale(1.05); }
-}
-</style>
-```
-
-### Highlight on Change
-
-```vue
-<template>
-  <div
-    :class="{ highlight: justUpdated }"
-  >
-    Value: {{ value }}
-  </div>
-</template>
-
-<script setup>
-import { ref, watch } from 'vue'
-
-const value = ref(0)
-const justUpdated = ref(false)
-
-watch(value, () => {
-  justUpdated.value = true
-  setTimeout(() => justUpdated.value = false, 1000)
-})
-</script>
-
-<style>
-.highlight {
-  animation: highlight 1s ease-out;
-}
-
-@keyframes highlight {
-  0% { background-color: yellow; }
-  100% { background-color: transparent; }
-}
-</style>
-```
-
-### Bounce Attention
-
-```vue
-<template>
-  <div
-    :class="{ bounce: needsAttention }"
-    @animationend="needsAttention = false"
-  >
-    <BellIcon />
-  </div>
-</template>
-
-<script setup>
-import { ref } from 'vue'
-
-const needsAttention = ref(false)
-
-function notifyUser() {
-  needsAttention.value = true
-  // No setTimeout needed - using animationend event
-}
-</script>
-
-<style>
-.bounce {
-  animation: bounce 0.5s ease;
-}
-
-@keyframes bounce {
-  0%, 100% { transform: translateY(0); }
-  50% { transform: translateY(-10px); }
-}
-</style>
-```
-
-## Using animationend Event
-
-Instead of `setTimeout`, use the `animationend` event for cleaner code:
-
-```vue
-<template>
-  <div
-    :class="{ animate: isAnimating }"
-    @animationend="isAnimating = false"
-  >
-    Content
-  </div>
-</template>
-
-<script setup>
-import { ref } from 'vue'
-
-const isAnimating = ref(false)
-
-function triggerAnimation() {
-  isAnimating.value = true
-  // Class is automatically removed when animation ends
-}
-</script>
-```
-
-## Composable for Reusable Animations
-
-```javascript
-// composables/useAnimation.js
-import { ref } from 'vue'
-
-export function useAnimation(duration = 500) {
-  const isAnimating = ref(false)
-
-  function trigger() {
-    isAnimating.value = true
-    setTimeout(() => {
-      isAnimating.value = false
-    }, duration)
-  }
-
-  return {
-    isAnimating,
-    trigger
-  }
-}
-```
-
-```vue
-<script setup>
-import { useAnimation } from '@/composables/useAnimation'
-
-const shake = useAnimation(820)
-const pulse = useAnimation(500)
-</script>
-
-<template>
-  <button
-    :class="{ shake: shake.isAnimating.value }"
-    @click="shake.trigger()"
-  >
-    Shake me
-  </button>
-
-  <button
-    :class="{ pulse: pulse.isAnimating.value }"
-    @click="pulse.trigger()"
-  >
-    Pulse me
-  </button>
-</template>
-```
diff --git a/.agents/skills/vue-best-practices/references/animation-state-driven-technique.md b/.agents/skills/vue-best-practices/references/animation-state-driven-technique.md
deleted file mode 100644
index 26b0120..0000000
--- a/.agents/skills/vue-best-practices/references/animation-state-driven-technique.md
+++ /dev/null
@@ -1,291 +0,0 @@
----
-title: State-driven Animations with CSS Transitions and Style Bindings
-impact: LOW
-impactDescription: Combining Vue's reactive style bindings with CSS transitions creates smooth, interactive animations
-type: best-practice
-tags: [vue3, animation, css, transition, style-binding, state, interactive]
----
-
-# State-driven Animations with CSS Transitions and Style Bindings
-
-**Impact: LOW** - For responsive, interactive animations that react to user input or state changes, combine Vue's dynamic style bindings with CSS transitions. This creates smooth animations that interpolate values in real-time based on state.
-
-## Task List
-
-- Use `:style` binding for dynamic properties that change frequently
-- Add CSS `transition` property to smoothly animate between values
-- Consider using `transform` and `opacity` for GPU-accelerated animations
-- For complex value interpolation, use watchers with animation libraries
-
-## Basic Pattern
-
-```vue
-<template>
-  <div
-    @mousemove="onMousemove"
-    :style="{ backgroundColor: `hsl(${hue}, 80%, 50%)` }"
-    class="interactive-area"
-  >
-    <p>Move your mouse across this div...</p>
-    <p>Hue: {{ hue }}</p>
-  </div>
-</template>
-
-<script setup>
-import { ref } from 'vue'
-
-const hue = ref(0)
-
-function onMousemove(e) {
-  // Map mouse X position to hue (0-360)
-  const rect = e.currentTarget.getBoundingClientRect()
-  hue.value = Math.round((e.clientX - rect.left) / rect.width * 360)
-}
-</script>
-
-<style>
-.interactive-area {
-  transition: background-color 0.3s ease;
-  height: 200px;
-  display: flex;
-  flex-direction: column;
-  align-items: center;
-  justify-content: center;
-}
-</style>
-```
-
-## Common Use Cases
-
-### Following Mouse Position
-
-```vue
-<template>
-  <div
-    class="container"
-    @mousemove="onMousemove"
-  >
-    <div
-      class="follower"
-      :style="{
-        transform: `translate(${x}px, ${y}px)`
-      }"
-    />
-  </div>
-</template>
-
-<script setup>
-import { ref } from 'vue'
-
-const x = ref(0)
-const y = ref(0)
-
-function onMousemove(e) {
-  const rect = e.currentTarget.getBoundingClientRect()
-  x.value = e.clientX - rect.left
-  y.value = e.clientY - rect.top
-}
-</script>
-
-<style>
-.container {
-  position: relative;
-  height: 300px;
-}
-
-.follower {
-  position: absolute;
-  width: 20px;
-  height: 20px;
-  background: blue;
-  border-radius: 50%;
-  /* Smooth following with transition */
-  transition: transform 0.1s ease-out;
-  /* Prevent the follower from triggering mousemove */
-  pointer-events: none;
-}
-</style>
-```
-
-### Progress Animation
-
-```vue
-<template>
-  <div class="progress-container">
-    <div
-      class="progress-bar"
-      :style="{ width: `${progress}%` }"
-    />
-  </div>
-  <input
-    type="range"
-    v-model.number="progress"
-    min="0"
-    max="100"
-  />
-</template>
-
-<script setup>
-import { ref } from 'vue'
-
-const progress = ref(0)
-</script>
-
-<style>
-.progress-container {
-  height: 20px;
-  background: #e0e0e0;
-  border-radius: 10px;
-  overflow: hidden;
-}
-
-.progress-bar {
-  height: 100%;
-  background: linear-gradient(90deg, #4CAF50, #8BC34A);
-  transition: width 0.3s ease;
-}
-</style>
-```
-
-### Scroll-based Animation
-
-```vue
-<template>
-  <div
-    class="hero"
-    :style="{
-      opacity: heroOpacity,
-      transform: `translateY(${scrollOffset}px)`
-    }"
-  >
-    <h1>Scroll Down</h1>
-  </div>
-</template>
-
-<script setup>
-import { ref, computed, onMounted, onUnmounted } from 'vue'
-
-const scrollY = ref(0)
-
-const heroOpacity = computed(() => {
-  return Math.max(0, 1 - scrollY.value / 300)
-})
-
-const scrollOffset = computed(() => {
-  return scrollY.value * 0.5  // Parallax effect
-})
-
-function handleScroll() {
-  scrollY.value = window.scrollY
-}
-
-onMounted(() => {
-  window.addEventListener('scroll', handleScroll, { passive: true })
-})
-
-onUnmounted(() => {
-  window.removeEventListener('scroll', handleScroll)
-})
-</script>
-
-<style>
-.hero {
-  height: 100vh;
-  display: flex;
-  align-items: center;
-  justify-content: center;
-  /* Note: No transition for scroll-based animations - they should be instant */
-}
-</style>
-```
-
-### Color Theme Transition
-
-```vue
-<template>
-  <div
-    class="app"
-    :style="themeStyles"
-  >
-    <button @click="toggleTheme">Toggle Theme</button>
-    <p>Current theme: {{ isDark ? 'Dark' : 'Light' }}</p>
-  </div>
-</template>
-
-<script setup>
-import { ref, computed } from 'vue'
-
-const isDark = ref(false)
-
-const themeStyles = computed(() => ({
-  '--bg-color': isDark.value ? '#1a1a1a' : '#ffffff',
-  '--text-color': isDark.value ? '#ffffff' : '#1a1a1a',
-  backgroundColor: 'var(--bg-color)',
-  color: 'var(--text-color)'
-}))
-
-function toggleTheme() {
-  isDark.value = !isDark.value
-}
-</script>
-
-<style>
-.app {
-  min-height: 100vh;
-  transition: background-color 0.5s ease, color 0.5s ease;
-}
-</style>
-```
-
-## Advanced: Numerical Tweening with Watchers
-
-For smooth number animations (counters, stats), use watchers with animation libraries:
-
-```vue
-<template>
-  <div>
-    <input v-model.number="targetNumber" type="number" />
-    <p class="counter">{{ displayNumber.toFixed(0) }}</p>
-  </div>
-</template>
-
-<script setup>
-import { computed, ref, reactive, watch } from 'vue'
-import gsap from 'gsap'
-
-const targetNumber = ref(0)
-const tweened = reactive({ value: 0 })
-
-// Computed for display
-const displayNumber = computed(() => tweened.value)
-
-watch(targetNumber, (newValue) => {
-  gsap.to(tweened, {
-    duration: 0.5,
-    value: Number(newValue) || 0,
-    ease: 'power2.out'
-  })
-})
-</script>
-```
-
-## Performance Considerations
-
-```vue
-<style>
-/* GOOD: GPU-accelerated properties */
-.element {
-  transition: transform 0.3s ease, opacity 0.3s ease;
-}
-
-/* AVOID: Properties that trigger layout recalculation */
-.element {
-  transition: width 0.3s ease, height 0.3s ease, margin 0.3s ease;
-}
-
-/* For high-frequency updates, consider will-change */
-.frequently-animated {
-  will-change: transform;
-}
-</style>
-```
diff --git a/.agents/skills/vue-best-practices/references/component-async.md b/.agents/skills/vue-best-practices/references/component-async.md
deleted file mode 100644
index b39310d..0000000
--- a/.agents/skills/vue-best-practices/references/component-async.md
+++ /dev/null
@@ -1,97 +0,0 @@
----
-title: Async Component Best Practices
-impact: MEDIUM
-impactDescription: Poor async component strategy can delay interactivity in SSR apps and create loading UI flicker
-type: best-practice
-tags: [vue3, async-components, ssr, hydration, performance, ux]
----
-
-# Async Component Best Practices
-
-**Impact: MEDIUM** - Async components should reduce JavaScript cost without degrading perceived performance. Focus on hydration timing in SSR and stable loading UX.
-
-## Task List
-
-- Use lazy hydration strategies for non-critical SSR component trees
-- Import only the hydration helpers you actually use
-- Keep `loadingComponent` delay near the default `200ms` unless real UX data suggests otherwise
-- Configure `delay` and `timeout` together for predictable loading behavior
-
-## Use Lazy Hydration Strategies in SSR
-
-In Vue 3.5+, async components can delay hydration until idle time, visibility, media query match, or user interaction.
-
-**BAD:**
-```vue
-<script setup lang="ts">
-import { defineAsyncComponent } from 'vue'
-
-const AsyncComments = defineAsyncComponent({
-  loader: () => import('./Comments.vue')
-})
-</script>
-```
-
-**GOOD:**
-```vue
-<script setup lang="ts">
-import {
-  defineAsyncComponent,
-  hydrateOnVisible,
-  hydrateOnIdle
-} from 'vue'
-
-const AsyncComments = defineAsyncComponent({
-  loader: () => import('./Comments.vue'),
-  hydrate: hydrateOnVisible({ rootMargin: '100px' })
-})
-
-const AsyncFooter = defineAsyncComponent({
-  loader: () => import('./Footer.vue'),
-  hydrate: hydrateOnIdle(5000)
-})
-</script>
-```
-
-## Prevent Loading Spinner Flicker
-
-Avoid showing loading UI immediately for components that usually resolve quickly.
-
-**BAD:**
-```vue
-<script setup lang="ts">
-import { defineAsyncComponent } from 'vue'
-import LoadingSpinner from './LoadingSpinner.vue'
-
-const AsyncDashboard = defineAsyncComponent({
-  loader: () => import('./Dashboard.vue'),
-  loadingComponent: LoadingSpinner,
-  delay: 0
-})
-</script>
-```
-
-**GOOD:**
-```vue
-<script setup lang="ts">
-import { defineAsyncComponent } from 'vue'
-import LoadingSpinner from './LoadingSpinner.vue'
-import ErrorDisplay from './ErrorDisplay.vue'
-
-const AsyncDashboard = defineAsyncComponent({
-  loader: () => import('./Dashboard.vue'),
-  loadingComponent: LoadingSpinner,
-  errorComponent: ErrorDisplay,
-  delay: 200,
-  timeout: 30000
-})
-</script>
-```
-
-## Delay Guidelines
-
-| Scenario | Recommended Delay |
-|----------|-------------------|
-| Small component, fast network | `200ms` |
-| Known heavy component | `100ms` |
-| Background or non-critical UI | `300-500ms` |
diff --git a/.agents/skills/vue-best-practices/references/component-data-flow.md b/.agents/skills/vue-best-practices/references/component-data-flow.md
deleted file mode 100644
index e1add1e..0000000
--- a/.agents/skills/vue-best-practices/references/component-data-flow.md
+++ /dev/null
@@ -1,307 +0,0 @@
----
-title: Component Data Flow Best Practices
-impact: HIGH
-impactDescription: Clear data flow between components prevents state bugs, stale UI, and brittle coupling
-type: best-practice
-tags: [vue3, props, emits, v-model, provide-inject, data-flow, typescript]
----
-
-# Component Data Flow Best Practices
-
-**Impact: HIGH** - Vue components stay reliable when data flow is explicit: props go down, events go up, `v-model` handles two-way bindings, and provide/inject supports cross-tree dependencies. Blurring these boundaries leads to stale state, hidden coupling, and hard-to-debug UI.
-
-The main principle of data flow in Vue.js is **Props Down / Events Up**. This is the most maintainable default, and one-way flow scales well.
-
-## Task List
-
-- Treat props as read-only inputs
-- Use props/emit for component communication; reserve refs for imperative actions
-- When refs are required for imperative APIs, type them with template refs
-- Emit events instead of mutating parent state directly
-- Use `defineModel` for v-model in modern Vue (3.4+)
-- Handle v-model modifiers deliberately in child components
-- Use symbols for provide/inject keys to avoid props drilling (over ~3 layers)
-- Keep mutations in the provider or expose explicit actions
-- In TypeScript projects, prefer type-based `defineProps`, `defineEmits`, and `InjectionKey`
-
-## Props: One-Way Data Down
-
-Props are inputs. Do not mutate them in the child.
-
-**BAD:**
-```vue
-<script setup>
-const props = defineProps({ count: Number })
-
-function increment() {
-  props.count++
-}
-</script>
-```
-
-**GOOD:**
-
-If state needs to change, emit an event, use `v-model` or create a local copy.
-
-## Prefer props/emit over component refs
-
-**BAD:**
-```vue
-<script setup>
-import { ref } from 'vue'
-import UserForm from './UserForm.vue'
-
-const formRef = ref(null)
-
-function submitForm() {
-  if (formRef.value.isValid) {
-    formRef.value.submit()
-  }
-}
-</script>
-
-<template>
-  <UserForm ref="formRef" />
-  <button @click="submitForm">Submit</button>
-</template>
-```
-
-**GOOD:**
-```vue
-<script setup>
-import UserForm from './UserForm.vue'
-
-function handleSubmit(formData) {
-  api.submit(formData)
-}
-</script>
-
-<template>
-  <UserForm @submit="handleSubmit" />
-</template>
-```
-
-## Type component refs when imperative access is required
-
-Prefer props/emits by default. When a parent must call an exposed child method, type the ref explicitly and expose only the intended API from the child with `defineExpose`.
-
-**BAD:**
-```vue
-<script setup lang="ts">
-import { ref, onMounted } from 'vue'
-import DialogPanel from './DialogPanel.vue'
-
-const panelRef = ref(null)
-
-onMounted(() => {
-  panelRef.value.open()
-})
-</script>
-
-<template>
-  <DialogPanel ref="panelRef" />
-</template>
-```
-
-**GOOD:**
-```vue
-<!-- DialogPanel.vue -->
-<script setup lang="ts">
-function open() {}
-
-defineExpose({ open })
-</script>
-```
-
-```vue
-<!-- Parent.vue -->
-<script setup lang="ts">
-import { onMounted, useTemplateRef } from 'vue'
-import DialogPanel from './DialogPanel.vue'
-
-// Vue 3.5+ with useTemplateRef
-const panelRef = useTemplateRef('panelRef')
-
-// Before Vue 3.5 with manual typing and ref
-// const panelRef = ref<InstanceType<typeof DialogPanel> | null>(null)
-
-onMounted(() => {
-  panelRef.value?.open()
-})
-</script>
-
-<template>
-  <DialogPanel ref="panelRef" />
-</template>
-```
-
-## Emits: Explicit Events Up
-
-Component events do not bubble. If a parent needs to know about an event, re-emit it explicitly.
-
-**BAD:**
-```vue
-<!-- Parent expects "saved" from grandchild, but it won't bubble -->
-<Child @saved="onSaved" />
-```
-
-**GOOD:**
-```vue
-<!-- Child.vue -->
-<script setup>
-const emit = defineEmits(['saved'])
-
-function onGrandchildSaved(payload) {
-  emit('saved', payload)
-}
-</script>
-
-<template>
-  <Grandchild @saved="onGrandchildSaved" />
-</template>
-```
-
-**Event naming:** use kebab-case in templates and camelCase in script:
-```vue
-<script setup>
-const emit = defineEmits(['updateUser'])
-</script>
-
-<template>
-  <ProfileForm @update-user="emit('updateUser', $event)" />
-</template>
-```
-
-## `v-model`: Predictable Two-Way Bindings
-
-Use `defineModel` by default for component bindings and emit updates on input. Only use the `modelValue` + `update:modelValue` pattern if you are on Vue < 3.4.
-
-**BAD:**
-```vue
-<script setup>
-const props = defineProps({ value: String })
-</script>
-
-<template>
-  <input :value="props.value" @input="$emit('input', $event.target.value)" />
-</template>
-```
-
-**GOOD (Vue 3.4+):**
-```vue
-<script setup>
-const model = defineModel({ type: String })
-</script>
-
-<template>
-  <input v-model="model" />
-</template>
-```
-
-**GOOD (Vue < 3.4):**
-```vue
-<script setup>
-const props = defineProps({ modelValue: String })
-const emit = defineEmits(['update:modelValue'])
-</script>
-
-<template>
-  <input
-    :value="props.modelValue"
-    @input="emit('update:modelValue', $event.target.value)"
-  />
-</template>
-```
-
-If you need the updated value immediately after a change, use the input event value or `nextTick` in the parent.
-
-## Provide/Inject: Shared Context Without Prop Drilling
-
-Use provide/inject for cross-tree state, but keep mutations centralized in the provider and expose explicit actions.
-
-**BAD:**
-```vue
-// Provider.vue
-provide('theme', reactive({ dark: false }))
-
-// Consumer.vue
-const theme = inject('theme')
-// Mutating shared state from any depth becomes hard to track
-theme.dark = true
-```
-
-**GOOD:**
-```vue
-// Provider.vue
-const theme = reactive({ dark: false })
-const toggleTheme = () => { theme.dark = !theme.dark }
-
-provide(themeKey, readonly(theme))
-provide(themeActionsKey, { toggleTheme })
-
-// Consumer.vue
-const theme = inject(themeKey)
-const { toggleTheme } = inject(themeActionsKey)
-```
-
-Use symbols for keys to avoid collisions in large apps:
-```ts
-export const themeKey = Symbol('theme')
-export const themeActionsKey = Symbol('theme-actions')
-```
-
-## Use TypeScript Contracts for Public Component APIs
-
-In TypeScript projects, type component boundaries directly with `defineProps`, `defineEmits`, and `InjectionKey` so invalid payloads and mismatched injections fail at compile time.
-
-**BAD:**
-```vue
-<script setup lang="ts">
-import { inject } from 'vue'
-
-const props = defineProps({
-  userId: String
-})
-
-const emit = defineEmits(['save'])
-const settings = inject('settings')
-
-// Payload shape is not checked here
-emit('save', 123)
-
-// Key is string-based and not type-safe
-settings?.theme = 'dark'
-</script>
-```
-
-**GOOD:**
-```vue
-<script setup lang="ts">
-import { inject, provide } from 'vue'
-import type { InjectionKey } from 'vue'
-
-interface Props {
-  userId: string
-}
-
-interface Emits {
-  save: [payload: { id: string; draft: boolean }]
-}
-
-interface Settings {
-  theme: 'light' | 'dark'
-}
-
-const settingsKey: InjectionKey<Settings> = Symbol('settings')
-
-const props = defineProps<Props>()
-const emit = defineEmits<Emits>()
-
-provide(settingsKey, { theme: 'light' })
-
-const settings = inject(settingsKey)
-if (settings) {
-  emit('save', { id: props.userId, draft: false })
-}
-</script>
-```
diff --git a/.agents/skills/vue-best-practices/references/component-fallthrough-attrs.md b/.agents/skills/vue-best-practices/references/component-fallthrough-attrs.md
deleted file mode 100644
index 5362fa4..0000000
--- a/.agents/skills/vue-best-practices/references/component-fallthrough-attrs.md
+++ /dev/null
@@ -1,174 +0,0 @@
----
-title: Component Fallthrough Attributes Best Practices
-impact: MEDIUM
-impactDescription: Incorrect $attrs access and reactivity assumptions can cause undefined values and watchers that never run
-type: best-practice
-tags: [vue3, attrs, fallthrough-attributes, composition-api, reactivity]
----
-
-# Component Fallthrough Attributes Best Practices
-
-**Impact: MEDIUM** - Fallthrough attributes are straightforward once you follow Vue's conventions: hyphenated names use bracket notation, listener keys are camelCase `onX`, and `useAttrs()` is current-but-not-reactive.
-
-## Task List
-
-- Access hyphenated attribute names with bracket notation (for example `attrs['data-testid']`)
-- Access event listeners with camelCase `onX` keys (for example `attrs.onClick`)
-- Do not `watch()` values returned from `useAttrs()`; those watchers do not trigger on attr changes
-- Use `onUpdated()` for attr-driven side effects
-- Promote frequently observed attrs to props when reactive observation is required
-
-## Access Attribute and Listener Keys Correctly
-
-Hyphenated attribute names preserve their original casing in JavaScript, so dot notation does not work for keys that include `-`.
-
-**BAD:**
-```vue
-<script setup>
-import { useAttrs } from 'vue'
-
-const attrs = useAttrs()
-
-console.log(attrs.data-testid)  // Syntax error
-console.log(attrs.dataTestid)   // undefined for data-testid
-console.log(attrs['on-click'])  // undefined
-console.log(attrs['@click'])    // undefined
-</script>
-```
-
-**GOOD:**
-```vue
-<script setup>
-import { useAttrs } from 'vue'
-
-const attrs = useAttrs()
-
-console.log(attrs['data-testid'])
-console.log(attrs['aria-label'])
-console.log(attrs['foo-bar'])
-
-console.log(attrs.onClick)
-console.log(attrs.onCustomEvent)
-console.log(attrs.onMouseEnter)
-</script>
-```
-
-### Naming Reference
-
-| Parent Usage | Access in `attrs` |
-|--------------|-------------------|
-| `class="foo"` | `attrs.class` |
-| `data-id="123"` | `attrs['data-id']` |
-| `aria-label="..."` | `attrs['aria-label']` |
-| `foo-bar="baz"` | `attrs['foo-bar']` |
-| `@click="fn"` | `attrs.onClick` |
-| `@custom-event="fn"` | `attrs.onCustomEvent` |
-| `@update:modelValue="fn"` | `attrs['onUpdate:modelValue']` |
-
-## `useAttrs()` Is Not Reactive
-
-`useAttrs()` always reflects the latest values, but it is intentionally not reactive for watcher tracking.
-
-**BAD:**
-```vue
-<script setup>
-import { watch, watchEffect, useAttrs } from 'vue'
-
-const attrs = useAttrs()
-
-watch(
-  () => attrs.someAttr,
-  (newValue) => {
-    console.log('Changed:', newValue) // Never runs on attr changes
-  }
-)
-
-watchEffect(() => {
-  console.log(attrs.class) // Runs on setup, not on attr updates
-})
-</script>
-```
-
-**GOOD:**
-```vue
-<script setup>
-import { onUpdated, useAttrs } from 'vue'
-
-const attrs = useAttrs()
-
-onUpdated(() => {
-  console.log('Latest attrs:', attrs)
-})
-</script>
-```
-
-**GOOD:**
-```vue
-<script setup>
-import { watch } from 'vue'
-
-const props = defineProps({
-  someAttr: String
-})
-
-watch(
-  () => props.someAttr,
-  (newValue) => {
-    console.log('Changed:', newValue)
-  }
-)
-</script>
-```
-
-## Common Patterns
-
-### Check for optional attrs safely
-
-```vue
-<script setup>
-import { computed, useAttrs } from 'vue'
-
-const attrs = useAttrs()
-
-const hasTestId = computed(() => 'data-testid' in attrs)
-const ariaLabel = computed(() => attrs['aria-label'] ?? 'Default label')
-</script>
-```
-
-### Forward listeners after internal logic
-
-```vue
-<script setup>
-import { useAttrs } from 'vue'
-
-defineOptions({ inheritAttrs: false })
-
-const attrs = useAttrs()
-
-function handleClick(event) {
-  console.log('Internal handling first')
-  attrs.onClick?.(event)
-}
-</script>
-
-<template>
-  <button @click="handleClick">
-    <slot />
-  </button>
-</template>
-```
-
-## TypeScript Notes
-
-`useAttrs()` is typed as `Record<string, unknown>`, so cast individual keys when needed.
-
-```vue
-<script setup lang="ts">
-import { useAttrs } from 'vue'
-
-const attrs = useAttrs()
-
-const testId = attrs['data-testid'] as string | undefined
-const onClick = attrs.onClick as ((event: MouseEvent) => void) | undefined
-</script>
-```
diff --git a/.agents/skills/vue-best-practices/references/component-keep-alive.md b/.agents/skills/vue-best-practices/references/component-keep-alive.md
deleted file mode 100644
index f887691..0000000
--- a/.agents/skills/vue-best-practices/references/component-keep-alive.md
+++ /dev/null
@@ -1,137 +0,0 @@
----
-title: KeepAlive Component Best Practices
-impact: HIGH
-impactDescription: KeepAlive caches component instances; misuse causes stale data, memory growth, or unexpected lifecycle behavior
-type: best-practice
-tags: [vue3, keepalive, cache, performance, router, dynamic-components]
----
-
-# KeepAlive Component Best Practices
-
-**Impact: HIGH** - `<KeepAlive>` caches component instances instead of destroying them. Use it to preserve state across switches, but manage cache size and freshness explicitly to avoid memory growth or stale UI.
-
-## Task List
-
-- Use KeepAlive only where state preservation improves UX
-- Set a reasonable `max` to cap cache size
-- Declare component names for include/exclude matching
-- Use `onActivated`/`onDeactivated` for cache-aware logic
-- Decide how and when cached views refresh their data
-- Avoid caching memory-heavy or security-sensitive views
-
-## When to Use KeepAlive
-
-Use KeepAlive when switching between views where state should persist (tabs, multi-step forms, dashboards). Avoid it when each visit should start fresh.
-
-**BAD:**
-```vue
-<template>
-  <!-- State resets on every switch -->
-  <component :is="currentTab" />
-</template>
-```
-
-**GOOD:**
-```vue
-<template>
-  <!-- State preserved between switches -->
-  <KeepAlive>
-    <component :is="currentTab" />
-  </KeepAlive>
-</template>
-```
-
-## When NOT to Use KeepAlive
-
-- Search or filter pages where users expect fresh results
-- Memory-heavy components (maps, large tables, media players)
-- Sensitive flows where data must be cleared on exit
-- Components with heavy background activity you cannot pause
-
-## Limit and Control the Cache
-
-Always cap cache size with `max` and restrict caching to specific components when possible.
-
-```vue
-<template>
-  <KeepAlive :max="5" include="Dashboard,Settings">
-    <component :is="currentView" />
-  </KeepAlive>
-</template>
-```
-
-## Ensure Component Names Match include/exclude
-
-`include` and `exclude` match the component `name` option. Explicitly set names for reliable caching.
-
-```vue
-<!-- TabA.vue -->
-<script setup>
-defineOptions({ name: 'TabA' })
-</script>
-```
-
-```vue
-<template>
-  <KeepAlive include="TabA,TabB">
-    <component :is="currentTab" />
-  </KeepAlive>
-</template>
-```
-
-## Cache Invalidation Strategies
-
-Vue 3 has no direct API to remove a specific cached instance. Use keys or dynamic include/exclude to force refreshes.
-
-```vue
-<script setup>
-import { ref, reactive } from 'vue'
-
-const currentView = ref('Dashboard')
-const viewKeys = reactive({ Dashboard: 0, Settings: 0 })
-
-function invalidateCache(view) {
-  viewKeys[view]++
-}
-</script>
-
-<template>
-  <KeepAlive>
-    <component :is="currentView" :key="`${currentView}-${viewKeys[currentView]}`" />
-  </KeepAlive>
-</template>
-```
-
-## Lifecycle Hooks for Cached Components
-
-Cached components are not destroyed on switch. Use activation hooks for refresh and cleanup.
-
-```vue
-<script setup>
-import { onActivated, onDeactivated } from 'vue'
-
-onActivated(() => {
-  refreshData()
-})
-
-onDeactivated(() => {
-  pauseTimers()
-})
-</script>
-```
-
-## Router Caching and Freshness
-
-Decide whether navigation should show cached state or a fresh view. A common pattern is to key by route when params change.
-
-```vue
-<template>
-  <router-view v-slot="{ Component, route }">
-    <KeepAlive>
-      <component :is="Component" :key="route.fullPath" />
-    </KeepAlive>
-  </router-view>
-</template>
-```
-
-If you want cache reuse but fresh data, refresh in `onActivated` and compare query/params before fetching.
diff --git a/.agents/skills/vue-best-practices/references/component-slots.md b/.agents/skills/vue-best-practices/references/component-slots.md
deleted file mode 100644
index f77a91c..0000000
--- a/.agents/skills/vue-best-practices/references/component-slots.md
+++ /dev/null
@@ -1,216 +0,0 @@
----
-title: Component Slots Best Practices
-impact: MEDIUM
-impactDescription: Poor slot API design causes empty DOM wrappers, weak TypeScript safety, brittle defaults, and unnecessary component overhead
-type: best-practice
-tags: [vue3, slots, components, typescript, composables]
----
-
-# Component Slots Best Practices
-
-**Impact: MEDIUM** - Slots are a core component API surface in Vue. Structure them intentionally so templates stay predictable, typed, and performant.
-
-## Task List
-
-- Use shorthand syntax for named slots (`#` instead of `v-slot:`)
-- Render optional slot wrapper elements only when slot content exists (`$slots` checks)
-- Type scoped slot contracts with `defineSlots` in TypeScript components
-- Provide fallback content for optional slots
-- Prefer composables over renderless components for pure logic reuse
-
-## Shorthand syntax for named slots
-
-**BAD:**
-```vue
-<MyComponent>
-  <template v-slot:header> ... </template>
-</MyComponent>
-```
-
-**GOOD:**
-```vue
-<MyComponent>
-  <template #header> ... </template>
-</MyComponent>
-```
-
-## Conditionally Render Optional Slot Wrappers
-
-Use `$slots` checks when wrapper elements add spacing, borders, or layout constraints.
-
-**BAD:**
-```vue
-<!-- Card.vue -->
-<template>
-  <article class="card">
-    <header class="card-header">
-      <slot name="header" />
-    </header>
-
-    <section class="card-body">
-      <slot />
-    </section>
-
-    <footer class="card-footer">
-      <slot name="footer" />
-    </footer>
-  </article>
-</template>
-```
-
-**GOOD:**
-```vue
-<!-- Card.vue -->
-<template>
-  <article class="card">
-    <header v-if="$slots.header" class="card-header">
-      <slot name="header" />
-    </header>
-
-    <section v-if="$slots.default" class="card-body">
-      <slot />
-    </section>
-
-    <footer v-if="$slots.footer" class="card-footer">
-      <slot name="footer" />
-    </footer>
-  </article>
-</template>
-```
-
-## Type Scoped Slot Props with defineSlots
-
-In `<script setup lang="ts">`, use `defineSlots` so slot consumers get autocomplete and static checks.
-
-**BAD:**
-```vue
-<!-- ProductList.vue -->
-<script setup lang="ts">
-interface Product {
-  id: number
-  name: string
-}
-
-defineProps<{ products: Product[] }>()
-</script>
-
-<template>
-  <ul>
-    <li v-for="(product, index) in products" :key="product.id">
-      <slot :product="product" :index="index" />
-    </li>
-  </ul>
-</template>
-```
-
-**GOOD:**
-```vue
-<!-- ProductList.vue -->
-<script setup lang="ts">
-interface Product {
-  id: number
-  name: string
-}
-
-defineProps<{ products: Product[] }>()
-
-defineSlots<{
-  default(props: { product: Product; index: number }): any
-  empty(): any
-}>()
-</script>
-
-<template>
-  <ul v-if="products.length">
-    <li v-for="(product, index) in products" :key="product.id">
-      <slot :product="product" :index="index" />
-    </li>
-  </ul>
-  <slot v-else name="empty" />
-</template>
-```
-
-## Provide Slot Fallback Content
-
-Fallback content makes components resilient when parents omit optional slots.
-
-**BAD:**
-```vue
-<!-- SubmitButton.vue -->
-<template>
-  <button type="submit" class="btn-primary">
-    <slot />
-  </button>
-</template>
-```
-
-**GOOD:**
-```vue
-<!-- SubmitButton.vue -->
-<template>
-  <button type="submit" class="btn-primary">
-    <slot>Submit</slot>
-  </button>
-</template>
-```
-
-## Prefer Composables for Pure Logic Reuse
-
-Renderless components are still useful for slot-driven composition, but composables are usually cleaner for logic-only reuse.
-
-**BAD:**
-```vue
-<!-- MouseTracker.vue -->
-<script setup lang="ts">
-import { ref, onMounted, onUnmounted } from 'vue'
-
-const x = ref(0)
-const y = ref(0)
-
-function onMove(event: MouseEvent) {
-  x.value = event.pageX
-  y.value = event.pageY
-}
-
-onMounted(() => window.addEventListener('mousemove', onMove))
-onUnmounted(() => window.removeEventListener('mousemove', onMove))
-</script>
-
-<template>
-  <slot :x="x" :y="y" />
-</template>
-```
-
-**GOOD:**
-```ts
-// composables/useMouse.ts
-import { ref, onMounted, onUnmounted } from 'vue'
-
-export function useMouse() {
-  const x = ref(0)
-  const y = ref(0)
-
-  function onMove(event: MouseEvent) {
-    x.value = event.pageX
-    y.value = event.pageY
-  }
-
-  onMounted(() => window.addEventListener('mousemove', onMove))
-  onUnmounted(() => window.removeEventListener('mousemove', onMove))
-
-  return { x, y }
-}
-```
-
-```vue
-<!-- MousePosition.vue -->
-<script setup lang="ts">
-import { useMouse } from '@/composables/useMouse'
-
-const { x, y } = useMouse()
-</script>
-
-<template>
-  <p>{{ x }}, {{ y }}</p>
-</template>
-```
diff --git a/.agents/skills/vue-best-practices/references/component-suspense.md b/.agents/skills/vue-best-practices/references/component-suspense.md
deleted file mode 100644
index 4d9ecab..0000000
--- a/.agents/skills/vue-best-practices/references/component-suspense.md
+++ /dev/null
@@ -1,228 +0,0 @@
----
-title: Suspense Component Best Practices
-impact: MEDIUM
-impactDescription: Suspense coordinates async dependencies with fallback UI; misconfiguration leads to missing loading states or confusing UX
-type: best-practice
-tags: [vue3, suspense, async-components, async-setup, loading, fallback, router, transition, keepalive]
----
-
-# Suspense Component Best Practices
-
-**Impact: MEDIUM** - `<Suspense>` coordinates async dependencies (async components or async setup) and renders a fallback while they resolve. Misconfiguration leads to missing loading states, empty renders, or subtle UX bugs.
-
-## Task List
-
-- Wrap default and fallback slot content in a single root node
-- Use `timeout` when you need the fallback to appear on reverts
-- Force root replacement with `:key` when you need Suspense to re-trigger
-- Add `suspensible` to nested Suspense boundaries (Vue 3.3+)
-- Use `@pending`, `@resolve`, and `@fallback` for programmatic loading state
-- Nest `RouterView` -> `Transition` -> `KeepAlive` -> `Suspense` in that order
-- Keep Suspense usage centralized and documented in production
-
-## Single Root in Default and Fallback Slots
-
-Suspense tracks a single immediate child in both slots. Wrap multiple elements in a single element or component.
-
-**BAD:**
-```vue
-<template>
-  <Suspense>
-    <AsyncHeader />
-    <AsyncList />
-
-    <template #fallback>
-      <LoadingSpinner />
-      <LoadingHint />
-    </template>
-  </Suspense>
-</template>
-```
-
-**GOOD:**
-```vue
-<template>
-  <Suspense>
-    <div>
-      <AsyncHeader />
-      <AsyncList />
-    </div>
-
-    <template #fallback>
-      <div>
-        <LoadingSpinner />
-        <LoadingHint />
-      </div>
-    </template>
-  </Suspense>
-</template>
-```
-
-## Fallback Timing on Reverts (`timeout`)
-
-When Suspense is already resolved and new async work starts, the previous content remains visible until the timeout elapses. Use `timeout="0"` for immediate fallback or a short delay to avoid flicker.
-
-**BAD:**
-```vue
-<template>
-  <Suspense>
-    <component :is="currentView" :key="viewKey" />
-
-    <template #fallback>
-      Loading...
-    </template>
-  </Suspense>
-</template>
-```
-
-**GOOD:**
-```vue
-<template>
-  <Suspense :timeout="200">
-    <component :is="currentView" :key="viewKey" />
-
-    <template #fallback>
-      Loading...
-    </template>
-  </Suspense>
-</template>
-```
-
-## Pending State Only Re-triggers on Root Replacement
-
-Once resolved, Suspense only re-enters pending when the root node of the default slot changes. If async work happens deeper in the tree, no fallback appears.
-
-**BAD:**
-```vue
-<template>
-  <Suspense>
-    <TabContainer>
-      <AsyncDashboard v-if="tab === 'dashboard'" />
-      <AsyncSettings v-else />
-    </TabContainer>
-
-    <template #fallback>
-      Loading...
-    </template>
-  </Suspense>
-</template>
-```
-
-**GOOD:**
-```vue
-<template>
-  <Suspense>
-    <component :is="tabs[tab]" :key="tab" />
-
-    <template #fallback>
-      Loading...
-    </template>
-  </Suspense>
-</template>
-```
-
-## Use `suspensible` for Nested Suspense (Vue 3.3+)
-
-Nested Suspense boundaries need `suspensible` on the inner boundary so the parent can coordinate loading state. Without it, inner async content may render empty nodes until resolved.
-
-**BAD:**
-```vue
-<template>
-  <Suspense>
-    <LayoutShell>
-      <Suspense>
-        <AsyncWidget />
-        <template #fallback>Loading widget...</template>
-      </Suspense>
-    </LayoutShell>
-
-    <template #fallback>Loading layout...</template>
-  </Suspense>
-</template>
-```
-
-**GOOD:**
-```vue
-<template>
-  <Suspense>
-    <LayoutShell>
-      <Suspense suspensible>
-        <AsyncWidget />
-        <template #fallback>Loading widget...</template>
-      </Suspense>
-    </LayoutShell>
-
-    <template #fallback>Loading layout...</template>
-  </Suspense>
-</template>
-```
-
-## Track Loading with Suspense Events
-
-Use `@pending`, `@resolve`, and `@fallback` for analytics, global loading indicators, or coordinating UI outside the Suspense boundary.
-
-```vue
-<script setup>
-import { ref } from 'vue'
-
-const isLoading = ref(false)
-
-const onPending = () => {
-  isLoading.value = true
-}
-
-const onResolve = () => {
-  isLoading.value = false
-}
-</script>
-
-<template>
-  <LoadingBar v-if="isLoading" />
-
-  <Suspense @pending="onPending" @resolve="onResolve">
-    <AsyncPage />
-    <template #fallback>
-      <PageSkeleton />
-    </template>
-  </Suspense>
-</template>
-```
-
-## Recommended Nesting with RouterView, Transition, KeepAlive
-
-When combining these components, the nesting order should be `RouterView` -> `Transition` -> `KeepAlive` -> `Suspense` so each wrapper works correctly.
-
-**BAD:**
-```vue
-<template>
-  <RouterView v-slot="{ Component }">
-    <Suspense>
-      <KeepAlive>
-        <Transition mode="out-in">
-          <component :is="Component" />
-        </Transition>
-      </KeepAlive>
-    </Suspense>
-  </RouterView>
-</template>
-```
-
-**GOOD:**
-```vue
-<template>
-  <RouterView v-slot="{ Component }">
-    <Transition mode="out-in">
-      <KeepAlive>
-        <Suspense>
-          <component :is="Component" />
-          <template #fallback>Loading...</template>
-        </Suspense>
-      </KeepAlive>
-    </Transition>
-  </RouterView>
-</template>
-```
-
-## Treat Suspense Cautiously in Production
-
-In production code, keep Suspense boundaries minimal, document where they are used, and have a fallback loading strategy if you ever need to replace or refactor them.
diff --git a/.agents/skills/vue-best-practices/references/component-teleport.md b/.agents/skills/vue-best-practices/references/component-teleport.md
deleted file mode 100644
index db48db2..0000000
--- a/.agents/skills/vue-best-practices/references/component-teleport.md
+++ /dev/null
@@ -1,108 +0,0 @@
----
-title: Teleport Component Best Practices
-impact: MEDIUM
-impactDescription: Teleport renders content outside the component's DOM position, which is essential for overlays but affects styling and layout
-type: best-practice
-tags: [vue3, teleport, modal, overlay, positioning, responsive]
----
-
-# Teleport Component Best Practices
-
-**Impact: MEDIUM** - `<Teleport>` renders part of a component's template in a different place in the DOM while preserving the Vue component hierarchy. Use it for overlays (modals, toasts, tooltips) or any UI that must escape stacking contexts, overflow, or fixed positioning constraints.
-
-## Task List
-
-- Teleport overlays to `body` or a dedicated container outside the app root
-- Keep a shared target for similar UI (`#modals`, `#notifications`) and control layering with order or z-index
-- Use `:disabled` for responsive layouts that should render inline on small screens
-- Remember props, emits, and provide/inject still work through teleport
-- Avoid relying on parent stacking contexts or transforms for teleported UI
-
-## Teleport Overlays Out of Transformed Containers
-
-When an ancestor has `transform`, `filter`, or `perspective`, fixed-position overlays can behave like they are locally positioned. Teleport escapes that context.
-
-**BAD:**
-```vue
-<template>
-  <div class="animated-container">
-    <button @click="open = true">Open</button>
-
-    <!-- Broken: fixed positioning is scoped to the transformed parent -->
-    <div v-if="open" class="modal">Modal</div>
-  </div>
-</template>
-
-<style>
-.animated-container {
-  transform: translateZ(0);
-}
-
-.modal {
-  position: fixed;
-  inset: 0;
-  z-index: 9999;
-}
-</style>
-```
-
-**GOOD:**
-```vue
-<template>
-  <div class="animated-container">
-    <button @click="open = true">Open</button>
-
-    <Teleport to="body">
-      <div v-if="open" class="modal">Modal</div>
-    </Teleport>
-  </div>
-</template>
-```
-
-## Responsive Layouts with `disabled`
-
-Use `:disabled` to render inline on mobile and teleport on larger screens:
-
-```vue
-<script setup>
-import { useMediaQuery } from '@vueuse/core'
-
-const isMobile = useMediaQuery('(max-width: 768px)')
-</script>
-
-<template>
-  <Teleport to="body" :disabled="isMobile">
-    <nav class="sidebar">Navigation</nav>
-  </Teleport>
-</template>
-```
-
-## Logical Hierarchy Is Preserved
-
-Teleport changes DOM position, not the Vue component tree. Props, emits, slots, and provide/inject still work:
-
-```vue
-<template>
-  <Teleport to="body">
-    <ChildPanel :message="message" @close="open = false" />
-  </Teleport>
-</template>
-```
-
-## Multiple Teleports to the Same Target
-
-Teleports to the same target append in declaration order:
-
-```vue
-<template>
-  <Teleport to="#notifications">
-    <div>First</div>
-  </Teleport>
-
-  <Teleport to="#notifications">
-    <div>Second</div>
-  </Teleport>
-</template>
-```
-
-Use a shared container to keep stacking predictable, and apply z-index only when you need explicit layering.
diff --git a/.agents/skills/vue-best-practices/references/component-transition-group.md b/.agents/skills/vue-best-practices/references/component-transition-group.md
deleted file mode 100644
index d0339ff..0000000
--- a/.agents/skills/vue-best-practices/references/component-transition-group.md
+++ /dev/null
@@ -1,128 +0,0 @@
----
-title: TransitionGroup Component Best Practices
-impact: MEDIUM
-impactDescription: TransitionGroup animates list items; missing keys or misuse leads to broken list transitions
-type: best-practice
-tags: [vue3, transition-group, animation, lists, keys]
----
-
-# TransitionGroup Component Best Practices
-
-**Impact: MEDIUM** - `<TransitionGroup>` animates lists of items entering, leaving, and moving. Use it for `v-for` lists or dynamic collections where individual items change over time.
-
-## Task List
-
-- Use `<TransitionGroup>` only for lists and repeated items
-- Provide unique, stable keys for every direct child
-- Use `tag` when you need semantic or layout wrappers
-- Avoid the `mode` prop (not supported)
-- Use JavaScript hooks for staggered effects
-
-## Use TransitionGroup for Lists
-
-`<TransitionGroup>` is designed for list items. Use `tag` to control the wrapper element when needed.
-
-**BAD:**
-```vue
-<template>
-  <TransitionGroup name="fade">
-    <ComponentA />
-    <ComponentB />
-  </TransitionGroup>
-</template>
-```
-
-**GOOD:**
-```vue
-<template>
-  <TransitionGroup name="list" tag="ul">
-    <li v-for="item in items" :key="item.id">
-      {{ item.name }}
-    </li>
-  </TransitionGroup>
-</template>
-```
-
-## Always Provide Stable Keys
-
-Keys are required. Without stable keys, Vue cannot track item positions and animations break.
-
-**BAD:**
-```vue
-<template>
-  <TransitionGroup name="list" tag="ul">
-    <li v-for="(item, index) in items" :key="index">
-      {{ item.name }}
-    </li>
-  </TransitionGroup>
-</template>
-```
-
-**GOOD:**
-```vue
-<template>
-  <TransitionGroup name="list" tag="ul">
-    <li v-for="item in items" :key="item.id">
-      {{ item.name }}
-    </li>
-  </TransitionGroup>
-</template>
-```
-
-## Do Not Use `mode` on TransitionGroup
-
-`mode` is only for `<Transition>` because it swaps a single element. Use `<Transition>` if you need in/out sequencing.
-
-**BAD:**
-```vue
-<template>
-  <TransitionGroup name="list" tag="div" mode="out-in">
-    <div v-for="item in items" :key="item.id">{{ item.name }}</div>
-  </TransitionGroup>
-</template>
-```
-
-**GOOD:**
-```vue
-<template>
-  <Transition name="fade" mode="out-in">
-    <component :is="currentView" :key="currentView" />
-  </Transition>
-</template>
-```
-
-## Stagger List Animations with Data Attributes
-
-For cascading list animations, pass the index to JavaScript hooks and compute delay per item.
-
-```vue
-<template>
-  <TransitionGroup
-    tag="ul"
-    :css="false"
-    @before-enter="onBeforeEnter"
-    @enter="onEnter"
-  >
-    <li v-for="(item, index) in items" :key="item.id" :data-index="index">
-      {{ item.name }}
-    </li>
-  </TransitionGroup>
-</template>
-
-<script setup>
-function onBeforeEnter(el) {
-  el.style.opacity = 0
-  el.style.transform = 'translateY(12px)'
-}
-
-function onEnter(el, done) {
-  const delay = Number(el.dataset.index) * 80
-  setTimeout(() => {
-    el.style.transition = 'all 0.25s ease'
-    el.style.opacity = 1
-    el.style.transform = 'translateY(0)'
-    setTimeout(done, 250)
-  }, delay)
-}
-</script>
-```
diff --git a/.agents/skills/vue-best-practices/references/component-transition.md b/.agents/skills/vue-best-practices/references/component-transition.md
deleted file mode 100644
index e6abed7..0000000
--- a/.agents/skills/vue-best-practices/references/component-transition.md
+++ /dev/null
@@ -1,125 +0,0 @@
----
-title: Transition Component Best Practices
-impact: MEDIUM
-impactDescription: Transition animates a single element or component; incorrect structure or keys prevent animations
-type: best-practice
-tags: [vue3, transition, animation, performance, keys]
----
-
-# Transition Component Best Practices
-
-**Impact: MEDIUM** - `<Transition>` animates entering/leaving of a single element or component. It is ideal for toggling UI states, swapping views, or animating one component at a time.
-
-## Task List
-
-- Wrap a single element or component inside `<Transition>`
-- Provide a `key` when switching between same element types
-- Use `mode="out-in"` when you need sequential swaps
-- Prefer `transform` and `opacity` for smooth animations
-
-## Use Transition for a Single Root Element
-
-`<Transition>` only supports one direct child. Wrap multiple nodes in a single element or component.
-
-**BAD:**
-```vue
-<template>
-  <Transition name="fade">
-    <h3>Title</h3>
-    <p>Description</p>
-  </Transition>
-</template>
-```
-
-**GOOD:**
-```vue
-<template>
-  <Transition name="fade">
-    <div>
-      <h3>Title</h3>
-      <p>Description</p>
-    </div>
-  </Transition>
-</template>
-```
-
-## Force Transitions Between Same Element Types
-
-Vue reuses the same DOM element when the tag type does not change. Add `key` so Vue treats it as a new element and triggers enter/leave.
-
-**BAD:**
-```vue
-<template>
-  <Transition name="fade">
-    <p v-if="isActive">Active</p>
-    <p v-else>Inactive</p>
-  </Transition>
-</template>
-```
-
-**GOOD:**
-```vue
-<template>
-  <Transition name="fade" mode="out-in">
-    <p v-if="isActive" key="active">Active</p>
-    <p v-else key="inactive">Inactive</p>
-  </Transition>
-</template>
-```
-
-## Use `mode` to Avoid Overlap During Swaps
-
-When swapping components or views, use `mode="out-in"` to prevent both from being visible at the same time.
-
-**BAD:**
-```vue
-<template>
-  <Transition name="fade">
-    <component :is="currentView" />
-  </Transition>
-</template>
-```
-
-**GOOD:**
-```vue
-<template>
-  <Transition name="fade" mode="out-in">
-    <component :is="currentView" :key="currentView" />
-  </Transition>
-</template>
-```
-
-## Animate `transform` and `opacity` for Performance
-
-Avoid layout-triggering properties such as `height`, `margin`, or `top`. Use `transform` and `opacity` for smooth, GPU-friendly transitions.
-
-**BAD:**
-```css
-.slide-enter-active,
-.slide-leave-active {
-  transition: height 0.3s ease;
-}
-
-.slide-enter-from,
-.slide-leave-to {
-  height: 0;
-}
-```
-
-**GOOD:**
-```css
-.slide-enter-active,
-.slide-leave-active {
-  transition: transform 0.3s ease, opacity 0.3s ease;
-}
-
-.slide-enter-from {
-  transform: translateX(-12px);
-  opacity: 0;
-}
-
-.slide-leave-to {
-  transform: translateX(12px);
-  opacity: 0;
-}
-```
diff --git a/.agents/skills/vue-best-practices/references/composables.md b/.agents/skills/vue-best-practices/references/composables.md
deleted file mode 100644
index cb18a6f..0000000
--- a/.agents/skills/vue-best-practices/references/composables.md
+++ /dev/null
@@ -1,290 +0,0 @@
----
-title: Composable Organization Patterns
-impact: MEDIUM
-impactDescription: Well-structured composables improve maintainability, reusability, and update performance
-type: best-practice
-tags: [vue3, composables, composition-api, code-organization, api-design, readonly, utilities]
----
-
-# Composable Organization Patterns
-
-**Impact: MEDIUM** - Treat composables as reusable, stateful building blocks and keep their code organized by feature concern. This keeps large components maintainable and prevents hard-to-debug mutation and API design issues.
-
-## Task List
-
-- Compose complex behavior from small, focused composables
-- Use options objects for composables with multiple optional parameters
-- Return readonly state when updates must flow through explicit actions
-- Keep pure utility functions as plain utilities, not composables
-- Organize composable and component code by feature concern, and extract composables when components grow
-
-## Compose Composables from Smaller Primitives
-
-**BAD:**
-```vue
-<script setup>
-import { ref, computed, onMounted, onUnmounted } from 'vue'
-
-const x = ref(0)
-const y = ref(0)
-const inside = ref(false)
-const el = ref(null)
-
-function onMove(e) {
-  x.value = e.pageX
-  y.value = e.pageY
-  if (!el.value) return
-  const r = el.value.getBoundingClientRect()
-  inside.value = x.value >= r.left && x.value <= r.right &&
-    y.value >= r.top && y.value <= r.bottom
-}
-
-onMounted(() => window.addEventListener('mousemove', onMove))
-onUnmounted(() => window.removeEventListener('mousemove', onMove))
-</script>
-```
-
-**GOOD:**
-```javascript
-// composables/useEventListener.js
-import { onMounted, onUnmounted, toValue } from 'vue'
-
-export function useEventListener(target, event, callback) {
-  onMounted(() => toValue(target).addEventListener(event, callback))
-  onUnmounted(() => toValue(target).removeEventListener(event, callback))
-}
-```
-
-```javascript
-// composables/useMouse.js
-import { ref } from 'vue'
-import { useEventListener } from './useEventListener'
-
-export function useMouse() {
-  const x = ref(0)
-  const y = ref(0)
-
-  useEventListener(window, 'mousemove', (e) => {
-    x.value = e.pageX
-    y.value = e.pageY
-  })
-
-  return { x, y }
-}
-```
-
-```javascript
-// composables/useMouseInElement.js
-import { computed } from 'vue'
-import { useMouse } from './useMouse'
-
-export function useMouseInElement(elementRef) {
-  const { x, y } = useMouse()
-
-  const isOutside = computed(() => {
-    if (!elementRef.value) return true
-    const rect = elementRef.value.getBoundingClientRect()
-    return x.value < rect.left || x.value > rect.right ||
-      y.value < rect.top || y.value > rect.bottom
-  })
-
-  return { x, y, isOutside }
-}
-```
-
-## Use Options Object Pattern for Composable Parameters
-
-**BAD:**
-```javascript
-export function useFetch(url, method, headers, timeout, retries, immediate) {
-  // hard to read and easy to misorder
-}
-
-useFetch('/api/users', 'GET', null, 5000, 3, true)
-```
-
-**GOOD:**
-```javascript
-export function useFetch(url, options = {}) {
-  const {
-    method = 'GET',
-    headers = {},
-    timeout = 30000,
-    retries = 0,
-    immediate = true
-  } = options
-
-  // implementation
-  return { method, headers, timeout, retries, immediate }
-}
-
-useFetch('/api/users', {
-  method: 'POST',
-  timeout: 5000,
-  retries: 3
-})
-```
-
-```typescript
-interface UseCounterOptions {
-  initial?: number
-  min?: number
-  max?: number
-  step?: number
-}
-
-export function useCounter(options: UseCounterOptions = {}) {
-  const { initial = 0, min = -Infinity, max = Infinity, step = 1 } = options
-  // implementation
-}
-```
-
-## Return Readonly State with Explicit Actions
-
-**BAD:**
-```javascript
-export function useCart() {
-  const items = ref([])
-  const total = computed(() => items.value.reduce((sum, item) => sum + item.price, 0))
-  return { items, total } // any consumer can mutate directly
-}
-
-const { items } = useCart()
-items.value.push({ id: 1, price: 10 })
-```
-
-**GOOD:**
-```javascript
-import { ref, computed, readonly } from 'vue'
-
-export function useCart() {
-  const _items = ref([])
-
-  const total = computed(() =>
-    _items.value.reduce((sum, item) => sum + item.price * item.quantity, 0)
-  )
-
-  function addItem(product, quantity = 1) {
-    const existing = _items.value.find(item => item.id === product.id)
-    if (existing) {
-      existing.quantity += quantity
-      return
-    }
-    _items.value.push({ ...product, quantity })
-  }
-
-  function removeItem(productId) {
-    _items.value = _items.value.filter(item => item.id !== productId)
-  }
-
-  return {
-    items: readonly(_items),
-    total,
-    addItem,
-    removeItem
-  }
-}
-```
-
-## Keep Utilities as Utilities
-
-**BAD:**
-```javascript
-export function useFormatters() {
-  const formatDate = (date) => new Intl.DateTimeFormat('en-US').format(date)
-  const formatCurrency = (amount) =>
-    new Intl.NumberFormat('en-US', { style: 'currency', currency: 'USD' }).format(amount)
-  return { formatDate, formatCurrency }
-}
-
-const { formatDate } = useFormatters()
-```
-
-**GOOD:**
-```javascript
-// utils/formatters.js
-export function formatDate(date) {
-  return new Intl.DateTimeFormat('en-US').format(date)
-}
-
-export function formatCurrency(amount) {
-  return new Intl.NumberFormat('en-US', {
-    style: 'currency',
-    currency: 'USD'
-  }).format(amount)
-}
-```
-
-```javascript
-// composables/useInvoiceSummary.js
-import { computed } from 'vue'
-import { formatCurrency } from '@/utils/formatters'
-
-export function useInvoiceSummary(invoiceRef) {
-  const totalLabel = computed(() => formatCurrency(invoiceRef.value.total))
-  return { totalLabel }
-}
-```
-
-## Organize Composable and Component Code by Feature Concern
-
-**BAD:**
-```vue
-<script setup>
-import { ref, computed, watch, onMounted } from 'vue'
-
-const searchQuery = ref('')
-const items = ref([])
-const selected = ref(null)
-const showModal = ref(false)
-const sortBy = ref('name')
-const filter = ref('all')
-const loading = ref(false)
-
-const filtered = computed(() => items.value.filter(i => i.category === filter.value))
-function openModal() { showModal.value = true }
-const sorted = computed(() => [...filtered.value].sort(/* ... */))
-watch(searchQuery, () => { /* ... */ })
-onMounted(() => { /* ... */ })
-</script>
-```
-
-**GOOD:**
-```vue
-<script setup>
-import { useItems } from '@/composables/useItems'
-import { useSearch } from '@/composables/useSearch'
-import { useSelectionModal } from '@/composables/useSelectionModal'
-
-// Data
-const { items, loading, fetchItems } = useItems()
-
-// Search/filter/sort
-const { query, visibleItems } = useSearch(items)
-
-// Selection + modal
-const { selectedItem, isModalOpen, selectItem, closeModal } = useSelectionModal()
-</script>
-```
-
-```javascript
-// composables/useItems.js
-import { ref, onMounted } from 'vue'
-
-export function useItems() {
-  const items = ref([])
-  const loading = ref(false)
-
-  async function fetchItems() {
-    loading.value = true
-    try {
-      items.value = await api.getItems()
-    } finally {
-      loading.value = false
-    }
-  }
-
-  onMounted(fetchItems)
-  return { items, loading, fetchItems }
-}
-```
diff --git a/.agents/skills/vue-best-practices/references/directives.md b/.agents/skills/vue-best-practices/references/directives.md
deleted file mode 100644
index 8412fbc..0000000
--- a/.agents/skills/vue-best-practices/references/directives.md
+++ /dev/null
@@ -1,162 +0,0 @@
----
-title: Directive Best Practices
-impact: MEDIUM
-impactDescription: Custom directives are powerful but easy to misuse; following patterns prevents leaks, invalid usage, and unclear abstractions
-type: best-practice
-tags: [vue3, directives, custom-directives, composition, typescript]
----
-
-# Directive Best Practices
-
-**Impact: MEDIUM** - Directives are for low-level DOM access. Use them sparingly, keep them side-effect safe, and prefer components or composables when you need stateful or reusable UI behavior.
-
-## Task List
-
-- Use directives only when you need direct DOM access
-- Do not mutate directive arguments or binding objects
-- Clean up timers, listeners, and observers in `unmounted`
-- Register directives in `<script setup>` with the `v-` prefix
-- In TypeScript projects, type directive values and augment template directive types
-- Prefer components or composables for complex behavior
-
-## Treat Directive Arguments as Read-Only
-
-Directive bindings are not reactive storage. Don’t write to them.
-
-```ts
-const vFocus = {
-  mounted(el, binding) {
-    // binding.value is read-only
-    el.focus()
-  }
-}
-```
-
-## Avoid Directives on Components
-
-Directives apply to DOM elements. When used on components, they attach to the root element and can break if the root changes.
-
-**BAD:**
-```vue
-<MyInput v-focus />
-```
-
-**GOOD:**
-```vue
-<!-- MyInput.vue -->
-<script setup>
-const vFocus = (el) => el.focus()
-</script>
-
-<template>
-  <input v-focus />
-</template>
-```
-
-## Clean Up Side Effects in `unmounted`
-
-Any timers, listeners, or observers must be removed to avoid leaks.
-
-```ts
-const vResize = {
-  mounted(el) {
-    const observer = new ResizeObserver(() => {})
-    observer.observe(el)
-    el._observer = observer
-  },
-  unmounted(el) {
-    el._observer?.disconnect()
-  }
-}
-```
-
-## Prefer Function Shorthand for Single-Hook Directives
-
-If you only need `mounted`/`updated`, use the function form.
-
-```ts
-const vAutofocus = (el) => el.focus()
-```
-
-## Use the `v-` Prefix and Script Setup Registration
-
-```vue
-<script setup>
-const vFocus = (el) => el.focus()
-</script>
-
-<template>
-  <input v-focus />
-</template>
-```
-
-## Type Custom Directives in TypeScript Projects
-
-Use `Directive<Element, ValueType>` so `binding.value` is typed, and augment Vue's template types so directives are recognized in SFC templates.
-
-**BAD:**
-```ts
-// Untyped directive value and no template type augmentation
-export const vHighlight = {
-  mounted(el, binding) {
-    el.style.backgroundColor = binding.value
-  }
-}
-```
-
-**GOOD:**
-```ts
-import type { Directive } from 'vue'
-
-type HighlightValue = string
-
-export const vHighlight = {
-  mounted(el, binding) {
-    el.style.backgroundColor = binding.value
-  }
-} satisfies Directive<HTMLElement, HighlightValue>
-
-declare module 'vue' {
-  interface ComponentCustomProperties {
-    vHighlight: typeof vHighlight
-  }
-}
-```
-
-## Handle SSR with `getSSRProps`
-
-Directive hooks such as `mounted` and `updated` do not run during SSR. If a directive sets attributes/classes that affect rendered HTML, provide an SSR equivalent via `getSSRProps` to avoid hydration mismatches.
-
-**BAD:**
-```ts
-const vTooltip = {
-  mounted(el, binding) {
-    el.setAttribute('data-tooltip', binding.value)
-    el.classList.add('has-tooltip')
-  }
-}
-```
-
-**GOOD:**
-```ts
-const vTooltip = {
-  mounted(el, binding) {
-    el.setAttribute('data-tooltip', binding.value)
-    el.classList.add('has-tooltip')
-  },
-  getSSRProps(binding) {
-    return {
-      'data-tooltip': binding.value,
-      class: 'has-tooltip'
-    }
-  }
-}
-```
-
-## Prefer Declarative Templates When Possible
-
-If a standard attribute or binding works, use it instead of a directive.
-
-## Decide Between Directives and Components
-
-Use a directive for DOM-level behavior. Use a component when behavior affects structure, state, or rendering.
diff --git a/.agents/skills/vue-best-practices/references/perf-avoid-component-abstraction-in-lists.md b/.agents/skills/vue-best-practices/references/perf-avoid-component-abstraction-in-lists.md
deleted file mode 100644
index 44f98ff..0000000
--- a/.agents/skills/vue-best-practices/references/perf-avoid-component-abstraction-in-lists.md
+++ /dev/null
@@ -1,159 +0,0 @@
----
-title: Avoid Excessive Component Abstraction in Large Lists
-impact: MEDIUM
-impactDescription: Each component instance has memory and render overhead - abstractions multiply this in lists
-type: efficiency
-tags: [vue3, performance, components, abstraction, lists, optimization]
----
-
-# Avoid Excessive Component Abstraction in Large Lists
-
-**Impact: MEDIUM** - Component instances are more expensive than plain DOM nodes. While abstractions improve code organization, unnecessary nesting creates overhead. In large lists, this overhead multiplies - 100 items with 3 levels of abstraction means 300+ component instances instead of 100.
-
-Don't avoid abstraction entirely, but be mindful of component depth in frequently-rendered elements like list items.
-
-## Task List
-
-- Review list item components for unnecessary wrapper components
-- Consider flattening component hierarchies in hot paths
-- Use native elements when a component adds no value
-- Profile component counts using Vue DevTools
-- Focus optimization efforts on the most-rendered components
-
-**BAD:**
-```vue
-<!-- BAD: Deep abstraction in list items -->
-<template>
-  <div class="user-list">
-    <!-- For 100 users: Creates 400 component instances -->
-    <UserCard v-for="user in users" :key="user.id" :user="user" />
-  </div>
-</template>
-
-<!-- UserCard.vue -->
-<template>
-  <Card>  <!-- Wrapper component #1 -->
-    <CardHeader>  <!-- Wrapper component #2 -->
-      <UserAvatar :src="user.avatar" />  <!-- Wrapper component #3 -->
-    </CardHeader>
-    <CardBody>  <!-- Wrapper component #4 -->
-      <Text>{{ user.name }}</Text>
-    </CardBody>
-  </Card>
-</template>
-
-<!-- Each UserCard creates: Card + CardHeader + CardBody + UserAvatar + Text
-     100 users = 500+ component instances -->
-```
-
-**GOOD:**
-```vue
-<!-- GOOD: Flattened structure in list items -->
-<template>
-  <div class="user-list">
-    <!-- For 100 users: Creates 100 component instances -->
-    <UserCard v-for="user in users" :key="user.id" :user="user" />
-  </div>
-</template>
-
-<!-- UserCard.vue - Flattened, uses native elements -->
-<template>
-  <div class="card">
-    <div class="card-header">
-      <img :src="user.avatar" :alt="user.name" class="avatar" />
-    </div>
-    <div class="card-body">
-      <span class="user-name">{{ user.name }}</span>
-    </div>
-  </div>
-</template>
-
-<script setup>
-defineProps({
-  user: Object
-})
-</script>
-
-<style scoped>
-/* Styles that would have been in Card, CardHeader, etc. */
-.card { /* ... */ }
-.card-header { /* ... */ }
-.card-body { /* ... */ }
-.avatar { /* ... */ }
-</style>
-```
-
-## When Abstraction Is Still Worth It
-
-```vue
-<!-- Component abstraction is valuable when: -->
-
-<!-- 1. Complex behavior is encapsulated -->
-<UserStatusIndicator :user="user" />  <!-- Has logic, tooltips, etc. -->
-
-<!-- 2. Reused outside of the hot path -->
-<Card>  <!-- OK to use in one-off places, not in 100-item lists -->
-
-<!-- 3. The list itself is small -->
-<template v-if="items.length < 20">
-  <FancyItem v-for="item in items" :key="item.id" />
-</template>
-
-<!-- 4. Virtualization is used (only ~20 items rendered at once) -->
-<RecycleScroller :items="items">
-  <template #default="{ item }">
-    <ComplexItem :item="item" />  <!-- OK - only 20 instances exist -->
-  </template>
-</RecycleScroller>
-```
-
-## Measuring Component Overhead
-
-```javascript
-// In development, profile component counts
-import { onMounted, getCurrentInstance } from 'vue'
-
-onMounted(() => {
-  const instance = getCurrentInstance()
-  let count = 0
-
-  function countComponents(vnode) {
-    if (vnode.component) count++
-    if (vnode.children) {
-      vnode.children.forEach(child => {
-        if (child.component || child.children) countComponents(child)
-      })
-    }
-  }
-
-  // Use Vue DevTools instead for accurate counts
-  console.log('Check Vue DevTools Components tab for instance counts')
-})
-```
-
-## Alternatives to Wrapper Components
-
-```vue
-<!-- Instead of a <Button> component for styling: -->
-<button class="btn btn-primary">Click</button>
-
-<!-- Instead of a <Text> component: -->
-<span class="text-body">{{ content }}</span>
-
-<!-- Instead of layout wrapper components in lists: -->
-<div class="flex items-center gap-2">
-  <!-- content -->
-</div>
-
-<!-- Use CSS classes or Tailwind instead of component abstractions for styling -->
-```
-
-## Impact Calculation
-
-| List Size | Components per Item | Total Instances | Memory Impact |
-|-----------|---------------------|-----------------|---------------|
-| 100 items | 1 (flat) | 100 | Baseline |
-| 100 items | 3 (nested) | 300 | ~3x memory |
-| 100 items | 5 (deeply nested) | 500 | ~5x memory |
-| 1000 items | 1 (flat) | 1000 | High |
-| 1000 items | 5 (deeply nested) | 5000 | Very High |
diff --git a/.agents/skills/vue-best-practices/references/perf-v-once-v-memo-directives.md b/.agents/skills/vue-best-practices/references/perf-v-once-v-memo-directives.md
deleted file mode 100644
index ce5f688..0000000
--- a/.agents/skills/vue-best-practices/references/perf-v-once-v-memo-directives.md
+++ /dev/null
@@ -1,182 +0,0 @@
----
-title: Use v-once and v-memo to Skip Unnecessary Updates
-impact: MEDIUM
-impactDescription: v-once skips all future updates for static content; v-memo conditionally memoizes subtrees
-type: efficiency
-tags: [vue3, performance, v-once, v-memo, optimization, directives]
----
-
-# Use v-once and v-memo to Skip Unnecessary Updates
-
-**Impact: MEDIUM** - Vue re-evaluates templates on every reactive change. For content that never changes or changes infrequently, `v-once` and `v-memo` tell Vue to skip updates, reducing render work.
-
-Use `v-once` for truly static content and `v-memo` for conditionally-static content in lists.
-
-## Task List
-
-- Apply `v-once` to elements that use runtime data but never need updating
-- Apply `v-memo` to list items that should only update on specific condition changes
-- Verify memoized content doesn't need to respond to other state changes
-- Profile with Vue DevTools to confirm update skipping
-
-## v-once: Render Once, Never Update
-
-**BAD:**
-```vue
-<template>
-  <!-- BAD: Re-evaluated on every parent re-render -->
-  <div class="terms-content">
-    <h1>Terms of Service</h1>
-    <p>Version: {{ termsVersion }}</p>
-    <div v-html="termsContent"></div>
-  </div>
-
-  <!-- This content NEVER changes, but Vue checks it every render -->
-  <footer>
-    <p>Copyright {{ copyrightYear }} {{ companyName }}</p>
-  </footer>
-</template>
-```
-
-**GOOD:**
-```vue
-<template>
-  <!-- GOOD: Rendered once, skipped on all future updates -->
-  <div class="terms-content" v-once>
-    <h1>Terms of Service</h1>
-    <p>Version: {{ termsVersion }}</p>
-    <div v-html="termsContent"></div>
-  </div>
-
-  <!-- v-once tells Vue this never needs to update -->
-  <footer v-once>
-    <p>Copyright {{ copyrightYear }} {{ companyName }}</p>
-  </footer>
-</template>
-
-<script setup>
-// These values are set once at component creation
-const termsVersion = '2.1'
-const termsContent = fetchedTermsHTML
-const copyrightYear = 2024
-const companyName = 'Acme Corp'
-</script>
-```
-
-## v-memo: Conditional Memoization for Lists
-
-**BAD:**
-```vue
-<template>
-  <!-- BAD: All items re-render when selectedId changes -->
-  <div v-for="item in list" :key="item.id">
-    <div :class="{ selected: item.id === selectedId }">
-      <ExpensiveComponent :data="item" />
-    </div>
-  </div>
-</template>
-```
-
-**GOOD:**
-```vue
-<template>
-  <!-- GOOD: Items only re-render when their selection state changes -->
-  <div
-    v-for="item in list"
-    :key="item.id"
-    v-memo="[item.id === selectedId]"
-  >
-    <div :class="{ selected: item.id === selectedId }">
-      <ExpensiveComponent :data="item" />
-    </div>
-  </div>
-</template>
-
-<script setup>
-import { ref } from 'vue'
-
-const list = ref([/* many items */])
-const selectedId = ref(null)
-
-// When selectedId changes:
-// - Only the previously-selected item re-renders (selected: true -> false)
-// - Only the newly-selected item re-renders (selected: false -> true)
-// - All other items are SKIPPED (v-memo values unchanged)
-</script>
-```
-
-## v-memo with Multiple Dependencies
-
-```vue
-<template>
-  <!-- Re-render only when item's selection OR editing state changes -->
-  <div
-    v-for="item in items"
-    :key="item.id"
-    v-memo="[item.id === selectedId, item.id === editingId]"
-  >
-    <ItemCard
-      :item="item"
-      :selected="item.id === selectedId"
-      :editing="item.id === editingId"
-    />
-  </div>
-</template>
-
-<script setup>
-const selectedId = ref(null)
-const editingId = ref(null)
-const items = ref([/* ... */])
-</script>
-```
-
-## v-memo with Empty Array = v-once
-
-```vue
-<template>
-  <!-- v-memo="[]" is equivalent to v-once -->
-  <div v-for="item in staticList" :key="item.id" v-memo="[]">
-    {{ item.name }}
-  </div>
-</template>
-```
-
-## When NOT to Use These Directives
-
-```vue
-<template>
-  <!-- DON'T: Content that DOES need to update -->
-  <div v-once>
-    <span>Count: {{ count }}</span>  <!-- count won't update! -->
-  </div>
-
-  <!-- DON'T: When child components have their own reactive state -->
-  <div v-memo="[selected]">
-    <InputField v-model="item.name" />  <!-- v-model won't work properly -->
-  </div>
-
-  <!-- DON'T: When the memoization benefit is minimal -->
-  <span v-once>{{ simpleText }}</span>  <!-- Overhead not worth it -->
-</template>
-```
-
-## Performance Comparison
-
-| Scenario | Without Directive | With v-once/v-memo |
-|----------|-------------------|-------------------|
-| Static header, parent re-renders 100x | Re-evaluated 100x | Evaluated 1x |
-| 1000 items, selection changes | 1000 items re-render | 2 items re-render |
-| Complex child component | Full re-render | Skipped if memoized |
-
-## Debugging Memoized Components
-
-```vue
-<script setup>
-import { onUpdated } from 'vue'
-
-// This won't fire if v-memo prevents update
-onUpdated(() => {
-  console.log('Component updated')
-})
-</script>
-```
diff --git a/.agents/skills/vue-best-practices/references/perf-virtualize-large-lists.md b/.agents/skills/vue-best-practices/references/perf-virtualize-large-lists.md
deleted file mode 100644
index 78a8a1c..0000000
--- a/.agents/skills/vue-best-practices/references/perf-virtualize-large-lists.md
+++ /dev/null
@@ -1,187 +0,0 @@
----
-title: Virtualize Large Lists to Avoid DOM Overload
-impact: HIGH
-impactDescription: Rendering thousands of list items creates excessive DOM nodes, causing slow renders and high memory usage
-type: efficiency
-tags: [vue3, performance, virtual-list, large-data, dom, optimization]
----
-
-# Virtualize Large Lists to Avoid DOM Overload
-
-**Impact: HIGH** - Rendering all items in a large list (hundreds or thousands) creates massive amounts of DOM nodes. Each node consumes memory, slows down initial render, and makes updates expensive. List virtualization only renders visible items, dramatically improving performance.
-
-Use a virtualization library when dealing with lists that could exceed 50-100 items, especially if items have complex content.
-
-## Task List
-
-- Identify lists that render more than 50-100 items
-- Install a virtualization library (vue-virtual-scroller, @tanstack/vue-virtual)
-- Replace standard `v-for` with virtualized component
-- Ensure list items have consistent or estimable heights
-- Test with realistic data volumes during development
-
-## Recommended Libraries
-
-| Library | Best For | Notes |
-|---------|----------|-------|
-| `vue-virtual-scroller` | General use, easy setup | Most popular, good defaults |
-| `@tanstack/vue-virtual` | Complex layouts, headless | Framework-agnostic, flexible |
-| `vue-virtual-scroll-grid` | Grid layouts | 2D virtualization |
-| `vueuc/VVirtualList` | Naive UI projects | Part of Naive UI ecosystem |
-
-**BAD:**
-```vue
-<template>
-  <!-- BAD: Renders ALL 10,000 items immediately -->
-  <div class="user-list">
-    <UserCard
-      v-for="user in users"
-      :key="user.id"
-      :user="user"
-    />
-  </div>
-</template>
-
-<script setup>
-import { ref, onMounted } from 'vue'
-import UserCard from './UserCard.vue'
-
-const users = ref([])
-
-onMounted(async () => {
-  // 10,000 DOM nodes created, browser struggles
-  users.value = await fetchAllUsers()
-})
-</script>
-```
-
-**GOOD:**
-```vue
-<template>
-  <!-- GOOD: Only renders ~20 visible items at a time -->
-  <RecycleScroller
-    class="user-list"
-    :items="users"
-    :item-size="80"
-    key-field="id"
-    v-slot="{ item }"
-  >
-    <UserCard :user="item" />
-  </RecycleScroller>
-</template>
-
-<script setup>
-import { ref, onMounted } from 'vue'
-import { RecycleScroller } from 'vue-virtual-scroller'
-import 'vue-virtual-scroller/dist/vue-virtual-scroller.css'
-import UserCard from './UserCard.vue'
-
-const users = ref([])
-
-onMounted(async () => {
-  // 10,000 items in memory, but only ~20 DOM nodes
-  users.value = await fetchAllUsers()
-})
-</script>
-
-<style scoped>
-.user-list {
-  height: 600px; /* Container must have fixed height */
-}
-</style>
-```
-
-## Using @tanstack/vue-virtual
-
-```vue
-<template>
-  <div ref="parentRef" class="list-container">
-    <div
-      :style="{
-        height: `${rowVirtualizer.getTotalSize()}px`,
-        position: 'relative'
-      }"
-    >
-      <div
-        v-for="virtualRow in rowVirtualizer.getVirtualItems()"
-        :key="virtualRow.key"
-        :style="{
-          position: 'absolute',
-          top: 0,
-          left: 0,
-          width: '100%',
-          height: `${virtualRow.size}px`,
-          transform: `translateY(${virtualRow.start}px)`
-        }"
-      >
-        <UserCard :user="users[virtualRow.index]" />
-      </div>
-    </div>
-  </div>
-</template>
-
-<script setup>
-import { ref } from 'vue'
-import { useVirtualizer } from '@tanstack/vue-virtual'
-
-const users = ref([/* 10,000 users */])
-const parentRef = ref(null)
-
-const rowVirtualizer = useVirtualizer({
-  count: users.value.length,
-  getScrollElement: () => parentRef.value,
-  estimateSize: () => 80,  // Estimated row height
-  overscan: 5  // Render 5 extra items above/below viewport
-})
-</script>
-
-<style scoped>
-.list-container {
-  height: 600px;
-  overflow: auto;
-}
-</style>
-```
-
-## Dynamic Heights with vue-virtual-scroller
-
-```vue
-<template>
-  <!-- For variable height items, use DynamicScroller -->
-  <DynamicScroller
-    :items="messages"
-    :min-item-size="54"
-    key-field="id"
-  >
-    <template #default="{ item, index, active }">
-      <DynamicScrollerItem
-        :item="item"
-        :active="active"
-        :data-index="index"
-      >
-        <ChatMessage :message="item" />
-      </DynamicScrollerItem>
-    </template>
-  </DynamicScroller>
-</template>
-
-<script setup>
-import { DynamicScroller, DynamicScrollerItem } from 'vue-virtual-scroller'
-</script>
-```
-
-## Performance Comparison
-
-| Approach | 100 Items | 1,000 Items | 10,000 Items |
-|----------|-----------|-------------|--------------|
-| Regular v-for | ~100 DOM nodes | ~1,000 DOM nodes | ~10,000 DOM nodes |
-| Virtualized | ~20 DOM nodes | ~20 DOM nodes | ~20 DOM nodes |
-| Initial render | Fast | Slow | Very slow / crashes |
-| Virtualized render | Fast | Fast | Fast |
-
-## When NOT to Virtualize
-
-- Lists under 50 items with simple content
-- Lists where all items must be accessible to screen readers simultaneously
-- Print layouts where all content must render
-- SEO-critical content that must be in initial HTML
diff --git a/.agents/skills/vue-best-practices/references/plugins.md b/.agents/skills/vue-best-practices/references/plugins.md
deleted file mode 100644
index 190cee8..0000000
--- a/.agents/skills/vue-best-practices/references/plugins.md
+++ /dev/null
@@ -1,166 +0,0 @@
----
-title: Vue Plugin Best Practices
-impact: MEDIUM
-impactDescription: Incorrect plugin structure or injection key strategy causes install failures, collisions, and unsafe APIs
-type: best-practice
-tags: [vue3, plugins, provide-inject, typescript, dependency-injection]
----
-
-# Vue Plugin Best Practices
-
-**Impact: MEDIUM** - Vue plugins should follow the `app.use()` contract, expose explicit capabilities, and use collision-safe injection keys. This keeps plugin setup predictable and composable across large apps.
-
-## Task List
-
-- Export plugins as an object with `install()` or as an install function
-- Use the `app` instance in `install()` to register components/directives/provides
-- Type plugin APIs with `Plugin` (and options tuple types when needed)
-- Use symbol keys (prefer `InjectionKey<T>`) for `provide/inject` in plugins
-- Add a small typed composable wrapper for required injections to fail fast
-
-## Structure Plugins for `app.use()`
-
-A Vue plugin must be either:
-- An object with `install(app, options?)`
-- A function with the same signature
-
-**BAD:**
-```ts
-const notAPlugin = {
-  doSomething() {}
-}
-
-app.use(notAPlugin)
-```
-
-**GOOD:**
-```ts
-import type { App } from 'vue'
-
-interface PluginOptions {
-  prefix?: string
-  debug?: boolean
-}
-
-const myPlugin = {
-  install(app: App, options: PluginOptions = {}) {
-    const { prefix = 'my', debug = false } = options
-
-    if (debug) {
-      console.log('Installing myPlugin with prefix:', prefix)
-    }
-
-    app.provide('myPlugin', { prefix })
-  }
-}
-
-app.use(myPlugin, { prefix: 'custom', debug: true })
-```
-
-**GOOD:**
-```ts
-import type { App } from 'vue'
-
-function simplePlugin(app: App, options?: { message: string }) {
-  app.config.globalProperties.$greet = () => options?.message ?? 'Hello!'
-}
-
-app.use(simplePlugin, { message: 'Welcome!' })
-```
-
-## Register Capabilities Explicitly in `install()`
-
-Inside `install()`, wire behavior through Vue application APIs:
-- `app.component()` for global components
-- `app.directive()` for global directives
-- `app.provide()` for injectable services and config
-- `app.config.globalProperties` for optional global helpers (sparingly)
-
-**BAD:**
-```ts
-const uselessPlugin = {
-  install(app, options) {
-    const service = createService(options)
-  }
-}
-```
-
-**GOOD:**
-```ts
-const usefulPlugin = {
-  install(app, options) {
-    const service = createService(options)
-    app.provide(serviceKey, service)
-  }
-}
-```
-
-## Type Plugin Contracts
-
-Use Vue's `Plugin` type to keep install signatures and options type-safe.
-
-```ts
-import type { App, Plugin } from 'vue'
-
-interface MyOptions {
-  apiKey: string
-}
-
-const myPlugin: Plugin<[MyOptions]> = {
-  install(app: App, options: MyOptions) {
-    app.provide(apiKeyKey, options.apiKey)
-  }
-}
-```
-
-## Use Symbol Injection Keys in Plugins
-
-String keys can collide (`'http'`, `'config'`, `'i18n'`). Use symbol keys with `InjectionKey<T>` so injections are unique and typed.
-
-**BAD:**
-```ts
-export default {
-  install(app) {
-    app.provide('http', axios)
-    app.provide('config', appConfig)
-  }
-}
-```
-
-**GOOD:**
-```ts
-import type { InjectionKey } from 'vue'
-import type { AxiosInstance } from 'axios'
-
-interface AppConfig {
-  apiUrl: string
-  timeout: number
-}
-
-export const httpKey: InjectionKey<AxiosInstance> = Symbol('http')
-export const configKey: InjectionKey<AppConfig> = Symbol('appConfig')
-
-export default {
-  install(app) {
-    app.provide(httpKey, axios)
-    app.provide(configKey, { apiUrl: '/api', timeout: 5000 })
-  }
-}
-```
-
-## Provide Required Injection Helpers
-
-Wrap required injections in composables that throw clear setup errors.
-
-```ts
-import { inject } from 'vue'
-import { authKey, type AuthService } from '@/injection-keys'
-
-export function useAuth(): AuthService {
-  const auth = inject(authKey)
-  if (!auth) {
-    throw new Error('Auth plugin not installed. Did you forget app.use(authPlugin)?')
-  }
-  return auth
-}
-```
diff --git a/.agents/skills/vue-best-practices/references/reactivity.md b/.agents/skills/vue-best-practices/references/reactivity.md
deleted file mode 100644
index 4cf0ad3..0000000
--- a/.agents/skills/vue-best-practices/references/reactivity.md
+++ /dev/null
@@ -1,344 +0,0 @@
----
-title: Reactivity Core Patterns (ref, reactive, shallowRef, computed, watch)
-impact: MEDIUM
-impactDescription: Clear reactivity choices keep state predictable and reduce unnecessary updates in Vue 3 apps
-type: efficiency
-tags: [vue3, reactivity, ref, reactive, shallowRef, computed, watch, watchEffect, external-state, best-practice]
----
-
-# Reactivity Core Patterns (ref, reactive, shallowRef, computed, watch)
-
-**Impact: MEDIUM** - Choose the right reactive primitive first, derive with `computed`, and use watchers only for side effects.
-
-This reference covers the core reactivity decisions for local state, external data, derived values, and effects.
-
-## Task List
-
-- Declare reactive state correctly
-  - Always use `shallowRef()` instead of `ref()` for primitive values
-  - Choose the correct reactive declaration method for objects/arrays/map/set
-- Follow best practices for `reactive`
-  - Avoid destructuring from `reactive()` directly
-  - Watch correctly for `reactive`
-- Follow best practices for `computed`
-  - Prefer `computed` over watcher-assigned derived refs
-  - Keep filtered/sorted derivations out of templates
-  - Use `computed` for reusable class/style logic
-  - Keep computed getters pure (no side effects) and put side effects in watchers
-- Follow best practices for watchers
-  - Use `immediate: true` instead of duplicate initial calls
-  - Clean up async effects for watchers
-
-## Declare reactive state correctly
-
-### Always use `shallowRef()` instead of `ref()` for primitive values (string, number, boolean, null, etc.) for better performance.
-
-**Incorrect:**
-```ts
-import { ref } from 'vue'
-const count = ref(0)
-```
-
-**Correct:**
-```ts
-import { shallowRef } from 'vue'
-const count = shallowRef(0)
-```
-
-### Choose the correct reactive declaration method for objects/arrays/map/set
-
-Use `ref()` when you often **replace the entire value** (`state.value = newObj`) and still want deep reactivity inside it, usually used for:
-
-- Frequently reassigned state (replace fetched object/list, reset to defaults, switch presets).
-- Composable return values where updates happen mostly via `.value` reassignment.
-
-Use `reactive()` when you mainly **mutate properties** and full replacement is uncommon, usually used for:
-
-- “Single state object” patterns (stores/forms): `state.count++`, `state.items.push(...)`, `state.user.name = ...`.
-- Situations where you want to avoid `.value` and update nested fields in place.
-
-```ts
-import { reactive } from 'vue'
-
-const state = reactive({
-  count: 0,
-  user: { name: 'Alice', age: 30 }
-})
-
-state.count++ // ✅ reactive
-state.user.age = 31 // ✅ reactive
-// ❌ avoid replacing the reactive object reference:
-// state = reactive({ count: 1 })
-```
-
-Use `shallowRef()` when the value is **opaque / should not be proxied** (class instances, external library objects, very large nested data) and you only want updates to trigger when you **replace** `state.value` (no deep tracking), usually used for:
-
-- Storing external instances/handles (SDK clients, class instances) without Vue proxying internals.
-- Large data where you update by replacing the root reference (immutable-style updates).
-
-```ts
-import { shallowRef } from 'vue'
-
-const user = shallowRef({ name: 'Alice', age: 30 })
-
-user.value.age = 31 // ❌ not reactive
-user.value = { name: 'Bob', age: 25 } // ✅ triggers update
-```
-
-Use `shallowReactive()` when you want **only top-level properties** reactive; nested objects remain raw, usually used for:
-
-- Container objects where only top-level keys change and nested payloads should stay unmanaged/unproxied.
-- Mixed structures where Vue tracks the wrapper object, but not deeply nested or foreign objects.
-
-```ts
-import { shallowReactive } from 'vue'
-
-const state = shallowReactive({
-  count: 0,
-  user: { name: 'Alice', age: 30 }
-})
-
-state.count++ // ✅ reactive
-state.user.age = 31 // ❌ not reactive
-```
-
-## Best practices for `reactive`
-
-### Avoid destructuring from `reactive()` directly
-
-**BAD:**
-
-```ts
-import { reactive } from 'vue'
-
-const state = reactive({ count: 0 })
-const { count } = state // ❌ disconnected from reactivity
-```
-
-### Watch correctly for reactive
-
-**BAD:**
-
-passing a non-getter value into `watch()`
-
-```ts
-import { reactive, watch } from 'vue'
-
-const state = reactive({ count: 0 })
-
-// ❌ watch expects a getter, ref, reactive object, or array of these
-watch(state.count, () => { /* ... */ })
-```
-
-**GOOD:**
-
-preserve reactivity with `toRefs()` and use a getter for `watch()`
-
-```ts
-import { reactive, toRefs, watch } from 'vue'
-
-const state = reactive({ count: 0 })
-const { count } = toRefs(state) // ✅ count is a ref
-
-watch(count, () => { /* ... */ }) // ✅
-watch(() => state.count, () => { /* ... */ }) // ✅
-```
-
-## Best practices for `computed`
-
-### Prefer `computed` over watcher-assigned derived refs
-
-**BAD:**
-```ts
-import { ref, watchEffect } from 'vue'
-
-const items = ref([{ price: 10 }, { price: 20 }])
-const total = ref(0)
-
-watchEffect(() => {
-  total.value = items.value.reduce((sum, item) => sum + item.price, 0)
-})
-```
-
-**GOOD:**
-```ts
-import { ref, computed } from 'vue'
-
-const items = ref([{ price: 10 }, { price: 20 }])
-const total = computed(() =>
-  items.value.reduce((sum, item) => sum + item.price, 0)
-)
-```
-
-### Keep filtered/sorted derivations out of templates
-
-**BAD:**
-```vue
-<template>
-  <li v-for="item in items.filter(item => item.active)" :key="item.id">
-    {{ item.name }}
-  </li>
-
-  <li v-for="item in getSortedItems()" :key="item.id">
-    {{ item.name }}
-  </li>
-</template>
-
-<script setup>
-import { ref } from 'vue'
-
-const items = ref([
-  { id: 1, name: 'B', active: true },
-  { id: 2, name: 'A', active: false }
-])
-
-function getSortedItems() {
-  return [...items.value].sort((a, b) => a.name.localeCompare(b.name))
-}
-</script>
-```
-
-**GOOD:**
-```vue
-<script setup>
-import { ref, computed } from 'vue'
-
-const items = ref([
-  { id: 1, name: 'B', active: true },
-  { id: 2, name: 'A', active: false }
-])
-
-const visibleItems = computed(() =>
-  items.value
-    .filter(item => item.active)
-    .sort((a, b) => a.name.localeCompare(b.name))
-)
-</script>
-
-<template>
-  <li v-for="item in visibleItems" :key="item.id">
-    {{ item.name }}
-  </li>
-</template>
-```
-
-### Use `computed` for reusable class/style logic
-
-**BAD:**
-```vue
-<template>
-  <button :class="{ btn: true, 'btn-primary': type === 'primary' && !disabled, 'btn-disabled': disabled }">
-    {{ label }}
-  </button>
-</template>
-```
-
-**GOOD:**
-```vue
-<script setup>
-import { computed } from 'vue'
-
-const props = defineProps({
-  type: { type: String, default: 'primary' },
-  disabled: Boolean,
-  label: String
-})
-
-const buttonClasses = computed(() => ({
-  btn: true,
-  [`btn-${props.type}`]: !props.disabled,
-  'btn-disabled': props.disabled
-}))
-</script>
-
-<template>
-  <button :class="buttonClasses">
-    {{ label }}
-  </button>
-</template>
-```
-
-### Keep computed getters pure (no side effects) and put side effects in watchers instead
-
-A computed getter should only derive a value. No mutation, no API calls, no storage writes, no event emits.
-([Reference](https://vuejs.org/guide/essentials/computed.html#best-practices))
-
-**BAD:**
-
-side effects inside computed
-
-```ts
-const count = ref(0)
-
-const doubled = computed(() => {
-  // ❌ side effect
-  if (count.value > 10) console.warn('Too big!')
-  return count.value * 2
-})
-```
-
-**GOOD:**
-
-pure computed + `watch()` for side effects
-
-```ts
-const count = ref(0)
-const doubled = computed(() => count.value * 2)
-
-watch(count, (value) => {
-  if (value > 10) console.warn('Too big!')
-})
-```
-
-## Best practices for watchers
-
-### Use `immediate: true` instead of duplicate initial calls
-
-**BAD:**
-```ts
-import { ref, watch, onMounted } from 'vue'
-
-const userId = ref(1)
-
-function loadUser(id) {
-  // ...
-}
-
-onMounted(() => loadUser(userId.value))
-watch(userId, (id) => loadUser(id))
-```
-
-**GOOD:**
-```ts
-import { ref, watch } from 'vue'
-
-const userId = ref(1)
-
-watch(
-  userId,
-  (id) => loadUser(id),
-  { immediate: true }
-)
-```
-
-### Clean up async effects for watchers
-
-When reacting to rapid changes (search boxes, filters), cancel the previous request.
-
-**GOOD:**
-
-```ts
-const query = ref('')
-const results = ref<string[]>([])
-
-watch(query, async (q, _prev, onCleanup) => {
-  const controller = new AbortController()
-  onCleanup(() => controller.abort())
-
-  const res = await fetch(`/api/search?q=${encodeURIComponent(q)}`, {
-    signal: controller.signal,
-  })
-
-  results.value = await res.json()
-})
-```
diff --git a/.agents/skills/vue-best-practices/references/render-functions.md b/.agents/skills/vue-best-practices/references/render-functions.md
deleted file mode 100644
index b64942c..0000000
--- a/.agents/skills/vue-best-practices/references/render-functions.md
+++ /dev/null
@@ -1,201 +0,0 @@
----
-title: Render Function Patterns and Performance
-impact: MEDIUM
-impactDescription: Render functions require explicit patterns for lists, events, v-model, and performance to stay correct and maintainable
-type: best-practice
-tags: [vue3, render-function, h, v-model, directives, performance, jsx]
----
-
-# Render Function Patterns and Performance
-
-**Impact: MEDIUM** - Render functions are powerful but opt out of template compiler optimizations. Use them intentionally and apply the key patterns below to keep output correct and performant.
-
-## Task List
-
-- Prefer templates; use render functions only when templates cannot express the logic
-- Always add stable keys when rendering lists with `h()`/JSX
-- Use `withModifiers` / `withKeys` for event modifiers
-- Implement `v-model` via `modelValue` + `onUpdate:modelValue`
-- Apply custom directives with `withDirectives`
-- Use functional components for stateless presentational UI
-
-## Prefer templates over render functions
-
-**BAD:**
-```vue
-<script setup>
-import { h, ref } from 'vue'
-
-const count = ref(0)
-const render = () => h('div', `Count: ${count.value}`)
-</script>
-```
-
-**GOOD:**
-```vue
-<script setup>
-import { ref } from 'vue'
-
-const count = ref(0)
-</script>
-
-<template>
-  <div>Count: {{ count }}</div>
-</template>
-```
-
-## Always add keys for list rendering
-
-**BAD:**
-```javascript
-import { h, ref } from 'vue'
-
-export default {
-  setup() {
-    const items = ref([{ id: 1, name: 'Apple' }])
-
-    return () => h('ul',
-      items.value.map(item => h('li', item.name))
-    )
-  }
-}
-```
-
-**GOOD:**
-```javascript
-import { h, ref } from 'vue'
-
-export default {
-  setup() {
-    const items = ref([{ id: 1, name: 'Apple' }])
-
-    return () => h('ul',
-      items.value.map(item => h('li', { key: item.id }, item.name))
-    )
-  }
-}
-```
-
-## Use `withModifiers` / `withKeys` for event modifiers
-
-**BAD:**
-```javascript
-import { h } from 'vue'
-
-export default {
-  setup() {
-    const handleClick = (e) => {
-      e.stopPropagation()
-      e.preventDefault()
-    }
-
-    return () => h('button', { onClick: handleClick }, 'Click')
-  }
-}
-```
-
-**GOOD:**
-```javascript
-import { h, withModifiers, withKeys } from 'vue'
-
-export default {
-  setup() {
-    const handleClick = () => {}
-    const handleEnter = () => {}
-
-    return () => h('div', [
-      h('button', {
-        onClick: withModifiers(handleClick, ['stop', 'prevent'])
-      }, 'Click'),
-      h('input', {
-        onKeyup: withKeys(handleEnter, ['enter'])
-      })
-    ])
-  }
-}
-```
-
-## Implement `v-model` explicitly
-
-**BAD:**
-```javascript
-import { h, ref } from 'vue'
-import CustomInput from './CustomInput.vue'
-
-export default {
-  setup() {
-    const text = ref('')
-    return () => h(CustomInput, { modelValue: text.value })
-  }
-}
-```
-
-**GOOD:**
-```javascript
-import { h, ref } from 'vue'
-import CustomInput from './CustomInput.vue'
-
-export default {
-  setup() {
-    const text = ref('')
-    return () => h(CustomInput, {
-      modelValue: text.value,
-      'onUpdate:modelValue': (value) => { text.value = value }
-    })
-  }
-}
-```
-
-## Use `withDirectives` for custom directives
-
-**BAD:**
-```javascript
-import { h } from 'vue'
-
-const vFocus = { mounted: (el) => el.focus() }
-
-export default {
-  setup() {
-    return () => h('input', { 'v-focus': true })
-  }
-}
-```
-
-**GOOD:**
-```javascript
-import { h, withDirectives } from 'vue'
-
-const vFocus = { mounted: (el) => el.focus() }
-
-export default {
-  setup() {
-    return () => withDirectives(h('input'), [[vFocus]])
-  }
-}
-```
-
-## Prefer functional components for stateless UI
-
-**BAD:**
-```javascript
-import { h } from 'vue'
-
-export default {
-  setup() {
-    return () => h('span', { class: 'badge' }, 'New')
-  }
-}
-```
-
-**GOOD:**
-```javascript
-import { h } from 'vue'
-
-function Badge(props, { slots }) {
-  return h('span', { class: 'badge' }, slots.default?.())
-}
-
-Badge.props = ['variant']
-
-export default Badge
-```
diff --git a/.agents/skills/vue-best-practices/references/sfc.md b/.agents/skills/vue-best-practices/references/sfc.md
deleted file mode 100644
index d1c3981..0000000
--- a/.agents/skills/vue-best-practices/references/sfc.md
+++ /dev/null
@@ -1,310 +0,0 @@
----
-title: Single-File Component Structure, Styling, and Template Patterns
-impact: MEDIUM
-impactDescription: Consistent SFC structure and styling choices improve maintainability, tooling support, and render performance
-type: best-practice
-tags: [vue3, sfc, scoped-css, styles, build-tools, performance, template, v-html, v-for, computed, v-if, v-show]
----
-
-# Single-File Component Structure, Styling, and Template Patterns
-
-**Impact: MEDIUM** - Using SFCs with consistent structure and performant styling keeps components easier to maintain and avoids unnecessary render overhead.
-
-## Task List
-
-- Use `.vue` SFCs instead of separate `.js`/`.ts` and `.css` files for components
-- Colocate template, script, and styles in the same SFC by default
-- Use PascalCase for component names in templates and filenames
-- Prefer component-scoped styles
-- Prefer class selectors (not element selectors) in scoped CSS for performance
-- Access DOM / component refs with `useTemplateRef()` in Vue 3.5+
-- Use camelCase keys in `:style` bindings for consistency and IDE support
-- Use `v-for` and `v-if` correctly
-- Never use `v-html` with untrusted/user-provided content
-- Choose `v-if` vs `v-show` based on toggle frequency and initial render cost
-
-## Colocate template, script, and styles
-
-**BAD:**
-```
-components/
-├── UserCard.vue
-├── UserCard.js
-└── UserCard.css
-```
-
-**GOOD:**
-```vue
-<!-- components/UserCard.vue -->
-<script setup>
-import { computed } from 'vue'
-
-const props = defineProps({
-  user: { type: Object, required: true }
-})
-
-const displayName = computed(() =>
-  `${props.user.firstName} ${props.user.lastName}`
-)
-</script>
-
-<template>
-  <div class="user-card">
-    <h3 class="name">{{ displayName }}</h3>
-  </div>
-</template>
-
-<style scoped>
-.user-card {
-  padding: 1rem;
-}
-
-.name {
-  margin: 0;
-}
-</style>
-```
-
-## Use PascalCase for component names
-
-**BAD:**
-```vue
-<script setup>
-import userProfile from './user-profile.vue'
-</script>
-
-<template>
-  <user-profile :user="currentUser" />
-</template>
-```
-
-**GOOD:**
-```vue
-<script setup>
-import UserProfile from './UserProfile.vue'
-</script>
-
-<template>
-  <UserProfile :user="currentUser" />
-</template>
-```
-
-## Best practices for `<style>` block in SFCs
-
-### Prefer component-scoped styles
-
-- Use `<style scoped>` for styles that belong to a component.
-- Keep **global CSS** in a dedicated file (e.g. `src/assets/main.css`) for resets, typography, tokens, etc.
-- Use `:deep()` sparingly (edge cases only).
-
-**BAD:**
-
-```vue
-<style>
-/* ❌ leaks everywhere */
-button { border-radius: 999px; }
-</style>
-```
-
-**GOOD:**
-
-```vue
-<style scoped>
-.button { border-radius: 999px; }
-</style>
-```
-
-**GOOD:**
-
-```css
-/* src/assets/main.css */
-/* ✅ resets, tokens, typography, app-wide rules */
-:root { --radius: 999px; }
-```
-
-### Use class selectors in scoped CSS
-
-**BAD:**
-```vue
-<template>
-  <article>
-    <h1>{{ title }}</h1>
-    <p>{{ subtitle }}</p>
-  </article>
-</template>
-
-<style scoped>
-article { max-width: 800px; }
-h1 { font-size: 2rem; }
-p { line-height: 1.6; }
-</style>
-```
-
-**GOOD:**
-```vue
-<template>
-  <article class="article">
-    <h1 class="article-title">{{ title }}</h1>
-    <p class="article-subtitle">{{ subtitle }}</p>
-  </article>
-</template>
-
-<style scoped>
-.article { max-width: 800px; }
-.article-title { font-size: 2rem; }
-.article-subtitle { line-height: 1.6; }
-</style>
-```
-
-## Access DOM / component refs with `useTemplateRef()`
-
-For Vue 3.5+: use `useTemplateRef()` to access template refs.
-
-```vue
-<script setup lang="ts">
-import { onMounted, useTemplateRef } from 'vue'
-
-const inputRef = useTemplateRef<HTMLInputElement>('input')
-
-onMounted(() => {
-  inputRef.value?.focus()
-})
-</script>
-
-<template>
-  <input ref="input" />
-</template>
-```
-
-## Use camelCase in `:style` bindings
-
-**BAD:**
-```vue
-<template>
-  <div :style="{ 'font-size': fontSize + 'px', 'background-color': bg }">
-    Content
-  </div>
-</template>
-```
-
-**GOOD:**
-```vue
-<template>
-  <div :style="{ fontSize: fontSize + 'px', backgroundColor: bg }">
-    Content
-  </div>
-</template>
-```
-
-## Use `v-for` and `v-if` correctly
-
-### Always provide a stable `:key`
-
-- Prefer primitive keys (`string | number`).
-- Avoid using objects as keys.
-
-**GOOD:**
-
-```vue
-<li v-for="item in items" :key="item.id">
-  <input v-model="item.text" />
-</li>
-```
-
-### Avoid `v-if` and `v-for` on the same element
-
-It leads to unclear intent and unnecessary work.
-([Reference](https://vuejs.org/guide/essentials/list.html#v-for-with-v-if))
-
-**To filter items**
-**BAD:**
-
-```vue
-<li v-for="user in users" v-if="user.active" :key="user.id">
-  {{ user.name }}
-</li>
-```
-
-**GOOD:**
-
-```vue
-<script setup lang="ts">
-import { computed } from 'vue'
-
-const activeUsers = computed(() => users.value.filter(u => u.active))
-</script>
-
-<template>
-  <li v-for="user in activeUsers" :key="user.id">
-    {{ user.name }}
-  </li>
-</template>
-```
-
-**To conditionally show/hide the entire list**
-**GOOD:**
-
-```vue
-<ul v-if="shouldShowUsers">
-  <li v-for="user in users" :key="user.id">
-    {{ user.name }}
-  </li>
-</ul>
-```
-
-## Never render untrusted HTML with `v-html`
-
-**BAD:**
-```vue
-<template>
-  <!-- DANGEROUS: untrusted input can inject scripts -->
-  <article v-html="userProvidedContent"></article>
-</template>
-```
-
-**GOOD:**
-```vue
-<script setup>
-import { computed } from 'vue'
-import DOMPurify from 'dompurify'
-
-const props = defineProps<{
-  trustedHtml?: string
-  plainText: string
-}>()
-
-const safeHtml = computed(() => DOMPurify.sanitize(props.trustedHtml ?? ''))
-</script>
-
-<template>
-  <!-- Preferred: escaped interpolation -->
-  <p>{{ props.plainText }}</p>
-
-  <!-- Only for trusted/sanitized HTML -->
-  <article v-html="safeHtml"></article>
-</template>
-```
-
-## Choose `v-if` vs `v-show` by toggle behavior
-
-**BAD:**
-```vue
-<template>
-  <!-- Frequent toggles with v-if cause repeated mount/unmount -->
-  <ComplexPanel v-if="isPanelOpen" />
-
-  <!-- Rarely shown content with v-show pays initial render cost -->
-  <AdminPanel v-show="isAdmin" />
-</template>
-```
-
-**GOOD:**
-```vue
-<template>
-  <!-- Frequent toggles: keep in DOM, toggle display -->
-  <ComplexPanel v-show="isPanelOpen" />
-
-  <!-- Rare condition: lazy render only when true -->
-  <AdminPanel v-if="isAdmin" />
-</template>
-```
diff --git a/.agents/skills/vue-best-practices/references/state-management.md b/.agents/skills/vue-best-practices/references/state-management.md
deleted file mode 100644
index 02423ab..0000000
--- a/.agents/skills/vue-best-practices/references/state-management.md
+++ /dev/null
@@ -1,135 +0,0 @@
----
-title: State Management Strategy
-impact: HIGH
-impactDescription: Choosing the wrong store pattern can cause SSR request leaks, brittle mutation flows, and poor scaling
-type: best-practice
-tags: [vue3, state-management, pinia, composables, ssr, vueuse]
----
-
-# State Management Strategy
-
-**Impact: HIGH** - Use the lightest state solution that fits your app architecture. SPA-only apps can use lightweight global composables, while SSR/Nuxt apps should default to Pinia for request-safe isolation and predictable tooling.
-
-## Task List
-
-- Keep state local first, then promote to shared/global only when needed
-- Use singleton composables only in non-SSR applications
-- Expose global state as readonly and mutate through explicit actions
-- Prefer Pinia for SSR/Nuxt, large apps, and advanced debugging/plugin needs
-- Avoid exporting mutable module-level reactive state directly
-
-## Choose the Lightest Store Approach
-
-- **Feature composable:** Default for reusable logic with local/feature-level state.
-- **Singleton composable or VueUse `createGlobalState`:** Small non-SSR apps needing shared app state.
-- **Pinia:** SSR/Nuxt apps, medium-to-large apps, and cases requiring DevTools, plugins, or action tracing.
-
-## Avoid Exporting Mutable Module State
-
-**BAD:**
-```ts
-// store/cart.ts
-import { reactive } from 'vue'
-
-export const cart = reactive({
-  items: [] as Array<{ id: string; qty: number }>
-})
-```
-
-**GOOD:**
-```ts
-// composables/useCartStore.ts
-import { reactive, readonly } from 'vue'
-
-let _store: ReturnType<typeof createCartStore> | null = null
-
-function createCartStore() {
-  const state = reactive({
-    items: [] as Array<{ id: string; qty: number }>
-  })
-
-  function addItem(id: string, qty = 1) {
-    const existing = state.items.find((item) => item.id === id)
-    if (existing) {
-      existing.qty += qty
-      return
-    }
-    state.items.push({ id, qty })
-  }
-
-  return {
-    state: readonly(state),
-    addItem
-  }
-}
-
-export function useCartStore() {
-  if (!_store) _store = createCartStore()
-  return _store
-}
-```
-
-## Do Not Use Runtime Singletons in SSR
-
-Module singletons live for the runtime lifetime. In SSR this can leak state between requests.
-
-**BAD:**
-```ts
-// shared singleton reused across requests
-const cartStore = useCartStore()
-
-export function useServerCart() {
-  return cartStore
-}
-```
-
-**GOOD:**
-
-> `pinia` dependency required.
-
-```ts
-// stores/cart.ts
-import { defineStore } from 'pinia'
-
-export const useCartStore = defineStore('cart', {
-  state: () => ({
-    items: [] as Array<{ id: string; qty: number }>
-  }),
-  actions: {
-    addItem(id: string, qty = 1) {
-      const existing = this.items.find((item) => item.id === id)
-      if (existing) {
-        existing.qty += qty
-        return
-      }
-      this.items.push({ id, qty })
-    }
-  }
-})
-```
-
-## Use `createGlobalState` for Small SPA Global State
-
-> `@vueuse/core` dependency required.
-
-If the app is non-SSR and already uses VueUse, `createGlobalState` removes singleton boilerplate.
-
-```ts
-import { createGlobalState } from '@vueuse/core'
-import { computed, ref } from 'vue'
-
-export const useAuthState = createGlobalState(() => {
-  const token = ref<string | null>(null)
-  const isAuthenticated = computed(() => token.value !== null)
-
-  function setToken(next: string | null) {
-    token.value = next
-  }
-
-  return {
-    token,
-    isAuthenticated,
-    setToken
-  }
-})
-```
diff --git a/.agents/skills/vue-best-practices/references/updated-hook-performance.md b/.agents/skills/vue-best-practices/references/updated-hook-performance.md
deleted file mode 100644
index 6375e86..0000000
--- a/.agents/skills/vue-best-practices/references/updated-hook-performance.md
+++ /dev/null
@@ -1,187 +0,0 @@
----
-title: Avoid Expensive Operations in Updated Hook
-impact: MEDIUM
-impactDescription: Heavy computations in updated hook cause performance bottlenecks and potential infinite loops
-type: capability
-tags: [vue3, vue2, lifecycle, updated, performance, optimization, reactivity]
----
-
-# Avoid Expensive Operations in Updated Hook
-
-**Impact: MEDIUM** - The `updated` hook runs after every reactive state change that causes a re-render. Placing expensive operations, API calls, or state mutations here can cause severe performance degradation, infinite loops, and dropped frames below the optimal 60fps threshold.
-
-Use `updated`/`onUpdated` sparingly for post-DOM-update operations that cannot be handled by watchers or computed properties. For most reactive data handling, prefer watchers (`watch`/`watchEffect`) which provide more control over what triggers the callback.
-
-## Task List
-
-- Never perform API calls in updated hook
-- Never mutate reactive state inside updated (causes infinite loops)
-- Use conditional checks to verify updates are relevant before acting
-- Prefer `watch` or `watchEffect` for reacting to specific data changes
-- Use throttling/debouncing if updated operations are expensive
-- Reserve updated for low-level DOM synchronization tasks
-
-**BAD:**
-```javascript
-// BAD: API call in updated - fires on every re-render
-export default {
-  data() {
-    return { items: [], lastUpdate: null }
-  },
-  updated() {
-    // This runs after every single state change!
-    fetch('/api/sync', {
-      method: 'POST',
-      body: JSON.stringify(this.items)
-    })
-  }
-}
-```
-
-```javascript
-// BAD: State mutation in updated - infinite loop
-export default {
-  data() {
-    return { renderCount: 0 }
-  },
-  updated() {
-    // This causes another update, which triggers updated again!
-    this.renderCount++ // Infinite loop
-  }
-}
-```
-
-```javascript
-// BAD: Heavy computation on every update
-export default {
-  updated() {
-    // Expensive operation runs on every keystroke, every state change
-    this.processedData = this.heavyComputation(this.rawData)
-    this.analytics = this.calculateMetrics(this.allData)
-  }
-}
-```
-
-**GOOD:**
-```javascript
-import debounce from 'lodash-es/debounce'
-
-// GOOD: Use watcher for specific data changes
-export default {
-  data() {
-    return { items: [] }
-  },
-  watch: {
-    // Only fires when items actually changes
-    items: {
-      handler(newItems) {
-        this.syncToServer(newItems)
-      },
-      deep: true
-    }
-  },
-  methods: {
-    syncToServer: debounce(function(items) {
-      fetch('/api/sync', {
-        method: 'POST',
-        body: JSON.stringify(items)
-      })
-    }, 500)
-  }
-}
-```
-
-```vue
-<!-- GOOD: Composition API with targeted watchers -->
-<script setup>
-import { ref, watch, onUpdated } from 'vue'
-import { useDebounceFn } from '@vueuse/core'
-
-const items = ref([])
-const scrollContainer = ref(null)
-
-// Watch specific data - not all updates
-watch(items, (newItems) => {
-  syncToServer(newItems)
-}, { deep: true })
-
-const syncToServer = useDebounceFn((items) => {
-  fetch('/api/sync', { method: 'POST', body: JSON.stringify(items) })
-}, 500)
-
-// Only use onUpdated for DOM synchronization
-onUpdated(() => {
-  // Scroll to bottom only if content changed height
-  if (scrollContainer.value) {
-    scrollContainer.value.scrollTop = scrollContainer.value.scrollHeight
-  }
-})
-</script>
-```
-
-```javascript
-// GOOD: Conditional check in updated hook
-export default {
-  data() {
-    return {
-      content: '',
-      lastSyncedContent: ''
-    }
-  },
-  updated() {
-    // Only act if specific condition is met
-    if (this.content !== this.lastSyncedContent) {
-      this.syncContent()
-      this.lastSyncedContent = this.content
-    }
-  },
-  methods: {
-    syncContent: debounce(function() {
-      // Sync logic
-    }, 300)
-  }
-}
-```
-
-## Valid Use Cases for Updated Hook
-
-```javascript
-// GOOD: Low-level DOM synchronization
-export default {
-  updated() {
-    // Sync third-party library with Vue's DOM
-    this.thirdPartyWidget.refresh()
-
-    // Update scroll position after content change
-    this.$nextTick(() => {
-      this.maintainScrollPosition()
-    })
-  }
-}
-```
-
-## Prefer Computed Properties for Derived Data
-
-```javascript
-// BAD: Calculating derived data in updated
-export default {
-  data() {
-    return { numbers: [1, 2, 3, 4, 5] }
-  },
-  updated() {
-    this.sum = this.numbers.reduce((a, b) => a + b, 0) // Causes another update!
-  }
-}
-
-// GOOD: Use computed property instead
-export default {
-  data() {
-    return { numbers: [1, 2, 3, 4, 5] }
-  },
-  computed: {
-    sum() {
-      return this.numbers.reduce((a, b) => a + b, 0)
-    }
-  }
-}
-```
diff --git a/.agents/skills/vue-router-best-practices/LICENSE.md b/.agents/skills/vue-router-best-practices/LICENSE.md
deleted file mode 100644
index 3f08a54..0000000
--- a/.agents/skills/vue-router-best-practices/LICENSE.md
+++ /dev/null
@@ -1,21 +0,0 @@
-MIT License
-
-Copyright (c) 2025 hyf0, SerKo <https://github.com/serkodev>
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
diff --git a/.agents/skills/vue-router-best-practices/SKILL.md b/.agents/skills/vue-router-best-practices/SKILL.md
deleted file mode 100644
index 6488d42..0000000
--- a/.agents/skills/vue-router-best-practices/SKILL.md
+++ /dev/null
@@ -1,23 +0,0 @@
----
-name: vue-router-best-practices
-description: "Vue Router 4 patterns, navigation guards, route params, and route-component lifecycle interactions."
-version: 1.0.0
-license: MIT
-author: github.com/vuejs-ai
----
-
-Vue Router best practices, common gotchas, and navigation patterns.
-
-### Navigation Guards
-- Navigating between same route with different params → See [router-beforeenter-no-param-trigger](reference/router-beforeenter-no-param-trigger.md)
-- Accessing component instance in beforeRouteEnter guard → See [router-beforerouteenter-no-this](reference/router-beforerouteenter-no-this.md)
-- Navigation guard making API calls without awaiting → See [router-guard-async-await-pattern](reference/router-guard-async-await-pattern.md)
-- Users trapped in infinite redirect loops → See [router-navigation-guard-infinite-loop](reference/router-navigation-guard-infinite-loop.md)
-- Navigation guard using deprecated next() function → See [router-navigation-guard-next-deprecated](reference/router-navigation-guard-next-deprecated.md)
-
-### Route Lifecycle
-- Stale data when navigating between same route → See [router-param-change-no-lifecycle](reference/router-param-change-no-lifecycle.md)
-- Event listeners persisting after component unmounts → See [router-simple-routing-cleanup](reference/router-simple-routing-cleanup.md)
-
-### Setup
-- Building production single-page application → See [router-use-vue-router-for-production](reference/router-use-vue-router-for-production.md)
diff --git a/.agents/skills/vue-router-best-practices/SYNC.md b/.agents/skills/vue-router-best-practices/SYNC.md
deleted file mode 100644
index c549070..0000000
--- a/.agents/skills/vue-router-best-practices/SYNC.md
+++ /dev/null
@@ -1,5 +0,0 @@
-# Sync Info
-
-- **Source:** `vendor/vuejs-ai/skills/vue-router-best-practices`
-- **Git SHA:** `f3dd1bf4d3ac78331bdc903e4519d561c538ca6a`
-- **Synced:** 2026-03-16
diff --git a/.agents/skills/vue-router-best-practices/reference/router-beforeenter-no-param-trigger.md b/.agents/skills/vue-router-best-practices/reference/router-beforeenter-no-param-trigger.md
deleted file mode 100644
index 1693a13..0000000
--- a/.agents/skills/vue-router-best-practices/reference/router-beforeenter-no-param-trigger.md
+++ /dev/null
@@ -1,167 +0,0 @@
----
-title: Per-Route beforeEnter Guards Ignore Param/Query Changes
-impact: MEDIUM
-impactDescription: Route-level beforeEnter guards don't fire when only params, query, or hash change, causing unexpected bypasses of validation logic
-type: gotcha
-tags: [vue3, vue-router, navigation-guards, params, query]
----
-
-# Per-Route beforeEnter Guards Ignore Param/Query Changes
-
-**Impact: MEDIUM** - The `beforeEnter` guard defined in route configuration only triggers when entering a route from a DIFFERENT route. Changes to params, query strings, or hash within the same route do NOT trigger `beforeEnter`, potentially bypassing important validation logic.
-
-## Task Checklist
-
-- [ ] Use in-component `onBeforeRouteUpdate` for param/query changes
-- [ ] Or use global `beforeEach` with route.params/query checks
-- [ ] Document which guards protect which scenarios
-- [ ] Test navigation between same route with different params
-
-## The Problem
-
-```javascript
-// router.js
-const routes = [
-  {
-    path: '/orders/:id',
-    component: OrderDetail,
-    beforeEnter: async (to, from) => {
-      // This runs when entering from /products
-      // But NOT when navigating from /orders/1 to /orders/2!
-      const order = await checkOrderAccess(to.params.id)
-      if (!order.canView) {
-        return '/unauthorized'
-      }
-    }
-  }
-]
-```
-
-**Scenario:**
-1. User navigates from `/products` to `/orders/1` - beforeEnter runs, access checked
-2. User navigates from `/orders/1` to `/orders/2` - beforeEnter DOES NOT run!
-3. User might access order they don't have permission for!
-
-## What Triggers beforeEnter vs. What Doesn't
-
-| Navigation | beforeEnter fires? |
-|------------|-------------------|
-| `/products` → `/orders/1` | YES |
-| `/orders/1` → `/orders/2` | NO |
-| `/orders/1` → `/orders/1?tab=details` | NO |
-| `/orders/1#section` → `/orders/1#other` | NO |
-| `/orders/1` → `/products` → `/orders/2` | YES (leaving and re-entering) |
-
-## Solution 1: Add In-Component Guard
-
-```vue
-<!-- OrderDetail.vue -->
-<script setup>
-import { onBeforeRouteUpdate } from 'vue-router'
-
-// Handle param changes within the same route
-onBeforeRouteUpdate(async (to, from) => {
-  if (to.params.id !== from.params.id) {
-    const order = await checkOrderAccess(to.params.id)
-    if (!order.canView) {
-      return '/unauthorized'
-    }
-  }
-})
-</script>
-```
-
-## Solution 2: Use Global beforeEach Instead
-
-```javascript
-// router.js
-router.beforeEach(async (to, from) => {
-  // Handle all order access checks globally
-  if (to.name === 'OrderDetail') {
-    // This runs on EVERY navigation to this route, including param changes
-    const order = await checkOrderAccess(to.params.id)
-    if (!order.canView) {
-      return '/unauthorized'
-    }
-  }
-})
-```
-
-## Solution 3: Combine Both Guards
-
-```javascript
-// router.js - For entering from different route
-const routes = [
-  {
-    path: '/orders/:id',
-    component: OrderDetail,
-    beforeEnter: (to) => validateOrderAccess(to.params.id)
-  }
-]
-
-// In component - For param changes within route
-// OrderDetail.vue
-onBeforeRouteUpdate((to) => validateOrderAccess(to.params.id))
-
-// Shared validation function
-async function validateOrderAccess(orderId) {
-  const order = await checkOrderAccess(orderId)
-  if (!order.canView) {
-    return '/unauthorized'
-  }
-}
-```
-
-## Solution 4: Use beforeEnter with Array of Guards
-
-```javascript
-// guards/orderGuards.js
-export const orderAccessGuard = async (to) => {
-  const order = await checkOrderAccess(to.params.id)
-  if (!order.canView) {
-    return '/unauthorized'
-  }
-}
-
-// router.js
-const routes = [
-  {
-    path: '/orders/:id',
-    component: OrderDetail,
-    beforeEnter: [orderAccessGuard]  // Can add multiple guards
-  }
-]
-
-// Still need in-component guard for param changes!
-```
-
-## Full Navigation Guard Execution Order
-
-Understanding when each guard type fires:
-
-```
-1. beforeRouteLeave (in-component, leaving component)
-2. beforeEach (global)
-3. beforeEnter (per-route, ONLY when entering from different route)
-4. beforeRouteEnter (in-component, entering component)
-5. beforeResolve (global)
-6. afterEach (global, after navigation confirmed)
-
-For param/query changes on same route:
-1. beforeRouteUpdate (in-component) - ONLY this fires!
-2. beforeEach (global)
-3. beforeResolve (global)
-4. afterEach (global)
-```
-
-## Key Points
-
-1. **beforeEnter is for route ENTRY only** - Not for within-route changes
-2. **Use onBeforeRouteUpdate for param changes** - This is the in-component solution
-3. **Global beforeEach always runs** - Good for centralized validation
-4. **Test param change scenarios** - Easy to miss during development
-5. **Consider security implications** - Param-based access control needs both guards
-
-## Reference
-- [Vue Router Navigation Guards](https://router.vuejs.org/guide/advanced/navigation-guards.html)
-- [Vue Router Per-Route Guards](https://router.vuejs.org/guide/advanced/navigation-guards.html#per-route-guard)
diff --git a/.agents/skills/vue-router-best-practices/reference/router-beforerouteenter-no-this.md b/.agents/skills/vue-router-best-practices/reference/router-beforerouteenter-no-this.md
deleted file mode 100644
index 795d6ee..0000000
--- a/.agents/skills/vue-router-best-practices/reference/router-beforerouteenter-no-this.md
+++ /dev/null
@@ -1,176 +0,0 @@
----
-title: beforeRouteEnter Cannot Access Component Instance
-impact: MEDIUM
-impactDescription: The beforeRouteEnter guard runs before component creation, so 'this' is undefined; use the next callback to access the instance
-type: gotcha
-tags: [vue3, vue-router, navigation-guards, lifecycle, this]
----
-
-# beforeRouteEnter Cannot Access Component Instance
-
-**Impact: MEDIUM** - The `beforeRouteEnter` in-component navigation guard executes BEFORE the component is created, meaning you cannot access `this` or any component instance properties. This is the ONLY navigation guard that supports a callback in the `next()` function to access the component instance after navigation.
-
-## Task Checklist
-
-- [ ] Use next(vm => ...) callback to access component instance
-- [ ] Or use composition API guards which have different patterns
-- [ ] Move data fetching logic appropriately based on timing needs
-- [ ] Consider using global guards for data that doesn't need component access
-
-## The Problem
-
-```javascript
-// Options API - WRONG: this is undefined
-export default {
-  data() {
-    return { user: null }
-  },
-  beforeRouteEnter(to, from, next) {
-    // BUG: this is undefined here - component doesn't exist yet!
-    this.user = await fetchUser(to.params.id)  // ERROR!
-    next()
-  }
-}
-```
-
-## Solution: Use next() Callback (Options API)
-
-```javascript
-// Options API - CORRECT: Use callback to access vm
-export default {
-  data() {
-    return {
-      user: null,
-      loading: true
-    }
-  },
-
-  beforeRouteEnter(to, from, next) {
-    // Fetch data before component exists
-    fetchUser(to.params.id)
-      .then(user => {
-        // Pass callback to next() - receives component instance as 'vm'
-        next(vm => {
-          vm.user = user
-          vm.loading = false
-        })
-      })
-      .catch(error => {
-        next(vm => {
-          vm.error = error
-          vm.loading = false
-        })
-      })
-  }
-}
-```
-
-## Solution: Async beforeRouteEnter (Options API)
-
-```javascript
-export default {
-  data() {
-    return { userData: null }
-  },
-
-  async beforeRouteEnter(to, from, next) {
-    try {
-      const user = await fetchUser(to.params.id)
-
-      // Still need callback for component access
-      next(vm => {
-        vm.userData = user
-      })
-    } catch (error) {
-      // Redirect on error
-      next('/error')
-    }
-  }
-}
-```
-
-## Composition API Alternative
-
-In Composition API with `<script setup>`, you cannot use `beforeRouteEnter` directly because the component instance is being set up. Use different patterns instead:
-
-```vue
-<script setup>
-import { ref, onMounted } from 'vue'
-import { useRoute, onBeforeRouteUpdate } from 'vue-router'
-
-const route = useRoute()
-const user = ref(null)
-const loading = ref(true)
-
-// Option 1: Fetch in onMounted (after component exists)
-onMounted(async () => {
-  user.value = await fetchUser(route.params.id)
-  loading.value = false
-})
-
-// Option 2: Handle subsequent param changes
-onBeforeRouteUpdate(async (to, from) => {
-  if (to.params.id !== from.params.id) {
-    loading.value = true
-    user.value = await fetchUser(to.params.id)
-    loading.value = false
-  }
-})
-</script>
-```
-
-## Route-Level Data Fetching
-
-For data that should load BEFORE navigation, use route-level guards:
-
-```javascript
-// router.js
-const routes = [
-  {
-    path: '/users/:id',
-    component: () => import('./UserProfile.vue'),
-    beforeEnter: async (to, from) => {
-      try {
-        // Store data for component to access
-        const user = await fetchUser(to.params.id)
-        to.meta.user = user  // Attach to route meta
-      } catch (error) {
-        return '/error'
-      }
-    }
-  }
-]
-```
-
-```vue
-<!-- UserProfile.vue -->
-<script setup>
-import { useRoute } from 'vue-router'
-
-const route = useRoute()
-// Access pre-fetched data from meta
-const user = route.meta.user
-</script>
-```
-
-## Comparison of Navigation Guards
-
-| Guard | Has `this`/component? | Can delay navigation? | Use case |
-|-------|----------------------|----------------------|----------|
-| beforeRouteEnter | NO (use next callback) | YES | Pre-fetch, redirect if data missing |
-| beforeRouteUpdate | YES | YES | React to param changes |
-| beforeRouteLeave | YES | YES | Unsaved changes warning |
-| Global beforeEach | NO | YES | Auth checks |
-| Route beforeEnter | NO | YES | Route-specific validation |
-
-## Key Points
-
-1. **beforeRouteEnter runs before component creation** - No access to `this`
-2. **Use next(vm => ...) callback** - Only way to access component instance
-3. **Composition API has limitations** - Use onMounted or global guards instead
-4. **Consider route meta for pre-fetched data** - Clean separation of concerns
-5. **beforeRouteUpdate and beforeRouteLeave have component access** - They run when component exists
-
-## Reference
-- [Vue Router In-Component Guards](https://router.vuejs.org/guide/advanced/navigation-guards.html#in-component-guards)
-- [Vue Router Navigation Resolution Flow](https://router.vuejs.org/guide/advanced/navigation-guards.html#the-full-navigation-resolution-flow)
diff --git a/.agents/skills/vue-router-best-practices/reference/router-guard-async-await-pattern.md b/.agents/skills/vue-router-best-practices/reference/router-guard-async-await-pattern.md
deleted file mode 100644
index 185dcda..0000000
--- a/.agents/skills/vue-router-best-practices/reference/router-guard-async-await-pattern.md
+++ /dev/null
@@ -1,227 +0,0 @@
----
-title: Async Navigation Guards Require Proper Promise Handling
-impact: MEDIUM
-impactDescription: Unawaited promises in guards cause navigation to complete before async checks finish, allowing unauthorized access or missing data
-type: gotcha
-tags: [vue3, vue-router, navigation-guards, async, promises]
----
-
-# Async Navigation Guards Require Proper Promise Handling
-
-**Impact: MEDIUM** - Navigation guards that perform async operations (API calls, auth checks) must properly handle promises. If you don't await async operations or return the promise, navigation completes before your check finishes, potentially allowing unauthorized access or navigating with incomplete data.
-
-## Task Checklist
-
-- [ ] Use async/await in navigation guards
-- [ ] Return the promise if not using async/await
-- [ ] Add loading states for long async operations
-- [ ] Implement timeouts for slow API calls
-- [ ] Handle errors to prevent navigation hanging
-
-## The Problem
-
-```javascript
-// WRONG: Not awaiting - navigation proceeds immediately
-router.beforeEach((to, from) => {
-  if (to.meta.requiresAuth) {
-    checkAuth()  // This returns a Promise but we're not waiting!
-    // Navigation continues before checkAuth completes
-  }
-})
-
-// WRONG: Async function but forgot return
-router.beforeEach(async (to, from) => {
-  if (to.meta.requiresAuth) {
-    const isValid = await checkAuth()
-    if (!isValid) {
-      // This redirect might happen after navigation already completed!
-      return '/login'
-    }
-  }
-  // Missing return - implicitly returns undefined, allowing navigation
-})
-```
-
-## Solution: Proper Async/Await Pattern
-
-```javascript
-// CORRECT: Async function with proper returns
-router.beforeEach(async (to, from) => {
-  if (to.meta.requiresAuth) {
-    try {
-      const isAuthenticated = await checkAuth()
-
-      if (!isAuthenticated) {
-        return { name: 'Login', query: { redirect: to.fullPath } }
-      }
-    } catch (error) {
-      console.error('Auth check failed:', error)
-      return { name: 'Error', params: { message: 'Authentication failed' } }
-    }
-  }
-  // Explicitly return nothing to proceed
-  return true
-})
-```
-
-## Solution: Promise-Based Pattern (Alternative)
-
-```javascript
-// CORRECT: Return promise explicitly
-router.beforeEach((to, from) => {
-  if (to.meta.requiresAuth) {
-    return checkAuth()
-      .then(isAuthenticated => {
-        if (!isAuthenticated) {
-          return { name: 'Login' }
-        }
-      })
-      .catch(error => {
-        console.error('Auth check failed:', error)
-        return { name: 'Error' }
-      })
-  }
-})
-```
-
-## Loading State During Async Guards
-
-```javascript
-// app/composables/useNavigationLoading.js
-import { ref } from 'vue'
-
-const isNavigating = ref(false)
-
-export function useNavigationLoading() {
-  return { isNavigating }
-}
-
-export function setupNavigationLoading(router) {
-  router.beforeEach(() => {
-    isNavigating.value = true
-  })
-
-  router.afterEach(() => {
-    isNavigating.value = false
-  })
-
-  router.onError(() => {
-    isNavigating.value = false
-  })
-}
-```
-
-```vue
-<!-- App.vue -->
-<script setup>
-import { useNavigationLoading } from '@/composables/useNavigationLoading'
-
-const { isNavigating } = useNavigationLoading()
-</script>
-
-<template>
-  <LoadingBar v-if="isNavigating" />
-  <router-view />
-</template>
-```
-
-## Timeout Pattern for Slow APIs
-
-```javascript
-// CORRECT: Add timeout to prevent indefinite waiting
-function withTimeout(promise, ms = 5000) {
-  return Promise.race([
-    promise,
-    new Promise((_, reject) =>
-      setTimeout(() => reject(new Error('Request timeout')), ms)
-    )
-  ])
-}
-
-router.beforeEach(async (to, from) => {
-  if (to.meta.requiresAuth) {
-    try {
-      const isValid = await withTimeout(checkAuth(), 5000)
-      if (!isValid) {
-        return '/login'
-      }
-    } catch (error) {
-      if (error.message === 'Request timeout') {
-        // Let user through but show warning
-        console.warn('Auth check timed out')
-      } else {
-        return '/login'
-      }
-    }
-  }
-})
-```
-
-## Multiple Async Checks
-
-```javascript
-// CORRECT: Run independent checks in parallel
-router.beforeEach(async (to, from) => {
-  if (to.meta.requiresAuth && to.meta.requiresSubscription) {
-    try {
-      const [isAuthenticated, hasSubscription] = await Promise.all([
-        checkAuth(),
-        checkSubscription()
-      ])
-
-      if (!isAuthenticated) {
-        return '/login'
-      }
-
-      if (!hasSubscription) {
-        return '/subscribe'
-      }
-    } catch (error) {
-      return '/error'
-    }
-  }
-})
-```
-
-## Error Handling Best Practices
-
-```javascript
-router.beforeEach(async (to, from) => {
-  try {
-    // Your async logic here
-    await performChecks(to)
-  } catch (error) {
-    // Always handle errors to prevent navigation from hanging
-
-    if (error.response?.status === 401) {
-      return '/login'
-    }
-
-    if (error.response?.status === 403) {
-      return '/forbidden'
-    }
-
-    if (error.code === 'NETWORK_ERROR') {
-      // Offline - maybe allow navigation but show warning
-      return true
-    }
-
-    // Unknown error - redirect to error page
-    console.error('Navigation guard error:', error)
-    return { name: 'Error', state: { error: error.message } }
-  }
-})
-```
-
-## Key Points
-
-1. **Always await async operations** - Otherwise navigation proceeds immediately
-2. **Return values matter** - Return route to redirect, false to cancel, true/undefined to proceed
-3. **Handle all error cases** - Uncaught errors can hang navigation
-4. **Add timeouts** - Slow APIs shouldn't block navigation indefinitely
-5. **Show loading state** - Users need feedback during async checks
-6. **Parallelize independent checks** - Use Promise.all for better performance
-
-## Reference
-- [Vue Router Navigation Guards](https://router.vuejs.org/guide/advanced/navigation-guards.html)
-- [Vue Router Navigation Failures](https://router.vuejs.org/guide/advanced/navigation-failures.html)
diff --git a/.agents/skills/vue-router-best-practices/reference/router-navigation-guard-infinite-loop.md b/.agents/skills/vue-router-best-practices/reference/router-navigation-guard-infinite-loop.md
deleted file mode 100644
index 38bb577..0000000
--- a/.agents/skills/vue-router-best-practices/reference/router-navigation-guard-infinite-loop.md
+++ /dev/null
@@ -1,187 +0,0 @@
----
-title: Navigation Guard Infinite Redirect Loops
-impact: HIGH
-impactDescription: Misconfigured navigation guards can trap users in infinite redirect loops, crashing the browser or making the app unusable
-type: gotcha
-tags: [vue3, vue-router, navigation-guards, redirect, debugging]
----
-
-# Navigation Guard Infinite Redirect Loops
-
-**Impact: HIGH** - A common mistake in navigation guards is creating conditions that cause infinite redirects. Vue Router will detect this and show a warning, but in production, it can crash the browser or create a broken user experience.
-
-## Task Checklist
-
-- [ ] Always check if already on target route before redirecting
-- [ ] Test guard logic with all possible navigation scenarios
-- [ ] Add route meta to control which routes need protection
-- [ ] Use Vue Router devtools to debug redirect chains
-
-## The Problem
-
-```javascript
-// WRONG: Infinite loop - always redirects to login, even when on login!
-router.beforeEach((to, from) => {
-  if (!isAuthenticated()) {
-    return '/login'  // Redirects to /login, which triggers guard again...
-  }
-})
-
-// WRONG: Circular redirect between two routes
-router.beforeEach((to, from) => {
-  if (to.path === '/dashboard' && !hasProfile()) {
-    return '/profile'
-  }
-  if (to.path === '/profile' && !isVerified()) {
-    return '/dashboard'  // Back to dashboard, which goes to profile...
-  }
-})
-```
-
-**Error you'll see:**
-```
-[Vue Router warn]: Detected an infinite redirection in a navigation guard when going from "/" to "/login". Aborting to avoid a Stack Overflow.
-```
-
-## Solution 1: Exclude Target Route
-
-```javascript
-// CORRECT: Don't redirect if already going to login
-router.beforeEach((to, from) => {
-  if (!isAuthenticated() && to.path !== '/login') {
-    return '/login'
-  }
-})
-
-// CORRECT: Use route name for cleaner check
-router.beforeEach((to, from) => {
-  const publicPages = ['Login', 'Register', 'ForgotPassword']
-
-  if (!isAuthenticated() && !publicPages.includes(to.name)) {
-    return { name: 'Login' }
-  }
-})
-```
-
-## Solution 2: Use Route Meta Fields
-
-```javascript
-// router.js
-const routes = [
-  {
-    path: '/login',
-    name: 'Login',
-    component: Login,
-    meta: { requiresAuth: false }
-  },
-  {
-    path: '/dashboard',
-    name: 'Dashboard',
-    component: Dashboard,
-    meta: { requiresAuth: true }
-  },
-  {
-    path: '/public',
-    name: 'PublicPage',
-    component: PublicPage,
-    meta: { requiresAuth: false }
-  }
-]
-
-// Guard checks meta field
-router.beforeEach((to, from) => {
-  // Only redirect if route requires auth
-  if (to.meta.requiresAuth && !isAuthenticated()) {
-    return { name: 'Login', query: { redirect: to.fullPath } }
-  }
-})
-```
-
-## Solution 3: Handle Redirect Chains Carefully
-
-```javascript
-// CORRECT: Break potential circular redirects
-router.beforeEach((to, from) => {
-  // Prevent redirect loops by tracking redirect depth
-  const redirectCount = to.query._redirectCount || 0
-
-  if (redirectCount > 3) {
-    console.error('Too many redirects, stopping at:', to.path)
-    return '/error'  // Escape hatch
-  }
-
-  if (needsRedirect(to)) {
-    return {
-      path: getRedirectTarget(to),
-      query: { ...to.query, _redirectCount: redirectCount + 1 }
-    }
-  }
-})
-```
-
-## Solution 4: Centralized Redirect Logic
-
-```javascript
-// guards/auth.js
-export function createAuthGuard(router) {
-  const publicRoutes = new Set(['Login', 'Register', 'ForgotPassword', 'ResetPassword'])
-  const guestOnlyRoutes = new Set(['Login', 'Register'])
-
-  router.beforeEach((to, from) => {
-    const isPublic = publicRoutes.has(to.name)
-    const isGuestOnly = guestOnlyRoutes.has(to.name)
-    const isLoggedIn = isAuthenticated()
-
-    // Not logged in, trying to access protected route
-    if (!isLoggedIn && !isPublic) {
-      return { name: 'Login', query: { redirect: to.fullPath } }
-    }
-
-    // Logged in, trying to access guest-only route (like login page)
-    if (isLoggedIn && isGuestOnly) {
-      return { name: 'Dashboard' }
-    }
-
-    // All other cases: proceed
-  })
-}
-```
-
-## Debugging Redirect Loops
-
-```javascript
-// Add logging to understand the redirect chain
-router.beforeEach((to, from) => {
-  console.log(`Navigation: ${from.path} -> ${to.path}`)
-  console.log('Auth state:', isAuthenticated())
-  console.log('Route meta:', to.meta)
-
-  // Your guard logic here
-})
-
-// Or use afterEach for confirmed navigations
-router.afterEach((to, from) => {
-  console.log(`Navigated: ${from.path} -> ${to.path}`)
-})
-```
-
-## Common Redirect Loop Patterns
-
-| Pattern | Problem | Fix |
-|---------|---------|-----|
-| Auth check without exclusion | Login redirects to login | Exclude `/login` from check |
-| Role-based with circular deps | Admin -> User -> Admin | Use single source of truth for role requirements |
-| Onboarding flow | Step 1 -> Step 2 -> Step 1 | Track completion state properly |
-| Redirect query handling | Reading redirect creates new redirect | Process redirect only once |
-
-## Key Points
-
-1. **Always exclude the target route** - Never redirect to a route that would trigger the same redirect
-2. **Use route meta fields** - Cleaner than path string comparisons
-3. **Test edge cases** - Direct URL access, refresh, back button
-4. **Add logging during development** - Helps trace redirect chains
-5. **Have an escape hatch** - Error page or max redirect count
-
-## Reference
-- [Vue Router Navigation Guards](https://router.vuejs.org/guide/advanced/navigation-guards.html)
-- [Vue Router Route Meta Fields](https://router.vuejs.org/guide/advanced/meta.html)
diff --git a/.agents/skills/vue-router-best-practices/reference/router-navigation-guard-next-deprecated.md b/.agents/skills/vue-router-best-practices/reference/router-navigation-guard-next-deprecated.md
deleted file mode 100644
index 9cabf03..0000000
--- a/.agents/skills/vue-router-best-practices/reference/router-navigation-guard-next-deprecated.md
+++ /dev/null
@@ -1,150 +0,0 @@
----
-title: Vue Router Navigation Guard next() Function Deprecated
-impact: HIGH
-impactDescription: Using the deprecated next() function incorrectly causes navigation to hang, infinite loops, or silent failures
-type: gotcha
-tags: [vue3, vue-router, navigation-guards, migration, async]
----
-
-# Vue Router Navigation Guard next() Function Deprecated
-
-**Impact: HIGH** - The third `next()` argument in navigation guards is deprecated in Vue Router 4. While still supported for backward compatibility, using it incorrectly is one of the most common sources of bugs: calling it multiple times, forgetting to call it, or calling it conditionally without proper logic.
-
-## Task Checklist
-
-- [ ] Refactor guards to use return-based syntax instead of next()
-- [ ] Remove all next() calls from navigation guards
-- [ ] Use async/await pattern for asynchronous checks
-- [ ] Return false to cancel, return route to redirect, return nothing to proceed
-
-## The Problem
-
-```javascript
-// WRONG: Using deprecated next() function
-router.beforeEach((to, from, next) => {
-  if (!isAuthenticated) {
-    next('/login')  // Easy to forget this call
-  }
-  // BUG: next() not called when authenticated - navigation hangs!
-})
-
-// WRONG: Multiple next() calls
-router.beforeEach((to, from, next) => {
-  if (!isAuthenticated) {
-    next('/login')
-  }
-  next()  // BUG: Called twice when not authenticated!
-})
-
-// WRONG: next() in async code without proper handling
-router.beforeEach(async (to, from, next) => {
-  const user = await fetchUser()
-  if (!user) {
-    next('/login')
-  }
-  next()  // Still gets called even after redirect!
-})
-```
-
-## Solution: Use Return-Based Guards
-
-```javascript
-// CORRECT: Return-based syntax (modern Vue Router 4+)
-router.beforeEach((to, from) => {
-  if (!isAuthenticated) {
-    return '/login'  // Redirect
-  }
-  // Return nothing (undefined) to proceed
-})
-
-// CORRECT: Return false to cancel navigation
-router.beforeEach((to, from) => {
-  if (hasUnsavedChanges) {
-    return false  // Cancel navigation
-  }
-})
-
-// CORRECT: Async with return-based syntax
-router.beforeEach(async (to, from) => {
-  const user = await fetchUser()
-  if (!user) {
-    return { name: 'Login', query: { redirect: to.fullPath } }
-  }
-  // Proceed with navigation
-})
-```
-
-## Return Values Explained
-
-```javascript
-router.beforeEach((to, from) => {
-  // Return nothing/undefined - allow navigation
-  return
-
-  // Return false - cancel navigation, stay on current route
-  return false
-
-  // Return string path - redirect to path
-  return '/login'
-
-  // Return route object - redirect with full control
-  return { name: 'Login', query: { redirect: to.fullPath } }
-
-  // Return Error - cancel and trigger router.onError()
-  return new Error('Navigation cancelled')
-})
-```
-
-## If You Must Use next() (Legacy Code)
-
-If maintaining legacy code that uses `next()`, follow these rules strictly:
-
-```javascript
-// CORRECT: Exactly one next() call per code path
-router.beforeEach((to, from, next) => {
-  if (!isAuthenticated) {
-    next('/login')
-    return  // CRITICAL: Exit after calling next()
-  }
-
-  if (!hasPermission(to)) {
-    next('/forbidden')
-    return  // CRITICAL: Exit after calling next()
-  }
-
-  next()  // Only reached if all checks pass
-})
-```
-
-## Error Handling Pattern
-
-```javascript
-router.beforeEach(async (to, from) => {
-  try {
-    await validateAccess(to)
-    // Proceed
-  } catch (error) {
-    if (error.status === 401) {
-      return '/login'
-    }
-    if (error.status === 403) {
-      return '/forbidden'
-    }
-    // Log error and proceed anyway (or return false)
-    console.error('Access validation failed:', error)
-    return false
-  }
-})
-```
-
-## Key Points
-
-1. **Prefer return-based syntax** - Cleaner, less error-prone, modern standard
-2. **next() must be called exactly once** - If using legacy syntax, ensure single call per path
-3. **Always return/exit after redirect** - Prevent multiple navigation actions
-4. **Async guards work naturally** - Just return the redirect route or nothing
-5. **Test all code paths** - Each branch must result in either return or next()
-
-## Reference
-- [Vue Router Navigation Guards](https://router.vuejs.org/guide/advanced/navigation-guards.html)
-- [RFC: Remove next() from Navigation Guards](https://github.com/vuejs/rfcs/discussions/302)
diff --git a/.agents/skills/vue-router-best-practices/reference/router-param-change-no-lifecycle.md b/.agents/skills/vue-router-best-practices/reference/router-param-change-no-lifecycle.md
deleted file mode 100644
index 12457d9..0000000
--- a/.agents/skills/vue-router-best-practices/reference/router-param-change-no-lifecycle.md
+++ /dev/null
@@ -1,181 +0,0 @@
----
-title: Route Param Changes Do Not Trigger Lifecycle Hooks
-impact: HIGH
-impactDescription: Navigating between routes with different params reuses the component instance, skipping created/mounted hooks and leaving stale data
-type: gotcha
-tags: [vue3, vue-router, lifecycle, params, reactivity]
----
-
-# Route Param Changes Do Not Trigger Lifecycle Hooks
-
-**Impact: HIGH** - When navigating between routes that use the same component (e.g., `/users/1` to `/users/2`), Vue Router reuses the existing component instance for performance. This means `onMounted`, `created`, and other lifecycle hooks do NOT fire, leaving you with stale data from the previous route.
-
-## Task Checklist
-
-- [ ] Use `watch` on route params for data fetching
-- [ ] Or use `onBeforeRouteUpdate` in-component guard
-- [ ] Or use `:key="route.params.id"` to force re-creation (less efficient)
-- [ ] Never rely solely on `onMounted` for route-param-dependent data
-
-## The Problem
-
-```vue
-<!-- UserProfile.vue - Used for /users/:id -->
-<script setup>
-import { ref, onMounted } from 'vue'
-import { useRoute } from 'vue-router'
-
-const route = useRoute()
-const user = ref(null)
-
-// BUG: Only runs once when component first mounts!
-// Navigating from /users/1 to /users/2 does NOT trigger this
-onMounted(async () => {
-  user.value = await fetchUser(route.params.id)
-})
-</script>
-
-<template>
-  <div>
-    <!-- Still shows User 1 data when navigating to /users/2! -->
-    <h1>{{ user?.name }}</h1>
-  </div>
-</template>
-```
-
-**Scenario:**
-1. Visit `/users/1` - Component mounts, fetches User 1 data
-2. Navigate to `/users/2` - Component is REUSED, onMounted doesn't run
-3. UI still shows User 1's data!
-
-## Solution 1: Watch Route Params (Recommended)
-
-```vue
-<script setup>
-import { ref, watch } from 'vue'
-import { useRoute } from 'vue-router'
-
-const route = useRoute()
-const user = ref(null)
-const loading = ref(false)
-
-// Watch for param changes - handles both initial load and navigation
-watch(
-  () => route.params.id,
-  async (newId) => {
-    loading.value = true
-    user.value = await fetchUser(newId)
-    loading.value = false
-  },
-  { immediate: true }  // Run immediately for initial load
-)
-</script>
-```
-
-## Solution 2: Use onBeforeRouteUpdate Guard
-
-```vue
-<script setup>
-import { ref, onMounted } from 'vue'
-import { useRoute, onBeforeRouteUpdate } from 'vue-router'
-
-const route = useRoute()
-const user = ref(null)
-
-async function loadUser(id) {
-  user.value = await fetchUser(id)
-}
-
-// Initial load
-onMounted(() => loadUser(route.params.id))
-
-// Handle param changes within same route
-onBeforeRouteUpdate(async (to, from) => {
-  if (to.params.id !== from.params.id) {
-    await loadUser(to.params.id)
-  }
-})
-</script>
-```
-
-## Solution 3: Force Component Re-creation with Key
-
-```vue
-<!-- App.vue or parent component -->
-<template>
-  <router-view :key="$route.fullPath" />
-</template>
-```
-
-**Tradeoffs:**
-- Simple but less performant
-- Destroys and recreates component on every param change
-- Loses component state
-- Use only when component state should reset completely
-
-## Solution 4: Composable for Route-Reactive Data
-
-```javascript
-// composables/useRouteData.js
-import { ref, watch } from 'vue'
-import { useRoute } from 'vue-router'
-
-export function useRouteData(paramName, fetcher) {
-  const route = useRoute()
-  const data = ref(null)
-  const loading = ref(false)
-  const error = ref(null)
-
-  watch(
-    () => route.params[paramName],
-    async (id) => {
-      if (!id) return
-
-      loading.value = true
-      error.value = null
-
-      try {
-        data.value = await fetcher(id)
-      } catch (e) {
-        error.value = e
-      } finally {
-        loading.value = false
-      }
-    },
-    { immediate: true }
-  )
-
-  return { data, loading, error }
-}
-```
-
-```vue
-<!-- Usage in component -->
-<script setup>
-import { useRouteData } from '@/composables/useRouteData'
-import { fetchUser } from '@/api/users'
-
-const { data: user, loading, error } = useRouteData('id', fetchUser)
-</script>
-```
-
-## What Triggers vs. What Doesn't
-
-| Navigation Type | Lifecycle Hooks | beforeRouteUpdate | Watch on params |
-|----------------|-----------------|-------------------|-----------------|
-| `/users/1` to `/posts/1` | YES | NO | YES |
-| `/users/1` to `/users/2` | NO | YES | YES |
-| `/users/1?tab=a` to `/users/1?tab=b` | NO | YES | NO (different watch) |
-| `/users/1` to `/users/1` (same) | NO | NO | NO |
-
-## Key Points
-
-1. **Same route, different params = same component instance** - This is a performance optimization
-2. **Lifecycle hooks only fire once** - When component first mounts
-3. **Use `watch` with `immediate: true`** - Covers both initial load and updates
-4. **`onBeforeRouteUpdate` is navigation-aware** - Good for data that must load before view updates
-5. **`:key="route.fullPath"` is a sledgehammer** - Use only when necessary
-
-## Reference
-- [Vue Router Dynamic Route Matching](https://router.vuejs.org/guide/essentials/dynamic-matching.html#reacting-to-params-changes)
-- [Vue School: Reacting to Param Changes](https://vueschool.io/lessons/reacting-to-param-changes)
diff --git a/.agents/skills/vue-router-best-practices/reference/router-simple-routing-cleanup.md b/.agents/skills/vue-router-best-practices/reference/router-simple-routing-cleanup.md
deleted file mode 100644
index ef31bef..0000000
--- a/.agents/skills/vue-router-best-practices/reference/router-simple-routing-cleanup.md
+++ /dev/null
@@ -1,209 +0,0 @@
----
-title: Simple Hash Routing Requires Event Listener Cleanup
-impact: MEDIUM
-impactDescription: When implementing basic routing without Vue Router, forgetting to remove hashchange listeners causes memory leaks and multiple handler execution
-type: gotcha
-tags: [vue3, routing, events, memory-leak, cleanup]
----
-
-# Simple Hash Routing Requires Event Listener Cleanup
-
-**Impact: MEDIUM** - When implementing basic client-side routing without Vue Router (using hash-based routing with `hashchange` events), you must clean up event listeners when the component unmounts. Failure to do so causes memory leaks and can result in multiple handlers firing after the component is recreated.
-
-## Task Checklist
-
-- [ ] Store event listener reference for cleanup
-- [ ] Use onUnmounted to remove event listener
-- [ ] Consider using Vue Router instead for production apps
-- [ ] Test component mount/unmount cycles
-
-## The Problem
-
-```vue
-<script setup>
-import { ref, computed } from 'vue'
-import Home from './Home.vue'
-import About from './About.vue'
-
-const routes = {
-  '/': Home,
-  '/about': About
-}
-
-const currentPath = ref(window.location.hash)
-
-// BUG: Event listener is never removed!
-// Each time this component mounts, a NEW listener is added
-// After mounting 5 times, you have 5 listeners running
-window.addEventListener('hashchange', () => {
-  currentPath.value = window.location.hash
-})
-
-const currentView = computed(() => {
-  return routes[currentPath.value.slice(1) || '/']
-})
-</script>
-```
-
-**What happens:**
-1. Component mounts, adds listener
-2. Component unmounts (e.g., route change, v-if toggle)
-3. Component mounts again, adds ANOTHER listener
-4. Now TWO listeners respond to each hash change
-5. Eventually causes performance issues and memory leaks
-
-## Solution: Proper Cleanup with onUnmounted
-
-```vue
-<script setup>
-import { ref, computed, onUnmounted } from 'vue'
-import Home from './Home.vue'
-import About from './About.vue'
-import NotFound from './NotFound.vue'
-
-const routes = {
-  '/': Home,
-  '/about': About
-}
-
-const currentPath = ref(window.location.hash)
-
-// Store handler reference for cleanup
-function handleHashChange() {
-  currentPath.value = window.location.hash
-}
-
-// Add listener
-window.addEventListener('hashchange', handleHashChange)
-
-// CRITICAL: Remove listener on unmount
-onUnmounted(() => {
-  window.removeEventListener('hashchange', handleHashChange)
-})
-
-const currentView = computed(() => {
-  return routes[currentPath.value.slice(1) || '/'] || NotFound
-})
-</script>
-```
-
-## Solution: Using Options API
-
-```vue
-<script>
-import Home from './Home.vue'
-import About from './About.vue'
-import NotFound from './NotFound.vue'
-
-const routes = {
-  '/': Home,
-  '/about': About
-}
-
-export default {
-  data() {
-    return {
-      currentPath: window.location.hash
-    }
-  },
-
-  computed: {
-    currentView() {
-      return routes[this.currentPath.slice(1) || '/'] || NotFound
-    }
-  },
-
-  mounted() {
-    // Store bound handler for cleanup
-    this.hashHandler = () => {
-      this.currentPath = window.location.hash
-    }
-    window.addEventListener('hashchange', this.hashHandler)
-  },
-
-  beforeUnmount() {
-    // Clean up
-    window.removeEventListener('hashchange', this.hashHandler)
-  }
-}
-</script>
-```
-
-## Solution: Composable for Reusable Hash Routing
-
-```javascript
-// composables/useHashRouter.js
-import { ref, computed, onUnmounted } from 'vue'
-
-export function useHashRouter(routes, notFoundComponent = null) {
-  const currentPath = ref(window.location.hash)
-
-  function handleHashChange() {
-    currentPath.value = window.location.hash
-  }
-
-  // Setup
-  window.addEventListener('hashchange', handleHashChange)
-
-  // Cleanup - handled automatically when component unmounts
-  onUnmounted(() => {
-    window.removeEventListener('hashchange', handleHashChange)
-  })
-
-  const currentView = computed(() => {
-    const path = currentPath.value.slice(1) || '/'
-    return routes[path] || notFoundComponent
-  })
-
-  function navigate(path) {
-    window.location.hash = path
-  }
-
-  return {
-    currentPath,
-    currentView,
-    navigate
-  }
-}
-```
-
-```vue
-<!-- Usage -->
-<script setup>
-import { useHashRouter } from '@/composables/useHashRouter'
-import Home from './Home.vue'
-import About from './About.vue'
-import NotFound from './NotFound.vue'
-
-const { currentView } = useHashRouter({
-  '/': Home,
-  '/about': About
-}, NotFound)
-</script>
-
-<template>
-  <component :is="currentView" />
-</template>
-```
-
-## When to Use Simple Routing vs Vue Router
-
-| Use Simple Hash Routing | Use Vue Router |
-|------------------------|----------------|
-| Learning/prototyping | Production apps |
-| Very simple apps (2-3 pages) | Nested routes needed |
-| No build step available | Navigation guards needed |
-| Bundle size critical | Lazy loading needed |
-| Static hosting only | History mode (clean URLs) |
-
-## Key Points
-
-1. **Always clean up event listeners** - Use onUnmounted or beforeUnmount
-2. **Store handler reference** - Anonymous functions can't be removed
-3. **Consider Vue Router for real apps** - It handles cleanup automatically
-4. **Test unmount scenarios** - v-if toggling, hot module replacement
-5. **Composables help encapsulate cleanup logic** - Reusable and automatic
-
-## Reference
-- [Vue.js Routing Documentation](https://vuejs.org/guide/scaling-up/routing.html)
-- [Vue Router Official Library](https://router.vuejs.org/)
diff --git a/.agents/skills/vue-router-best-practices/reference/router-use-vue-router-for-production.md b/.agents/skills/vue-router-best-practices/reference/router-use-vue-router-for-production.md
deleted file mode 100644
index 1e60304..0000000
--- a/.agents/skills/vue-router-best-practices/reference/router-use-vue-router-for-production.md
+++ /dev/null
@@ -1,183 +0,0 @@
----
-title: Use Vue Router Library for Production Applications
-impact: LOW
-impactDescription: Simple hash routing lacks essential features for production SPAs; Vue Router provides navigation guards, lazy loading, and proper history management
-type: best-practice
-tags: [vue3, vue-router, spa, production, architecture]
----
-
-# Use Vue Router Library for Production Applications
-
-**Impact: LOW** - While you can implement basic routing with hash changes and dynamic components, the official Vue Router library should be used for any production single-page application. It provides essential features like navigation guards, nested routes, lazy loading, and proper browser history integration that are tedious and error-prone to implement manually.
-
-## Task Checklist
-
-- [ ] Install Vue Router for production SPAs
-- [ ] Use simple routing only for learning or tiny prototypes
-- [ ] Leverage built-in features: guards, lazy loading, meta fields
-- [ ] Consider router-based state and data loading patterns
-
-## When Simple Routing is Acceptable
-
-```vue
-<!-- Only for: learning, prototypes, or micro-apps with 2-3 pages -->
-<script setup>
-import { ref, computed } from 'vue'
-import Home from './Home.vue'
-import About from './About.vue'
-
-const routes = { '/': Home, '/about': About }
-const currentPath = ref(window.location.hash.slice(1) || '/')
-
-window.addEventListener('hashchange', () => {
-  currentPath.value = window.location.hash.slice(1) || '/'
-})
-
-const currentView = computed(() => routes[currentPath.value])
-</script>
-
-<template>
-  <nav>
-    <a href="#/">Home</a>
-    <a href="#/about">About</a>
-  </nav>
-  <component :is="currentView" />
-</template>
-```
-
-## Why Vue Router for Production
-
-### Features You'd Have to Implement Manually
-
-| Feature | Simple Routing | Vue Router |
-|---------|---------------|------------|
-| Navigation guards | Manual, error-prone | Built-in, composable |
-| Nested routes | Complex to implement | Native support |
-| Route params | Parse manually | Automatic extraction |
-| Lazy loading | DIY with dynamic imports | Built-in with code splitting |
-| History mode (clean URLs) | Requires server config + manual | Built-in |
-| Scroll behavior | Manual | Configurable |
-| Route transitions | DIY | Integrated with Transition |
-| Active link styling | Manual class toggling | `router-link-active` class |
-| Programmatic navigation | `location.hash = ...` | `router.push()`, `router.replace()` |
-| Route meta fields | N/A | Built-in |
-
-## Production Setup with Vue Router
-
-```javascript
-// router/index.js
-import { createRouter, createWebHistory } from 'vue-router'
-
-const routes = [
-  {
-    path: '/',
-    name: 'Home',
-    component: () => import('@/views/Home.vue'),  // Lazy loaded
-    meta: { requiresAuth: false }
-  },
-  {
-    path: '/dashboard',
-    name: 'Dashboard',
-    component: () => import('@/views/Dashboard.vue'),
-    meta: { requiresAuth: true },
-    children: [
-      {
-        path: 'settings',
-        name: 'Settings',
-        component: () => import('@/views/Settings.vue')
-      }
-    ]
-  },
-  {
-    path: '/users/:id',
-    name: 'UserProfile',
-    component: () => import('@/views/UserProfile.vue'),
-    props: true  // Pass params as props
-  },
-  {
-    path: '/:pathMatch(.*)*',
-    name: 'NotFound',
-    component: () => import('@/views/NotFound.vue')
-  }
-]
-
-const router = createRouter({
-  history: createWebHistory(),
-  routes,
-  scrollBehavior(to, from, savedPosition) {
-    return savedPosition || { top: 0 }
-  }
-})
-
-// Global navigation guard
-router.beforeEach((to, from) => {
-  if (to.meta.requiresAuth && !isAuthenticated()) {
-    return { name: 'Login', query: { redirect: to.fullPath } }
-  }
-})
-
-export default router
-```
-
-```javascript
-// main.js
-import { createApp } from 'vue'
-import App from './App.vue'
-import router from './router'
-
-createApp(App)
-  .use(router)
-  .mount('#app')
-```
-
-```vue
-<!-- App.vue -->
-<template>
-  <nav>
-    <router-link to="/">Home</router-link>
-    <router-link to="/dashboard">Dashboard</router-link>
-  </nav>
-
-  <router-view v-slot="{ Component }">
-    <transition name="fade" mode="out-in">
-      <component :is="Component" />
-    </transition>
-  </router-view>
-</template>
-```
-
-## Modern Vue Router Features (2025+)
-
-```javascript
-// Data Loading API (Vue Router 4.2+)
-const routes = [
-  {
-    path: '/users/:id',
-    component: UserProfile,
-    // Load data at route level
-    loader: async (route) => {
-      return { user: await fetchUser(route.params.id) }
-    }
-  }
-]
-
-// View Transitions API integration
-const router = createRouter({
-  // Enable native browser view transitions
-  // Requires browser support (Chrome 111+)
-})
-```
-
-## Key Points
-
-1. **Use Vue Router for any app beyond a prototype** - The features are essential
-2. **Simple routing is for learning** - Understand the concepts, then use the library
-3. **Lazy loading is critical for bundle size** - Vue Router makes it trivial
-4. **Navigation guards prevent security issues** - Hard to get right manually
-5. **History mode requires Vue Router** - Clean URLs need proper handling
-6. **New features keep coming** - Data Loading API, View Transitions
-
-## Reference
-- [Vue.js Routing Guide](https://vuejs.org/guide/scaling-up/routing.html)
-- [Vue Router Documentation](https://router.vuejs.org/)
-- [Vue Router Getting Started](https://router.vuejs.org/guide/)
diff --git a/.agents/skills/vue-testing-best-practices/LICENSE.md b/.agents/skills/vue-testing-best-practices/LICENSE.md
deleted file mode 100644
index 3f08a54..0000000
--- a/.agents/skills/vue-testing-best-practices/LICENSE.md
+++ /dev/null
@@ -1,21 +0,0 @@
-MIT License
-
-Copyright (c) 2025 hyf0, SerKo <https://github.com/serkodev>
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
diff --git a/.agents/skills/vue-testing-best-practices/SKILL.md b/.agents/skills/vue-testing-best-practices/SKILL.md
deleted file mode 100644
index c600b52..0000000
--- a/.agents/skills/vue-testing-best-practices/SKILL.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-name: vue-testing-best-practices
-version: 1.0.0
-license: MIT
-author: github.com/vuejs-ai
-description: Use for Vue.js testing. Covers Vitest, Vue Test Utils, component testing, mocking, testing patterns, and Playwright for E2E testing.
----
-
-Vue.js testing best practices, patterns, and common gotchas.
-
-### Testing
-- Setting up test infrastructure for Vue 3 projects → See [testing-vitest-recommended-for-vue](reference/testing-vitest-recommended-for-vue.md)
-- Tests keep breaking when refactoring component internals → See [testing-component-blackbox-approach](reference/testing-component-blackbox-approach.md)
-- Tests fail intermittently with race conditions → See [testing-async-await-flushpromises](reference/testing-async-await-flushpromises.md)
-- Composables using lifecycle hooks or inject fail to test → See [testing-composables-helper-wrapper](reference/testing-composables-helper-wrapper.md)
-- Getting "injection Symbol(pinia) not found" errors in tests → See [testing-pinia-store-setup](reference/testing-pinia-store-setup.md)
-- Components with async setup won't render in tests → See [testing-suspense-async-components](reference/testing-suspense-async-components.md)
-- Snapshot tests keep passing despite broken functionality → See [testing-no-snapshot-only](reference/testing-no-snapshot-only.md)
-- Choosing end-to-end testing framework for Vue apps → See [testing-e2e-playwright-recommended](reference/testing-e2e-playwright-recommended.md)
-- Tests need to verify computed styles or real DOM events → See [testing-browser-vs-node-runners](reference/testing-browser-vs-node-runners.md)
-- Testing components created with defineAsyncComponent fails → See [async-component-testing](reference/async-component-testing.md)
-- Teleported modal content can't be found in wrapper queries → See [teleport-testing-complexity](reference/teleport-testing-complexity.md)
-
-## Reference
-
-- [Vue.js Testing Guide](https://vuejs.org/guide/scaling-up/testing)
-- [Vue Test Utils](https://test-utils.vuejs.org/)
-- [Vitest Documentation](https://vitest.dev/)
-- [Playwright Documentation](https://playwright.dev/)
diff --git a/.agents/skills/vue-testing-best-practices/SYNC.md b/.agents/skills/vue-testing-best-practices/SYNC.md
deleted file mode 100644
index 6e968f2..0000000
--- a/.agents/skills/vue-testing-best-practices/SYNC.md
+++ /dev/null
@@ -1,5 +0,0 @@
-# Sync Info
-
-- **Source:** `vendor/vuejs-ai/skills/vue-testing-best-practices`
-- **Git SHA:** `f3dd1bf4d3ac78331bdc903e4519d561c538ca6a`
-- **Synced:** 2026-03-16
diff --git a/.agents/skills/vue-testing-best-practices/reference/async-component-testing.md b/.agents/skills/vue-testing-best-practices/reference/async-component-testing.md
deleted file mode 100644
index a4d2c49..0000000
--- a/.agents/skills/vue-testing-best-practices/reference/async-component-testing.md
+++ /dev/null
@@ -1,163 +0,0 @@
----
-title: Use flushPromises for Testing Async Components
-impact: HIGH
-impactDescription: Without awaiting async operations, tests make assertions before the component has rendered, causing false negatives
-type: gotcha
-tags: [vue3, testing, async, defineAsyncComponent, flushPromises, vitest]
----
-
-# Use flushPromises for Testing Async Components
-
-**Impact: HIGH** - When testing async components created with `defineAsyncComponent`, you must use `await flushPromises()` to ensure the component has loaded before making assertions. Vue updates asynchronously, so tests that don't account for this will make assertions before the component has rendered.
-
-## Task Checklist
-
-- [ ] Use `async/await` in test functions for async components
-- [ ] Call `await flushPromises()` after mounting async components
-- [ ] Test loading states by making assertions before `flushPromises()`
-- [ ] Test error states using rejected promises in `defineAsyncComponent`
-- [ ] Use `trigger()` with `await` as it returns a Promise
-
-**Incorrect:**
-
-```javascript
-import { mount } from '@vue/test-utils'
-import { defineAsyncComponent } from 'vue'
-
-const AsyncWidget = defineAsyncComponent(() =>
-  import('./Widget.vue')
-)
-
-test('renders async component', () => {
-  const wrapper = mount(AsyncWidget)
-
-  // FAILS: Component hasn't loaded yet
-  expect(wrapper.text()).toContain('Widget Content')
-})
-```
-
-**Correct:**
-
-```javascript
-import { mount, flushPromises } from '@vue/test-utils'
-import { defineAsyncComponent, nextTick } from 'vue'
-
-const AsyncWidget = defineAsyncComponent(() =>
-  import('./Widget.vue')
-)
-
-test('renders async component', async () => {
-  const wrapper = mount(AsyncWidget)
-
-  // Wait for async component to load
-  await flushPromises()
-
-  expect(wrapper.text()).toContain('Widget Content')
-})
-
-test('shows loading state initially', async () => {
-  const AsyncWithLoading = defineAsyncComponent({
-    loader: () => import('./Widget.vue'),
-    loadingComponent: { template: '<div>Loading...</div>' },
-    delay: 0
-  })
-
-  const wrapper = mount(AsyncWithLoading)
-
-  // Check loading state immediately
-  expect(wrapper.text()).toContain('Loading...')
-
-  // Wait for component to load
-  await flushPromises()
-
-  // Check final state
-  expect(wrapper.text()).toContain('Widget Content')
-})
-```
-
-## Testing with Suspense
-
-```javascript
-import { mount, flushPromises } from '@vue/test-utils'
-import { Suspense, defineAsyncComponent, h } from 'vue'
-
-const AsyncWidget = defineAsyncComponent(() =>
-  import('./Widget.vue')
-)
-
-test('renders async component with Suspense', async () => {
-  const wrapper = mount({
-    components: { AsyncWidget },
-    template: `
-      <Suspense>
-        <AsyncWidget />
-        <template #fallback>
-          <div>Loading...</div>
-        </template>
-      </Suspense>
-    `
-  })
-
-  // Initially shows fallback
-  expect(wrapper.text()).toContain('Loading...')
-
-  // Wait for async resolution
-  await flushPromises()
-
-  // Now shows actual content
-  expect(wrapper.text()).toContain('Widget Content')
-})
-```
-
-## Testing Error States
-
-```javascript
-import { mount, flushPromises } from '@vue/test-utils'
-import { defineAsyncComponent } from 'vue'
-
-test('shows error component on load failure', async () => {
-  const AsyncWithError = defineAsyncComponent({
-    loader: () => Promise.reject(new Error('Failed to load')),
-    errorComponent: { template: '<div>Error loading component</div>' }
-  })
-
-  const wrapper = mount(AsyncWithError)
-
-  await flushPromises()
-
-  expect(wrapper.text()).toContain('Error loading component')
-})
-```
-
-## Utilities Reference
-
-| Utility | Purpose |
-|---------|---------|
-| `await flushPromises()` | Resolves all pending promises |
-| `await nextTick()` | Waits for Vue's next DOM update cycle |
-| `await wrapper.trigger('click')` | Triggers event and waits for update |
-
-## Dynamic Import Handling
-
-**Note:** Dynamic imports (`import('./File.vue')`) may require additional handling beyond `flushPromises()` in test environments. Test runners like Vitest handle module resolution differently than runtime bundlers, which can cause timing issues with dynamic imports. If `flushPromises()` alone doesn't resolve the component, consider:
-
-- Mocking the dynamic import to return the component synchronously
-- Using multiple `await flushPromises()` calls in sequence
-- Wrapping assertions in `waitFor()` or retry utilities
-- Configuring your test runner's module resolution settings
-
-```javascript
-// If flushPromises() isn't sufficient, mock the import
-vi.mock('./Widget.vue', () => ({
-  default: { template: '<div>Widget Content</div>' }
-}))
-
-// Or use multiple flush calls for nested async operations
-await flushPromises()
-await flushPromises()
-```
-
-## References
-
-- [Vue Test Utils - Asynchronous Behavior](https://test-utils.vuejs.org/guide/advanced/async-suspense)
-- [Vue.js Async Components Documentation](https://vuejs.org/guide/components/async)
diff --git a/.agents/skills/vue-testing-best-practices/reference/teleport-testing-complexity.md b/.agents/skills/vue-testing-best-practices/reference/teleport-testing-complexity.md
deleted file mode 100644
index 887836f..0000000
--- a/.agents/skills/vue-testing-best-practices/reference/teleport-testing-complexity.md
+++ /dev/null
@@ -1,158 +0,0 @@
----
-title: Teleported Content Requires Special Testing Approach
-impact: MEDIUM
-impactDescription: Vue Test Utils cannot find teleported content using standard wrapper.find() methods
-type: gotcha
-tags: [vue3, teleport, testing, vue-test-utils]
----
-
-# Teleported Content Requires Special Testing Approach
-
-**Impact: MEDIUM** - Vue Test Utils scopes queries to the mounted component. Teleported content renders outside the component's DOM tree, so `wrapper.find()` cannot locate it. This leads to failing tests and confusion.
-
-## Task Checklist
-
-- [ ] Stub Teleport in unit tests to keep content in component tree
-- [ ] Use `document.body` queries for integration tests with real Teleport
-- [ ] Consider using `getComponent()` instead of DOM queries for teleported components
-
-**Problem - Standard Testing Fails:**
-```vue
-<!-- Modal.vue -->
-<template>
-  <button @click="open = true">Open</button>
-  <Teleport to="body">
-    <div v-if="open" class="modal" data-testid="modal">
-      <input type="text" data-testid="modal-input" />
-    </div>
-  </Teleport>
-</template>
-```
-
-```ts
-// Modal.spec.ts - BROKEN
-import { mount } from '@vue/test-utils'
-import Modal from './Modal.vue'
-
-test('modal input exists', async () => {
-  const wrapper = mount(Modal)
-  await wrapper.find('button').trigger('click')
-
-  // FAILS: Teleported content is not in wrapper's DOM tree
-  expect(wrapper.find('[data-testid="modal-input"]').exists()).toBe(true)
-})
-```
-
-**Solution 1 - Stub Teleport:**
-```ts
-import { mount } from '@vue/test-utils'
-import Modal from './Modal.vue'
-
-test('modal input exists', async () => {
-  const wrapper = mount(Modal, {
-    global: {
-      stubs: {
-        // Stub teleport to render content inline
-        Teleport: true
-      }
-    }
-  })
-
-  await wrapper.find('button').trigger('click')
-
-  // Works: Content renders inside wrapper
-  expect(wrapper.find('[data-testid="modal-input"]').exists()).toBe(true)
-})
-```
-
-**Solution 2 - Query Document Body:**
-```ts
-import { mount } from '@vue/test-utils'
-import Modal from './Modal.vue'
-
-test('modal renders to body', async () => {
-  const wrapper = mount(Modal, {
-    attachTo: document.body  // Required for Teleport to work
-  })
-
-  await wrapper.find('button').trigger('click')
-
-  // Query the actual DOM
-  const modal = document.querySelector('[data-testid="modal"]')
-  expect(modal).toBeTruthy()
-
-  const input = document.querySelector('[data-testid="modal-input"]')
-  expect(input).toBeTruthy()
-
-  // Cleanup
-  wrapper.unmount()
-})
-```
-
-**Solution 3 - Custom Teleport Stub with Content Access:**
-```ts
-import { mount, config } from '@vue/test-utils'
-import { h, Teleport } from 'vue'
-import Modal from './Modal.vue'
-
-// Custom stub that renders content in a testable way
-const TeleportStub = {
-  setup(props, { slots }) {
-    return () => h('div', { class: 'teleport-stub' }, slots.default?.())
-  }
-}
-
-test('modal with custom stub', async () => {
-  const wrapper = mount(Modal, {
-    global: {
-      stubs: {
-        Teleport: TeleportStub
-      }
-    }
-  })
-
-  await wrapper.find('button').trigger('click')
-
-  // Content is inside .teleport-stub
-  expect(wrapper.find('.teleport-stub [data-testid="modal-input"]').exists()).toBe(true)
-})
-```
-
-## Testing Vue Final Modal and UI Libraries
-
-Libraries like Vue Final Modal use Teleport internally, causing test failures:
-
-```ts
-// Problem: Vue Final Modal teleports to body
-import { VueFinalModal } from 'vue-final-modal'
-
-test('modal content', async () => {
-  const wrapper = mount(MyComponent, {
-    global: {
-      stubs: {
-        // Stub the modal component to avoid teleport issues
-        VueFinalModal: true
-      }
-    }
-  })
-})
-```
-
-## E2E Testing (Cypress, Playwright)
-
-E2E tests query the real DOM, so Teleport works naturally:
-
-```ts
-// Cypress
-it('opens modal', () => {
-  cy.visit('/page-with-modal')
-  cy.get('button').click()
-
-  // Works: Cypress queries the real DOM
-  cy.get('[data-testid="modal"]').should('be.visible')
-})
-```
-
-## Reference
-- [Vue Test Utils - Teleport](https://test-utils.vuejs.org/guide/advanced/teleport)
-- [Vue Test Utils - Stubs](https://test-utils.vuejs.org/guide/advanced/stubs-shallow-mount)
diff --git a/.agents/skills/vue-testing-best-practices/reference/testing-async-await-flushpromises.md b/.agents/skills/vue-testing-best-practices/reference/testing-async-await-flushpromises.md
deleted file mode 100644
index 597d9c8..0000000
--- a/.agents/skills/vue-testing-best-practices/reference/testing-async-await-flushpromises.md
+++ /dev/null
@@ -1,175 +0,0 @@
----
-title: Properly Handle Async Updates with nextTick and flushPromises
-impact: HIGH
-impactDescription: Race conditions and flaky tests occur when async DOM updates or API calls complete after assertions run
-type: gotcha
-tags: [vue3, testing, async, flushPromises, nextTick, vitest, vue-test-utils, race-condition]
----
-
-# Properly Handle Async Updates with nextTick and flushPromises
-
-**Impact: HIGH** - Vue updates the DOM asynchronously. Without properly awaiting these updates, tests may assert against stale DOM state, causing intermittent failures and false negatives.
-
-Use `await` with triggers and `setValue`, use `nextTick` for reactive updates, and use `flushPromises` for external async operations like API calls.
-
-## Task Checklist
-
-- [ ] Always await `trigger()` and `setValue()` calls
-- [ ] Use `await nextTick()` after programmatic reactive state changes
-- [ ] Use `await flushPromises()` for external async operations (API calls, timers)
-- [ ] Don't chain multiple `nextTick` calls - use `flushPromises` instead
-- [ ] Consider using `waitFor` from testing-library for polling assertions
-
-**Incorrect:**
-```javascript
-import { mount } from '@vue/test-utils'
-import SearchComponent from './SearchComponent.vue'
-
-// BAD: Not awaiting trigger - assertion runs before DOM updates
-test('search filters results', () => {
-  const wrapper = mount(SearchComponent)
-
-  wrapper.find('input').setValue('vue')  // Missing await!
-  wrapper.find('button').trigger('click')  // Missing await!
-
-  // This assertion likely fails - DOM hasn't updated yet
-  expect(wrapper.findAll('.result').length).toBe(3)
-})
-
-// BAD: Using nextTick for API calls
-test('loads data from API', async () => {
-  const wrapper = mount(DataLoader)
-
-  await nextTick()  // This won't wait for the API call!
-
-  // Assertion runs before fetch completes
-  expect(wrapper.find('.data').text()).toBe('Loaded data')
-})
-```
-
-**Correct:**
-```javascript
-import { mount, flushPromises } from '@vue/test-utils'
-import { nextTick } from 'vue'
-import SearchComponent from './SearchComponent.vue'
-import DataLoader from './DataLoader.vue'
-
-// CORRECT: Await trigger and setValue
-test('search filters results', async () => {
-  const wrapper = mount(SearchComponent)
-
-  await wrapper.find('input').setValue('vue')
-  await wrapper.find('button').trigger('click')
-
-  expect(wrapper.findAll('.result').length).toBe(3)
-})
-
-// CORRECT: Use flushPromises for API calls
-test('loads data from API', async () => {
-  const wrapper = mount(DataLoader)
-
-  // Wait for all pending promises to resolve
-  await flushPromises()
-
-  expect(wrapper.find('.data').text()).toBe('Loaded data')
-})
-```
-
-## When to Use Each Method
-
-### `await trigger()` / `await setValue()` - User Interactions
-```javascript
-// These methods return nextTick internally
-await wrapper.find('button').trigger('click')
-await wrapper.find('input').setValue('new value')
-await wrapper.find('form').trigger('submit')
-```
-
-### `await nextTick()` - Programmatic Reactive Updates
-```javascript
-import { nextTick } from 'vue'
-
-test('reflects programmatic state changes', async () => {
-  const wrapper = mount(Counter)
-
-  // Direct state modification (when testing with exposed internals)
-  wrapper.vm.count = 5
-
-  await nextTick()  // Wait for Vue to update DOM
-
-  expect(wrapper.find('.count').text()).toBe('5')
-})
-```
-
-### `await flushPromises()` - External Async Operations
-```javascript
-import { flushPromises } from '@vue/test-utils'
-
-test('displays fetched data', async () => {
-  const wrapper = mount(UserProfile, {
-    props: { userId: 1 }
-  })
-
-  // Wait for component's API call to complete
-  await flushPromises()
-
-  expect(wrapper.find('.username').text()).toBe('John')
-})
-
-// Sometimes you need multiple flushPromises for chained async operations
-test('processes data after fetch', async () => {
-  const wrapper = mount(DataProcessor)
-
-  await flushPromises()  // Wait for fetch
-  await flushPromises()  // Wait for processing triggered by fetch
-
-  expect(wrapper.find('.processed').exists()).toBe(true)
-})
-```
-
-## Common Pattern: Combining Methods
-```javascript
-test('submits form and shows success', async () => {
-  const wrapper = mount(ContactForm)
-
-  // Fill form (awaiting each interaction)
-  await wrapper.find('#name').setValue('John')
-  await wrapper.find('#email').setValue('john@example.com')
-
-  // Submit form
-  await wrapper.find('form').trigger('submit')
-
-  // Wait for API submission to complete
-  await flushPromises()
-
-  // Assert success state
-  expect(wrapper.find('.success-message').exists()).toBe(true)
-})
-```
-
-## Testing with MSW or Mock APIs
-```javascript
-import { flushPromises } from '@vue/test-utils'
-import { rest } from 'msw'
-import { setupServer } from 'msw/node'
-
-const server = setupServer(
-  rest.get('/api/user', (req, res, ctx) => {
-    return res(ctx.json({ name: 'John' }))
-  })
-)
-
-test('displays user data', async () => {
-  const wrapper = mount(UserCard)
-
-  // MSW might require multiple flushPromises
-  await flushPromises()
-  await flushPromises()
-
-  expect(wrapper.find('.name').text()).toBe('John')
-})
-```
-
-## Reference
-- [Vue Test Utils - Asynchronous Behavior](https://test-utils.vuejs.org/guide/advanced/async-suspense)
-- [Vue.js Testing Guide](https://vuejs.org/guide/scaling-up/testing)
diff --git a/.agents/skills/vue-testing-best-practices/reference/testing-browser-vs-node-runners.md b/.agents/skills/vue-testing-best-practices/reference/testing-browser-vs-node-runners.md
deleted file mode 100644
index a112a42..0000000
--- a/.agents/skills/vue-testing-best-practices/reference/testing-browser-vs-node-runners.md
+++ /dev/null
@@ -1,208 +0,0 @@
----
-title: Choose Browser-Based Runner for Style and DOM Event Testing
-impact: MEDIUM
-impactDescription: Node-based runners cannot test real CSS behavior, native DOM events, cookies, or computed styles
-type: capability
-tags: [vue3, testing, component-testing, vitest, browser, jsdom]
----
-
-# Choose Browser-Based Runner for Style and DOM Event Testing
-
-**Impact: MEDIUM** - Node-based test runners (Vitest with jsdom/happy-dom) simulate the DOM but cannot test real CSS rendering, native browser events, cookies, computed styles, or cross-browser behavior. Use browser-based runners when these matter.
-
-Use Vitest for most component tests (fast), but use Vitest Browser Mode when testing visual/DOM-dependent features.
-
-## Task Checklist
-
-- [ ] Use Vitest (node) for logic-focused component tests
-- [ ] Use Vitest Browser Mode for style-dependent tests
-- [ ] Use Vitest Browser Mode for native events (focus, drag, resize)
-- [ ] Use Vitest Browser Mode for cookies and computed CSS styles
-- [ ] Accept slower speed tradeoff for browser accuracy
-
-## When to Use Each Approach
-
-### Node-Based Runner (Vitest + happy-dom/jsdom)
-Best for:
-- Pure logic testing
-- State management
-- Event emission
-- Props/slots behavior
-- Most component interactions
-- Fast CI/CD pipelines
-
-```javascript
-// vitest.config.js
-export default defineConfig({
-  test: {
-    environment: 'happy-dom',  // or 'jsdom'
-  }
-})
-```
-
-```javascript
-// Fast but limited - fine for most tests
-test('button emits click event', async () => {
-  const wrapper = mount(Button)
-  await wrapper.trigger('click')
-  expect(wrapper.emitted('click')).toBeTruthy()
-})
-```
-
-### Vitest Browser Mode
-Required for:
-- CSS computed styles verification
-- CSS transitions/animations
-- Real focus/blur behavior
-- Drag and drop
-- Cookie operations
-- Viewport-dependent behavior
-- Cross-browser validation
-
-## Vitest Browser Mode Setup
-
-```bash
-npm install -D @vitest/browser playwright
-```
-
-```javascript
-// vitest.config.js
-import { defineConfig } from 'vitest/config'
-
-export default defineConfig({
-  test: {
-    browser: {
-      enabled: true,
-      name: 'chromium',
-      provider: 'playwright',
-    },
-  },
-})
-```
-
-```javascript
-// Button.browser.test.js
-import { render } from 'vitest-browser-vue'
-import Button from './Button.vue'
-
-test('has correct hover styling', async () => {
-  const { getByRole } = render(Button, { props: { label: 'Click me' } })
-
-  const button = getByRole('button')
-
-  // Check initial style
-  await expect.element(button).toHaveStyle({
-    backgroundColor: 'rgb(59, 130, 246)'  // blue
-  })
-})
-
-test('maintains focus after click', async () => {
-  const { getByRole } = render(Button)
-
-  const button = getByRole('button')
-  await button.click()
-
-  await expect.element(button).toHaveFocus()
-})
-```
-
-## Examples: What Each Runner Can/Cannot Test
-
-### Styles - Browser Required
-```javascript
-// Node runner: CANNOT verify actual CSS
-test('danger button has red background', () => {
-  const wrapper = mount(Button, { props: { variant: 'danger' } })
-  // This only checks class exists, not actual color
-  expect(wrapper.classes()).toContain('bg-red-500')
-})
-
-// Vitest Browser Mode: CAN verify computed styles
-test('danger button renders red', async () => {
-  const { getByRole } = render(Button, { props: { variant: 'danger' } })
-  await expect.element(getByRole('button')).toHaveStyle({
-    backgroundColor: 'rgb(239, 68, 68)'
-  })
-})
-```
-
-### Computed CSS Styles - Browser Required
-```javascript
-// Node runner: CANNOT get real computed styles
-test('button has correct padding', () => {
-  const wrapper = mount(Button)
-  // getComputedStyle returns empty/default values in jsdom
-  const style = window.getComputedStyle(wrapper.element)
-  // style.padding will be empty string, not actual computed value
-})
-
-// Vitest Browser Mode: Real computed styles
-test('button has correct padding', async () => {
-  const { getByRole } = render(Button)
-  const button = getByRole('button')
-
-  await expect.element(button).toHaveStyle({
-    padding: '12px 24px'
-  })
-})
-```
-
-### Native Events - Browser Required
-```javascript
-// Node runner: Synthetic events only
-test('handles drag and drop', async () => {
-  const wrapper = mount(DraggableList)
-  // trigger('dragstart') is synthetic - may not work as expected
-  await wrapper.find('.item').trigger('dragstart')
-})
-
-// Vitest Browser Mode: Real native events via userEvent
-import { userEvent } from '@vitest/browser/context'
-
-test('reorders items on drag', async () => {
-  const { getByTestId } = render(DraggableList)
-
-  const item = getByTestId('item-1')
-  const target = getByTestId('item-3')
-
-  await userEvent.dragAndDrop(item, target)
-
-  // Assert reordering
-})
-```
-
-## Recommended Testing Strategy
-
-```javascript
-// vitest.config.js - Separate test configurations
-
-export default defineConfig({
-  test: {
-    // Default: Node environment for speed
-    environment: 'happy-dom',
-
-    // Browser tests in separate directory
-    include: ['src/**/*.test.{js,ts}'],
-  },
-})
-
-// Run browser tests separately
-// npx vitest --browser.enabled
-```
-
-### Directory Structure
-```
-tests/
-├── unit/              # Fast node-based tests
-│   ├── Button.test.js
-│   └── useCounter.test.js
-├── component/         # Slower browser-based tests
-│   ├── Button.browser.test.js
-│   └── DragDrop.browser.test.js
-└── e2e/               # Full E2E tests (Playwright)
-    └── user-flow.spec.ts
-```
-
-## Reference
-- [Vue.js Testing - Component Testing](https://vuejs.org/guide/scaling-up/testing#component-testing)
-- [Vitest Browser Mode](https://vitest.dev/guide/browser.html)
diff --git a/.agents/skills/vue-testing-best-practices/reference/testing-component-blackbox-approach.md b/.agents/skills/vue-testing-best-practices/reference/testing-component-blackbox-approach.md
deleted file mode 100644
index e3a869c..0000000
--- a/.agents/skills/vue-testing-best-practices/reference/testing-component-blackbox-approach.md
+++ /dev/null
@@ -1,144 +0,0 @@
----
-title: Test Components Using Blackbox Approach - Focus on Behavior Not Implementation
-impact: HIGH
-impactDescription: Implementation-aware tests become brittle and break during refactoring, leading to high maintenance burden
-type: best-practice
-tags: [vue3, testing, component-testing, vitest, vue-test-utils, blackbox]
----
-
-# Test Components Using Blackbox Approach - Focus on Behavior Not Implementation
-
-**Impact: HIGH** - Tests that rely on implementation details (internal state, private methods, component structure) break during refactoring even when functionality remains correct. This leads to false negatives and high test maintenance burden.
-
-Follow Kent C. Dodds' testing philosophy: "The more your tests resemble how your software is used, the more confidence they can give you."
-
-## Task Checklist
-
-- [ ] Test what the component does, not how it does it
-- [ ] Query elements by user-visible attributes (text, role, testid)
-- [ ] Simulate user interactions (click, type) rather than calling methods directly
-- [ ] Assert on rendered output, emitted events, and visible state changes
-- [ ] Avoid accessing component internal state or private methods
-- [ ] Use data-testid attributes for elements without semantic meaning
-
-**Incorrect:**
-```javascript
-import { mount } from '@vue/test-utils'
-import Counter from './Counter.vue'
-
-// BAD: Testing implementation details
-test('counter increments', async () => {
-  const wrapper = mount(Counter)
-
-  // Accessing internal state directly
-  expect(wrapper.vm.count).toBe(0)
-
-  // Calling internal method instead of simulating user action
-  wrapper.vm.increment()
-
-  // Checking internal state instead of visible output
-  expect(wrapper.vm.count).toBe(1)
-})
-
-// BAD: Testing component structure
-test('has increment button', () => {
-  const wrapper = mount(Counter)
-
-  // Testing implementation detail - what if button becomes an anchor?
-  expect(wrapper.find('button').exists()).toBe(true)
-})
-```
-
-**Correct:**
-```javascript
-import { mount } from '@vue/test-utils'
-import Counter from './Counter.vue'
-
-// CORRECT: Testing behavior like a user would
-test('counter displays updated value after clicking increment', async () => {
-  const wrapper = mount(Counter, {
-    props: { max: 10 }
-  })
-
-  // Assert initial visible state
-  expect(wrapper.find('[data-testid="counter-value"]').text()).toContain('0')
-
-  // Simulate user action
-  await wrapper.find('[data-testid="increment-button"]').trigger('click')
-
-  // Assert visible result
-  expect(wrapper.find('[data-testid="counter-value"]').text()).toContain('1')
-})
-
-// CORRECT: Testing emitted events (public API)
-test('emits change event with new value when incremented', async () => {
-  const wrapper = mount(Counter)
-
-  await wrapper.find('[data-testid="increment-button"]').trigger('click')
-
-  expect(wrapper.emitted('change')).toHaveLength(1)
-  expect(wrapper.emitted('change')[0]).toEqual([1])
-})
-```
-
-## Using @testing-library/vue for Better Blackbox Tests
-
-```javascript
-import { render, screen, fireEvent } from '@testing-library/vue'
-import Counter from './Counter.vue'
-
-// Testing Library encourages accessible, user-centric queries
-test('increments counter on button click', async () => {
-  render(Counter)
-
-  // Query by role - how screen readers see it
-  const button = screen.getByRole('button', { name: /increment/i })
-  const display = screen.getByText('0')
-
-  await fireEvent.click(button)
-
-  expect(screen.getByText('1')).toBeInTheDocument()
-})
-```
-
-## What to Test vs What Not to Test
-
-### DO Test (Public Interface)
-```javascript
-// Props affect rendered output
-test('shows title from props', () => {
-  const wrapper = mount(Card, {
-    props: { title: 'Hello World' }
-  })
-  expect(wrapper.text()).toContain('Hello World')
-})
-
-// Slots render correctly
-test('renders slot content', () => {
-  const wrapper = mount(Card, {
-    slots: { default: '<p>Slot content</p>' }
-  })
-  expect(wrapper.text()).toContain('Slot content')
-})
-
-// Emitted events
-test('emits close event when X clicked', async () => {
-  const wrapper = mount(Modal)
-  await wrapper.find('[data-testid="close-button"]').trigger('click')
-  expect(wrapper.emitted('close')).toBeTruthy()
-})
-```
-
-### DON'T Test (Implementation Details)
-```javascript
-// Don't test internal computed properties
-// Don't test internal methods
-// Don't test component options/setup internals
-// Don't test that specific child components are rendered (unless critical)
-// Don't rely exclusively on snapshot tests for correctness
-```
-
-## Reference
-- [Vue.js Testing Guide](https://vuejs.org/guide/scaling-up/testing)
-- [Vue Test Utils - Testing Philosophy](https://test-utils.vuejs.org/guide/)
-- [Testing Library Guiding Principles](https://testing-library.com/docs/guiding-principles)
diff --git a/.agents/skills/vue-testing-best-practices/reference/testing-composables-helper-wrapper.md b/.agents/skills/vue-testing-best-practices/reference/testing-composables-helper-wrapper.md
deleted file mode 100644
index f6e4f07..0000000
--- a/.agents/skills/vue-testing-best-practices/reference/testing-composables-helper-wrapper.md
+++ /dev/null
@@ -1,238 +0,0 @@
----
-title: Test Complex Composables with Host Component Wrapper
-impact: MEDIUM
-impactDescription: Composables using lifecycle hooks or provide/inject fail when tested directly without a component context
-type: capability
-tags: [vue3, testing, composables, vitest, lifecycle-hooks, provide-inject]
----
-
-# Test Complex Composables with Host Component Wrapper
-
-**Impact: MEDIUM** - Composables that use Vue lifecycle hooks (`onMounted`, `onUnmounted`) or dependency injection (`inject`) require a component context to function. Testing them directly will cause errors or incorrect behavior.
-
-Simple composables using only reactivity APIs can be tested directly. Complex composables need a helper function that creates a host component context.
-
-## Task Checklist
-
-- [ ] Identify if composable uses lifecycle hooks or inject
-- [ ] For simple composables (refs, computed only): test directly
-- [ ] For complex composables: use `withSetup` helper pattern
-- [ ] Clean up by unmounting the test app after each test
-- [ ] Use `app.provide()` to mock injected dependencies
-
-**Simple Composable - Test Directly:**
-```javascript
-// composables/useCounter.js
-import { ref, computed } from 'vue'
-
-export function useCounter(initialValue = 0) {
-  const count = ref(initialValue)
-  const doubled = computed(() => count.value * 2)
-  const increment = () => count.value++
-
-  return { count, doubled, increment }
-}
-```
-
-```javascript
-// useCounter.test.js
-import { describe, it, expect } from 'vitest'
-import { useCounter } from './useCounter'
-
-// CORRECT: Simple composable can be tested directly
-describe('useCounter', () => {
-  it('initializes with default value', () => {
-    const { count } = useCounter()
-    expect(count.value).toBe(0)
-  })
-
-  it('increments count', () => {
-    const { count, increment } = useCounter()
-    increment()
-    expect(count.value).toBe(1)
-  })
-
-  it('computes doubled value', () => {
-    const { count, doubled, increment } = useCounter(5)
-    expect(doubled.value).toBe(10)
-    increment()
-    expect(doubled.value).toBe(12)
-  })
-})
-```
-
-**Complex Composable - Use Host Wrapper:**
-```javascript
-// composables/useFetch.js
-import { ref, onMounted, onUnmounted, inject } from 'vue'
-
-export function useFetch(url) {
-  const data = ref(null)
-  const error = ref(null)
-  const loading = ref(true)
-  let controller = null
-
-  // Uses inject - needs component context
-  const apiClient = inject('apiClient')
-
-  // Uses lifecycle hooks - needs component context
-  onMounted(async () => {
-    controller = new AbortController()
-    try {
-      const response = await apiClient.get(url, { signal: controller.signal })
-      data.value = response.data
-    } catch (e) {
-      if (e.name !== 'AbortError') error.value = e
-    } finally {
-      loading.value = false
-    }
-  })
-
-  onUnmounted(() => {
-    controller?.abort()
-  })
-
-  return { data, error, loading }
-}
-```
-
-```javascript
-// test-utils.js
-import { createApp } from 'vue'
-
-/**
- * Helper to test composables that need component context
- */
-export function withSetup(composable) {
-  let result
-
-  const app = createApp({
-    setup() {
-      result = composable()
-      // Return a render function to suppress warnings
-      return () => {}
-    }
-  })
-
-  app.mount(document.createElement('div'))
-
-  return [result, app]
-}
-```
-
-```javascript
-// useFetch.test.js
-import { describe, it, expect, vi, beforeEach, afterEach } from 'vitest'
-import { flushPromises } from '@vue/test-utils'
-import { withSetup } from './test-utils'
-import { useFetch } from './useFetch'
-
-describe('useFetch', () => {
-  let app
-  const mockApiClient = {
-    get: vi.fn()
-  }
-
-  afterEach(() => {
-    // IMPORTANT: Clean up to trigger onUnmounted
-    app?.unmount()
-  })
-
-  it('fetches data on mount', async () => {
-    mockApiClient.get.mockResolvedValue({ data: { id: 1, name: 'Test' } })
-
-    const [result, testApp] = withSetup(() => useFetch('/api/test'))
-    app = testApp
-
-    // Provide mocked dependency
-    app.provide('apiClient', mockApiClient)
-
-    // Wait for async operations
-    await flushPromises()
-
-    expect(result.data.value).toEqual({ id: 1, name: 'Test' })
-    expect(result.loading.value).toBe(false)
-    expect(result.error.value).toBeNull()
-  })
-
-  it('handles errors', async () => {
-    const testError = new Error('Network error')
-    mockApiClient.get.mockRejectedValue(testError)
-
-    const [result, testApp] = withSetup(() => useFetch('/api/test'))
-    app = testApp
-    app.provide('apiClient', mockApiClient)
-
-    await flushPromises()
-
-    expect(result.error.value).toBe(testError)
-    expect(result.data.value).toBeNull()
-  })
-})
-```
-
-## Enhanced withSetup Helper with Provide Support
-```javascript
-// test-utils.js
-export function withSetup(composable, options = {}) {
-  let result
-
-  const app = createApp({
-    setup() {
-      result = composable()
-      return () => {}
-    }
-  })
-
-  // Apply global provides before mounting
-  if (options.provide) {
-    Object.entries(options.provide).forEach(([key, value]) => {
-      app.provide(key, value)
-    })
-  }
-
-  app.mount(document.createElement('div'))
-
-  return [result, app]
-}
-
-// Usage
-const [result, app] = withSetup(() => useMyComposable(), {
-  provide: {
-    apiClient: mockApiClient,
-    currentUser: { id: 1, name: 'Test User' }
-  }
-})
-```
-
-## Testing with @vue/test-utils mount
-```javascript
-import { mount } from '@vue/test-utils'
-import { defineComponent } from 'vue'
-import { useFetch } from './useFetch'
-
-test('useFetch in component context', async () => {
-  const TestComponent = defineComponent({
-    setup() {
-      const { data, loading } = useFetch('/api/users')
-      return { data, loading }
-    },
-    template: '<div>{{ loading ? "Loading..." : data }}</div>'
-  })
-
-  const wrapper = mount(TestComponent, {
-    global: {
-      provide: {
-        apiClient: mockApiClient
-      }
-    }
-  })
-
-  await flushPromises()
-  expect(wrapper.text()).toContain('Test data')
-})
-```
-
-## Reference
-- [Vue.js Testing Guide - Testing Composables](https://vuejs.org/guide/scaling-up/testing#testing-composables)
-- [Vue Test Utils - Mounting Components](https://test-utils.vuejs.org/guide/)
diff --git a/.agents/skills/vue-testing-best-practices/reference/testing-e2e-playwright-recommended.md b/.agents/skills/vue-testing-best-practices/reference/testing-e2e-playwright-recommended.md
deleted file mode 100644
index 3df2ff0..0000000
--- a/.agents/skills/vue-testing-best-practices/reference/testing-e2e-playwright-recommended.md
+++ /dev/null
@@ -1,242 +0,0 @@
----
-title: Use Playwright for E2E Testing - Cross-Browser Support and Better DX
-impact: MEDIUM
-impactDescription: Cypress has browser limitations and some features require paid subscriptions
-type: best-practice
-tags: [vue3, testing, e2e, playwright, cypress, end-to-end]
----
-
-# Use Playwright for E2E Testing - Cross-Browser Support and Better DX
-
-**Impact: MEDIUM** - Playwright offers superior cross-browser testing (Chromium, WebKit, Firefox), excellent debugging tools, and is fully open source. Cypress has limitations with WebKit support and requires paid subscriptions for some features.
-
-Use Playwright for new E2E testing setups. Consider Cypress if team already has expertise or for its visual debugging UI.
-
-## Task Checklist
-
-- [ ] Install Playwright with browsers for your target platforms
-- [ ] Configure for Vue dev server integration
-- [ ] Set up projects for different browsers
-- [ ] Use locator strategies that match component test patterns
-- [ ] Configure CI for parallel test execution
-- [ ] Use trace and screenshot features for debugging
-
-## Quick Setup
-
-```bash
-# Install Playwright
-npm init playwright@latest
-
-# This will create:
-# - playwright.config.ts
-# - tests/ directory
-# - tests-examples/ directory
-```
-
-**playwright.config.ts:**
-```typescript
-import { defineConfig, devices } from '@playwright/test'
-
-export default defineConfig({
-  testDir: './e2e',
-  fullyParallel: true,
-  forbidOnly: !!process.env.CI,
-  retries: process.env.CI ? 2 : 0,
-  workers: process.env.CI ? 1 : undefined,
-  reporter: 'html',
-
-  use: {
-    // Base URL for navigation
-    baseURL: 'http://localhost:5173',
-    // Capture trace on first retry
-    trace: 'on-first-retry',
-    // Screenshot on failure
-    screenshot: 'only-on-failure',
-  },
-
-  projects: [
-    {
-      name: 'chromium',
-      use: { ...devices['Desktop Chrome'] },
-    },
-    {
-      name: 'firefox',
-      use: { ...devices['Desktop Firefox'] },
-    },
-    {
-      name: 'webkit',
-      use: { ...devices['Desktop Safari'] },
-    },
-    // Mobile viewports
-    {
-      name: 'Mobile Chrome',
-      use: { ...devices['Pixel 5'] },
-    },
-  ],
-
-  // Run local dev server before tests
-  webServer: {
-    command: 'npm run dev',
-    url: 'http://localhost:5173',
-    reuseExistingServer: !process.env.CI,
-  },
-})
-```
-
-## E2E Test Example
-
-```typescript
-// e2e/user-flow.spec.ts
-import { test, expect } from '@playwright/test'
-
-test.describe('User Authentication', () => {
-  test('user can log in and see dashboard', async ({ page }) => {
-    // Navigate to login
-    await page.goto('/login')
-
-    // Fill login form
-    await page.getByLabel('Email').fill('user@example.com')
-    await page.getByLabel('Password').fill('password123')
-    await page.getByRole('button', { name: 'Sign In' }).click()
-
-    // Verify redirect to dashboard
-    await expect(page).toHaveURL('/dashboard')
-    await expect(page.getByRole('heading', { name: 'Welcome' })).toBeVisible()
-  })
-
-  test('shows error for invalid credentials', async ({ page }) => {
-    await page.goto('/login')
-
-    await page.getByLabel('Email').fill('wrong@example.com')
-    await page.getByLabel('Password').fill('wrongpassword')
-    await page.getByRole('button', { name: 'Sign In' }).click()
-
-    await expect(page.getByRole('alert')).toContainText('Invalid credentials')
-    await expect(page).toHaveURL('/login')
-  })
-})
-```
-
-## Playwright vs Cypress Comparison
-
-| Feature | Playwright | Cypress |
-|---------|------------|---------|
-| Browsers | Chromium, Firefox, WebKit | Chromium, Firefox, Electron (WebKit experimental) |
-| Cross-browser | Full support | Limited |
-| Parallelization | Built-in | Requires Cypress Cloud |
-| Open source | Fully | Core only |
-| Mobile testing | Device emulation | Limited |
-| Debugging | Inspector, trace viewer | Time-travel UI |
-| API testing | Built-in | Plugin required |
-| Iframes | Full support | Limited |
-
-## Testing Vue Components with Data-Testid
-
-```typescript
-// e2e/product-list.spec.ts
-import { test, expect } from '@playwright/test'
-
-test('user can add product to cart', async ({ page }) => {
-  await page.goto('/products')
-
-  // Use data-testid for reliable selectors
-  await page.getByTestId('product-card').first().click()
-
-  // Verify product detail page
-  await expect(page.getByTestId('product-title')).toBeVisible()
-
-  // Add to cart
-  await page.getByTestId('add-to-cart-button').click()
-
-  // Verify cart updated
-  await expect(page.getByTestId('cart-count')).toHaveText('1')
-})
-```
-
-## Page Object Pattern for Vue Apps
-
-```typescript
-// e2e/pages/LoginPage.ts
-import { Page, Locator } from '@playwright/test'
-
-export class LoginPage {
-  readonly page: Page
-  readonly emailInput: Locator
-  readonly passwordInput: Locator
-  readonly submitButton: Locator
-  readonly errorMessage: Locator
-
-  constructor(page: Page) {
-    this.page = page
-    this.emailInput = page.getByLabel('Email')
-    this.passwordInput = page.getByLabel('Password')
-    this.submitButton = page.getByRole('button', { name: 'Sign In' })
-    this.errorMessage = page.getByRole('alert')
-  }
-
-  async goto() {
-    await this.page.goto('/login')
-  }
-
-  async login(email: string, password: string) {
-    await this.emailInput.fill(email)
-    await this.passwordInput.fill(password)
-    await this.submitButton.click()
-  }
-}
-```
-
-```typescript
-// e2e/auth.spec.ts
-import { test, expect } from '@playwright/test'
-import { LoginPage } from './pages/LoginPage'
-
-test('successful login', async ({ page }) => {
-  const loginPage = new LoginPage(page)
-  await loginPage.goto()
-  await loginPage.login('user@example.com', 'password123')
-
-  await expect(page).toHaveURL('/dashboard')
-})
-```
-
-## Visual Regression Testing
-
-```typescript
-test('homepage visual regression', async ({ page }) => {
-  await page.goto('/')
-
-  // Full page screenshot comparison
-  await expect(page).toHaveScreenshot('homepage.png')
-
-  // Element-specific screenshot
-  await expect(page.getByTestId('hero-section')).toHaveScreenshot('hero.png')
-})
-```
-
-## Running Tests
-
-```bash
-# Run all tests
-npx playwright test
-
-# Run in headed mode (see browser)
-npx playwright test --headed
-
-# Run specific file
-npx playwright test e2e/auth.spec.ts
-
-# Run in specific browser
-npx playwright test --project=chromium
-
-# Debug mode
-npx playwright test --debug
-
-# Generate test from actions
-npx playwright codegen localhost:5173
-```
-
-## Reference
-- [Playwright Documentation](https://playwright.dev/)
-- [Vue.js E2E Testing Recommendations](https://vuejs.org/guide/scaling-up/testing#e2e-testing)
-- [Playwright Best Practices](https://playwright.dev/docs/best-practices)
diff --git a/.agents/skills/vue-testing-best-practices/reference/testing-no-snapshot-only.md b/.agents/skills/vue-testing-best-practices/reference/testing-no-snapshot-only.md
deleted file mode 100644
index e44f437..0000000
--- a/.agents/skills/vue-testing-best-practices/reference/testing-no-snapshot-only.md
+++ /dev/null
@@ -1,197 +0,0 @@
----
-title: Avoid Snapshot-Only Tests - They Don't Prove Correctness
-impact: MEDIUM
-impactDescription: Snapshot tests verify structure but not functionality, leading to false confidence and brittle tests
-type: best-practice
-tags: [vue3, testing, snapshot, vitest, vue-test-utils, anti-pattern]
----
-
-# Avoid Snapshot-Only Tests - They Don't Prove Correctness
-
-**Impact: MEDIUM** - Snapshot tests only verify that HTML structure hasn't changed - they don't verify that the component works correctly. Relying exclusively on snapshots leads to false confidence and tests that break on any refactoring, even when functionality is preserved.
-
-Use snapshots sparingly for regression detection. Prefer behavioral assertions that test what the component does.
-
-## Task Checklist
-
-- [ ] Don't use snapshots as the only assertion for component behavior
-- [ ] Use snapshots for regression detection on stable UI components
-- [ ] Always pair snapshots with behavioral assertions
-- [ ] Keep snapshots small and focused (avoid full component snapshots)
-- [ ] Review snapshot diffs carefully - don't blindly update
-- [ ] Consider inline snapshots for small, critical structures
-
-**Incorrect:**
-```javascript
-import { mount } from '@vue/test-utils'
-import UserCard from './UserCard.vue'
-
-// BAD: Snapshot-only test proves nothing about functionality
-test('UserCard renders correctly', () => {
-  const wrapper = mount(UserCard, {
-    props: { user: { name: 'John', email: 'john@example.com' } }
-  })
-
-  expect(wrapper.html()).toMatchSnapshot()
-})
-
-// This test passes even if:
-// - The email isn't clickable
-// - The avatar doesn't load
-// - User actions are completely broken
-// - Accessibility is broken
-```
-
-**Correct:**
-```javascript
-import { mount } from '@vue/test-utils'
-import UserCard from './UserCard.vue'
-
-// CORRECT: Test actual behavior
-test('UserCard displays user information', () => {
-  const wrapper = mount(UserCard, {
-    props: { user: { name: 'John', email: 'john@example.com' } }
-  })
-
-  expect(wrapper.find('[data-testid="user-name"]').text()).toBe('John')
-  expect(wrapper.find('[data-testid="user-email"]').text()).toBe('john@example.com')
-})
-
-test('UserCard email link is clickable', async () => {
-  const wrapper = mount(UserCard, {
-    props: { user: { name: 'John', email: 'john@example.com' } }
-  })
-
-  const emailLink = wrapper.find('a[href^="mailto:"]')
-  expect(emailLink.exists()).toBe(true)
-  expect(emailLink.attributes('href')).toBe('mailto:john@example.com')
-})
-
-test('UserCard emits select event when clicked', async () => {
-  const wrapper = mount(UserCard, {
-    props: { user: { id: 1, name: 'John' } }
-  })
-
-  await wrapper.trigger('click')
-
-  expect(wrapper.emitted('select')).toBeTruthy()
-  expect(wrapper.emitted('select')[0]).toEqual([{ id: 1, name: 'John' }])
-})
-```
-
-## When Snapshots ARE Useful
-
-### Regression Detection for Stable Components
-```javascript
-// ACCEPTABLE: Snapshot as additional check, not the only check
-test('ErrorBoundary renders error message', () => {
-  const wrapper = mount(ErrorBoundary, {
-    props: { error: new Error('Something went wrong') }
-  })
-
-  // Primary assertions - verify behavior
-  expect(wrapper.find('.error-title').text()).toBe('Error')
-  expect(wrapper.find('.error-message').text()).toContain('Something went wrong')
-
-  // Secondary snapshot - catches unexpected structural changes
-  expect(wrapper.find('.error-container').html()).toMatchSnapshot()
-})
-```
-
-### Inline Snapshots for Small Structures
-```javascript
-// ACCEPTABLE: Inline snapshot for small, critical structure
-test('generates correct list markup', () => {
-  const wrapper = mount(ListItem, { props: { item: 'Test' } })
-
-  expect(wrapper.html()).toMatchInlineSnapshot(`
-    "<li class="list-item">Test</li>"
-  `)
-})
-```
-
-### Complex SVG or Icon Output
-```javascript
-// ACCEPTABLE: Snapshot for complex generated content
-test('renders correct chart SVG', () => {
-  const wrapper = mount(PieChart, {
-    props: { data: [30, 40, 30] }
-  })
-
-  // Verify key behavior
-  expect(wrapper.findAll('path').length).toBe(3)
-
-  // Snapshot for full SVG structure
-  expect(wrapper.find('svg').html()).toMatchSnapshot()
-})
-```
-
-## Better Alternatives to Snapshots
-
-### Test Specific Elements
-```javascript
-// Instead of snapshotting entire component
-test('renders product with all required fields', () => {
-  const wrapper = mount(ProductCard, {
-    props: { product: { name: 'Widget', price: 9.99, inStock: true } }
-  })
-
-  expect(wrapper.find('.product-name').text()).toBe('Widget')
-  expect(wrapper.find('.product-price').text()).toContain('9.99')
-  expect(wrapper.find('.in-stock-badge').exists()).toBe(true)
-})
-```
-
-### Test CSS Classes for Styling
-```javascript
-test('applies danger styling for errors', () => {
-  const wrapper = mount(Alert, {
-    props: { type: 'error', message: 'Failed!' }
-  })
-
-  expect(wrapper.classes()).toContain('alert-danger')
-  expect(wrapper.find('.alert-icon').classes()).toContain('icon-error')
-})
-```
-
-### Use Testing Library Queries
-```javascript
-import { render, screen } from '@testing-library/vue'
-
-test('form has accessible labels', () => {
-  render(LoginForm)
-
-  // Testing Library queries verify accessibility
-  expect(screen.getByLabelText('Email')).toBeInTheDocument()
-  expect(screen.getByLabelText('Password')).toBeInTheDocument()
-  expect(screen.getByRole('button', { name: 'Sign In' })).toBeInTheDocument()
-})
-```
-
-## Snapshot Anti-Patterns
-
-```javascript
-// ANTI-PATTERN: Giant component snapshot
-test('page renders', () => {
-  const wrapper = mount(EntirePageComponent)
-  expect(wrapper.html()).toMatchSnapshot()  // 500+ lines of HTML
-})
-
-// ANTI-PATTERN: Snapshot with dynamic content
-test('shows current date', () => {
-  const wrapper = mount(DateDisplay)
-  expect(wrapper.html()).toMatchSnapshot()  // Fails every day!
-})
-
-// ANTI-PATTERN: Snapshot after every test
-test('button works', async () => {
-  const wrapper = mount(Counter)
-  await wrapper.find('button').trigger('click')
-  expect(wrapper.html()).toMatchSnapshot()  // Redundant
-})
-```
-
-## Reference
-- [Vue.js Testing Guide - What Not to Test](https://vuejs.org/guide/scaling-up/testing)
-- [Effective Snapshot Testing](https://kentcdodds.com/blog/effective-snapshot-testing)
-- [Vitest Snapshot Testing](https://vitest.dev/guide/snapshot.html)
diff --git a/.agents/skills/vue-testing-best-practices/reference/testing-pinia-store-setup.md b/.agents/skills/vue-testing-best-practices/reference/testing-pinia-store-setup.md
deleted file mode 100644
index 3f8d440..0000000
--- a/.agents/skills/vue-testing-best-practices/reference/testing-pinia-store-setup.md
+++ /dev/null
@@ -1,228 +0,0 @@
----
-title: Configure Pinia Testing with createTestingPinia and setActivePinia
-impact: HIGH
-impactDescription: Missing Pinia configuration causes 'injection Symbol(pinia) not found' errors and failing tests
-type: gotcha
-tags: [vue3, testing, pinia, vitest, store, mocking, createTestingPinia]
----
-
-# Configure Pinia Testing with createTestingPinia and setActivePinia
-
-**Impact: HIGH** - Testing components or composables that use Pinia stores without proper configuration results in "[Vue warn]: injection Symbol(pinia) not found" errors. Tests will fail or behave unexpectedly.
-
-Use `@pinia/testing` package with `createTestingPinia` for component tests and `setActivePinia(createPinia())` for unit testing stores directly.
-
-## Task Checklist
-
-- [ ] Install `@pinia/testing` as a dev dependency
-- [ ] Use `createTestingPinia` in component tests with `global.plugins`
-- [ ] Use `setActivePinia(createPinia())` in `beforeEach` for store unit tests
-- [ ] Configure `createSpy: vi.fn` when NOT using `globals: true` in Vitest
-- [ ] Initialize store inside each test to get fresh state
-- [ ] Use `stubActions: false` when you need real action execution
-
-**Incorrect:**
-```javascript
-import { mount } from '@vue/test-utils'
-import UserProfile from './UserProfile.vue'
-
-// BAD: Missing Pinia - causes injection error
-test('displays user name', () => {
-  const wrapper = mount(UserProfile)  // ERROR: injection "Symbol(pinia)" not found
-  expect(wrapper.text()).toContain('John')
-})
-```
-
-```javascript
-import { useUserStore } from '@/stores/user'
-
-// BAD: No active Pinia instance
-test('user store actions', () => {
-  const store = useUserStore()  // ERROR: no active Pinia
-  store.login('john', 'password')
-})
-```
-
-**Correct - Component Testing:**
-```javascript
-import { mount } from '@vue/test-utils'
-import { createTestingPinia } from '@pinia/testing'
-import { vi } from 'vitest'
-import UserProfile from './UserProfile.vue'
-import { useUserStore } from '@/stores/user'
-
-// CORRECT: Provide testing pinia with stubbed actions
-test('displays user name', () => {
-  const wrapper = mount(UserProfile, {
-    global: {
-      plugins: [
-        createTestingPinia({
-          createSpy: vi.fn,  // Required if not using globals: true
-          initialState: {
-            user: { name: 'John', email: 'john@example.com' }
-          }
-        })
-      ]
-    }
-  })
-
-  expect(wrapper.text()).toContain('John')
-})
-
-// CORRECT: Test with stubbed actions (default behavior)
-test('calls logout action', async () => {
-  const wrapper = mount(UserProfile, {
-    global: {
-      plugins: [createTestingPinia({ createSpy: vi.fn })]
-    }
-  })
-
-  // Get store AFTER mounting with createTestingPinia
-  const store = useUserStore()
-
-  await wrapper.find('[data-testid="logout"]').trigger('click')
-
-  // Actions are stubbed and wrapped in spies
-  expect(store.logout).toHaveBeenCalled()
-})
-```
-
-**Correct - Store Unit Testing:**
-```javascript
-import { describe, it, expect, beforeEach, vi } from 'vitest'
-import { setActivePinia, createPinia } from 'pinia'
-import { useUserStore } from '@/stores/user'
-
-describe('User Store', () => {
-  beforeEach(() => {
-    // Create fresh Pinia instance for each test
-    setActivePinia(createPinia())
-  })
-
-  it('initializes with empty user', () => {
-    const store = useUserStore()
-    expect(store.user).toBeNull()
-    expect(store.isLoggedIn).toBe(false)
-  })
-
-  it('updates user on login', async () => {
-    const store = useUserStore()
-
-    // Real action executes - not stubbed
-    await store.login('john', 'password')
-
-    expect(store.user).toEqual({ name: 'John' })
-    expect(store.isLoggedIn).toBe(true)
-  })
-
-  it('clears user on logout', () => {
-    const store = useUserStore()
-    store.user = { name: 'John' }  // Set initial state
-
-    store.logout()
-
-    expect(store.user).toBeNull()
-  })
-})
-```
-
-## Testing with Real Actions vs Stubbed Actions
-
-```javascript
-import { createTestingPinia } from '@pinia/testing'
-
-// Stubbed actions (default) - for isolation
-const wrapper = mount(Component, {
-  global: {
-    plugins: [
-      createTestingPinia({
-        createSpy: vi.fn,
-        // stubActions: true (default) - actions are mocked
-      })
-    ]
-  }
-})
-
-// Real actions - for integration testing
-const wrapper = mount(Component, {
-  global: {
-    plugins: [
-      createTestingPinia({
-        createSpy: vi.fn,
-        stubActions: false  // Actions execute normally
-      })
-    ]
-  }
-})
-```
-
-## Mocking Specific Action Implementations
-
-```javascript
-import { mount } from '@vue/test-utils'
-import { createTestingPinia } from '@pinia/testing'
-import { vi } from 'vitest'
-import { useCartStore } from '@/stores/cart'
-
-test('handles checkout failure', async () => {
-  const wrapper = mount(Checkout, {
-    global: {
-      plugins: [createTestingPinia({ createSpy: vi.fn })]
-    }
-  })
-
-  const cartStore = useCartStore()
-
-  // Mock specific action behavior
-  cartStore.checkout.mockRejectedValue(new Error('Payment failed'))
-
-  await wrapper.find('[data-testid="checkout"]').trigger('click')
-  await flushPromises()
-
-  expect(wrapper.find('.error').text()).toContain('Payment failed')
-})
-```
-
-## Spying on Actions with vi.spyOn
-
-```javascript
-import { setActivePinia, createPinia } from 'pinia'
-import { vi } from 'vitest'
-import { useUserStore } from '@/stores/user'
-
-test('tracks action calls', async () => {
-  setActivePinia(createPinia())
-  const store = useUserStore()
-
-  const loginSpy = vi.spyOn(store, 'login')
-  loginSpy.mockResolvedValue({ success: true })
-
-  await store.login('john', 'password')
-
-  expect(loginSpy).toHaveBeenCalledWith('john', 'password')
-})
-```
-
-## Testing Store $subscribe
-
-```javascript
-import { setActivePinia, createPinia } from 'pinia'
-import { useUserStore } from '@/stores/user'
-
-test('subscription triggers on state change', () => {
-  setActivePinia(createPinia())
-  const store = useUserStore()
-
-  const callback = vi.fn()
-  store.$subscribe(callback)
-
-  store.user = { name: 'John' }
-
-  expect(callback).toHaveBeenCalled()
-})
-```
-
-## Reference
-- [Pinia Testing Guide](https://pinia.vuejs.org/cookbook/testing.html)
-- [@pinia/testing Package](https://www.npmjs.com/package/@pinia/testing)
-- [Vue Test Utils - Plugins](https://test-utils.vuejs.org/guide/advanced/plugins.html)
diff --git a/.agents/skills/vue-testing-best-practices/reference/testing-suspense-async-components.md b/.agents/skills/vue-testing-best-practices/reference/testing-suspense-async-components.md
deleted file mode 100644
index f935533..0000000
--- a/.agents/skills/vue-testing-best-practices/reference/testing-suspense-async-components.md
+++ /dev/null
@@ -1,229 +0,0 @@
----
-title: Wrap Async Setup Components in Suspense for Testing
-impact: HIGH
-impactDescription: Components with async setup() fail to render in tests without Suspense wrapper, causing cryptic errors
-type: gotcha
-tags: [vue3, testing, suspense, async-setup, vue-test-utils, vitest]
----
-
-# Wrap Async Setup Components in Suspense for Testing
-
-**Impact: HIGH** - Components using `async setup()` require a `<Suspense>` wrapper to function correctly. Testing them without Suspense causes the component to never render, leading to test failures and confusing errors.
-
-Create a test wrapper component with Suspense or use a `mountSuspense` helper function for testing async components.
-
-## Task Checklist
-
-- [ ] Identify components with async setup (uses `await` in `<script setup>` or `async setup()`)
-- [ ] Create a wrapper component with `<Suspense>` for testing
-- [ ] Use `flushPromises()` after mounting to wait for async resolution
-- [ ] Access the actual component via `findComponent()` for assertions
-- [ ] Consider using `@testing-library/vue` with caution (has Suspense issues)
-
-**Incorrect:**
-```javascript
-import { mount } from '@vue/test-utils'
-import AsyncUserProfile from './AsyncUserProfile.vue'
-
-// BAD: Async component without Suspense wrapper
-test('displays user data', async () => {
-  // This won't render - Vue expects Suspense wrapper for async setup
-  const wrapper = mount(AsyncUserProfile, {
-    props: { userId: 1 }
-  })
-
-  await flushPromises()
-
-  // This fails - component never rendered
-  expect(wrapper.find('.username').text()).toBe('John')
-})
-```
-
-**Correct - Manual Wrapper Component:**
-```javascript
-import { mount, flushPromises } from '@vue/test-utils'
-import { defineComponent, Suspense } from 'vue'
-import AsyncUserProfile from './AsyncUserProfile.vue'
-
-test('displays user data', async () => {
-  // Create wrapper component with Suspense
-  const TestWrapper = defineComponent({
-    components: { AsyncUserProfile },
-    template: `
-      <Suspense>
-        <AsyncUserProfile :user-id="1" />
-        <template #fallback>Loading...</template>
-      </Suspense>
-    `
-  })
-
-  const wrapper = mount(TestWrapper)
-
-  // Initially shows fallback
-  expect(wrapper.text()).toContain('Loading...')
-
-  // Wait for async setup to complete
-  await flushPromises()
-
-  // Find the actual component for detailed assertions
-  const profile = wrapper.findComponent(AsyncUserProfile)
-  expect(profile.find('.username').text()).toBe('John')
-})
-```
-
-**Correct - Reusable Helper Function:**
-```javascript
-// test-utils.js
-import { mount, flushPromises } from '@vue/test-utils'
-import { defineComponent, Suspense, h } from 'vue'
-
-export async function mountSuspense(component, options = {}) {
-  const { props, slots, ...mountOptions } = options
-
-  const wrapper = mount(
-    defineComponent({
-      render() {
-        return h(
-          Suspense,
-          null,
-          {
-            default: () => h(component, props, slots),
-            fallback: () => h('div', 'Loading...')
-          }
-        )
-      }
-    }),
-    mountOptions
-  )
-
-  // Wait for async component to resolve
-  await flushPromises()
-
-  return {
-    wrapper,
-    // Provide easy access to the actual component
-    component: wrapper.findComponent(component)
-  }
-}
-```
-
-```javascript
-// AsyncUserProfile.test.js
-import { mountSuspense } from './test-utils'
-import AsyncUserProfile from './AsyncUserProfile.vue'
-
-test('displays user data', async () => {
-  const { component } = await mountSuspense(AsyncUserProfile, {
-    props: { userId: 1 },
-    global: {
-      stubs: {
-        // Stub any child components if needed
-      }
-    }
-  })
-
-  expect(component.find('.username').text()).toBe('John')
-})
-
-test('handles errors gracefully', async () => {
-  const { component } = await mountSuspense(AsyncUserProfile, {
-    props: { userId: 'invalid' }
-  })
-
-  expect(component.find('.error').exists()).toBe(true)
-})
-```
-
-## Testing with onErrorCaptured
-
-```javascript
-import { mount, flushPromises } from '@vue/test-utils'
-import { defineComponent, Suspense, h, ref, onErrorCaptured } from 'vue'
-import AsyncComponent from './AsyncComponent.vue'
-
-test('catches async errors', async () => {
-  const capturedError = ref(null)
-
-  const TestWrapper = defineComponent({
-    setup() {
-      onErrorCaptured((error) => {
-        capturedError.value = error
-        return true // Prevent error propagation
-      })
-      return { capturedError }
-    },
-    render() {
-      return h(Suspense, null, {
-        default: () => h(AsyncComponent, { shouldFail: true }),
-        fallback: () => h('div', 'Loading...')
-      })
-    }
-  })
-
-  const wrapper = mount(TestWrapper)
-  await flushPromises()
-
-  expect(capturedError.value).toBeTruthy()
-  expect(capturedError.value.message).toContain('Failed to load')
-})
-```
-
-## Using with Nuxt's mountSuspended
-
-```javascript
-// If using Nuxt, use the built-in mountSuspended helper
-import { mountSuspended } from '@nuxt/test-utils/runtime'
-import AsyncPage from './AsyncPage.vue'
-
-test('renders async page', async () => {
-  const wrapper = await mountSuspended(AsyncPage, {
-    props: { id: 1 }
-  })
-
-  expect(wrapper.find('h1').text()).toBe('Page Title')
-})
-```
-
-## Important Caveats
-
-### @testing-library/vue Limitation
-```javascript
-// CAUTION: @testing-library/vue has issues with Suspense
-// Use @vue/test-utils for async components instead
-
-// If you must use Testing Library, create manual wrapper:
-import { render, waitFor } from '@testing-library/vue'
-
-test('async component with testing library', async () => {
-  const TestWrapper = {
-    template: `
-      <Suspense>
-        <AsyncComponent />
-      </Suspense>
-    `,
-    components: { AsyncComponent }
-  }
-
-  const { getByText } = render(TestWrapper)
-
-  await waitFor(() => {
-    expect(getByText('Loaded content')).toBeInTheDocument()
-  })
-})
-```
-
-### Accessing Component Instance
-```javascript
-test('access vm on async component', async () => {
-  const { wrapper, component } = await mountSuspense(AsyncComponent)
-
-  // The wrapper.vm is the Suspense wrapper - not useful
-  // Use component.vm for the actual async component
-  expect(component.vm.someData).toBe('value')
-})
-```
-
-## Reference
-- [Vue Test Utils - Async Suspense](https://test-utils.vuejs.org/guide/advanced/async-suspense)
-- [Vue.js Suspense Documentation](https://vuejs.org/guide/built-ins/suspense.html)
-- [Testing Library Vue Suspense Issue](https://github.com/testing-library/vue-testing-library/issues/230)
diff --git a/.agents/skills/vue-testing-best-practices/reference/testing-vitest-recommended-for-vue.md b/.agents/skills/vue-testing-best-practices/reference/testing-vitest-recommended-for-vue.md
deleted file mode 100644
index 7962890..0000000
--- a/.agents/skills/vue-testing-best-practices/reference/testing-vitest-recommended-for-vue.md
+++ /dev/null
@@ -1,204 +0,0 @@
----
-title: Use Vitest for Vue 3 Testing - Recommended by Vue Team
-impact: MEDIUM
-impactDescription: Using Jest or other runners with Vite projects requires complex configuration and causes slower test runs
-type: best-practice
-tags: [vue3, testing, vitest, vite, configuration, setup]
----
-
-# Use Vitest for Vue 3 Testing - Recommended by Vue Team
-
-**Impact: MEDIUM** - Vitest is created and maintained by Vue/Vite team members and shares the same configuration and transform pipeline as Vite. Using Jest or other test runners with Vite-based projects requires additional configuration and can result in slower test execution and compatibility issues.
-
-Use Vitest for new Vue 3 projects. Only consider Jest if migrating an existing test suite.
-
-## Task Checklist
-
-- [ ] Install Vitest and related packages for Vue testing
-- [ ] Configure vitest in vite.config.js or vitest.config.js
-- [ ] Set up proper test environment (happy-dom or jsdom)
-- [ ] Add test scripts to package.json
-- [ ] Configure globals if desired for cleaner test syntax
-- [ ] Use @vue/test-utils for component mounting
-
-## Quick Setup
-
-```bash
-# Install required packages
-npm install -D vitest @vue/test-utils happy-dom
-# or with jsdom
-npm install -D vitest @vue/test-utils jsdom
-```
-
-**vite.config.js:**
-```javascript
-import { defineConfig } from 'vite'
-import vue from '@vitejs/plugin-vue'
-
-export default defineConfig({
-  plugins: [vue()],
-  test: {
-    // Enable global test APIs (describe, it, expect)
-    globals: true,
-    // Use happy-dom for faster tests (or 'jsdom' for better compatibility)
-    environment: 'happy-dom',
-    // Optional: Setup files for global configuration
-    setupFiles: ['./src/test/setup.js']
-  }
-})
-```
-
-**package.json:**
-```json
-{
-  "scripts": {
-    "test": "vitest",
-    "test:run": "vitest run",
-    "test:coverage": "vitest run --coverage"
-  }
-}
-```
-
-**tsconfig.json (if using TypeScript):**
-```json
-{
-  "compilerOptions": {
-    "types": ["vitest/globals"]
-  }
-}
-```
-
-## Test File Example
-
-```javascript
-// src/components/Counter.test.js
-import { describe, it, expect, beforeEach } from 'vitest'  // optional with globals: true
-import { mount } from '@vue/test-utils'
-import Counter from './Counter.vue'
-
-describe('Counter', () => {
-  let wrapper
-
-  beforeEach(() => {
-    wrapper = mount(Counter)
-  })
-
-  it('renders initial count', () => {
-    expect(wrapper.find('[data-testid="count"]').text()).toBe('0')
-  })
-
-  it('increments when button clicked', async () => {
-    await wrapper.find('[data-testid="increment"]').trigger('click')
-    expect(wrapper.find('[data-testid="count"]').text()).toBe('1')
-  })
-})
-```
-
-## Vitest vs Jest Comparison
-
-| Feature | Vitest | Jest |
-|---------|--------|------|
-| Vite Integration | Native | Requires config |
-| Speed | Very fast (ESM native) | Slower with Vite |
-| Watch Mode | Excellent | Good |
-| Vue SFC Support | Works with Vite | Needs vue-jest |
-| Config Sharing | Same as vite.config | Separate |
-| API | Jest-compatible | Standard |
-
-## Using with Testing Library
-
-```bash
-npm install -D @testing-library/vue @testing-library/jest-dom
-```
-
-```javascript
-// src/test/setup.js
-import { expect } from 'vitest'
-import * as matchers from '@testing-library/jest-dom/matchers'
-
-expect.extend(matchers)
-```
-
-```javascript
-// Component.test.js
-import { render, screen, fireEvent } from '@testing-library/vue'
-import UserCard from './UserCard.vue'
-
-test('displays user name', () => {
-  render(UserCard, {
-    props: { name: 'John Doe' }
-  })
-
-  expect(screen.getByText('John Doe')).toBeInTheDocument()
-})
-```
-
-## Advanced Configuration
-
-```javascript
-// vitest.config.js (separate file if preferred)
-import { defineConfig } from 'vitest/config'
-import vue from '@vitejs/plugin-vue'
-
-export default defineConfig({
-  plugins: [vue()],
-  test: {
-    globals: true,
-    environment: 'happy-dom',
-    include: ['**/*.{test,spec}.{js,ts,jsx,tsx}'],
-    exclude: ['node_modules', 'dist', 'e2e'],
-    coverage: {
-      provider: 'v8',
-      reporter: ['text', 'json', 'html'],
-      exclude: ['node_modules', 'test']
-    },
-    // Helpful for debugging
-    reporters: ['verbose'],
-    // Run tests in sequence in CI
-    poolOptions: {
-      threads: {
-        singleThread: process.env.CI === 'true'
-      }
-    }
-  }
-})
-```
-
-## Common Patterns
-
-### Mocking Modules
-```javascript
-import { vi } from 'vitest'
-
-vi.mock('@/api/users', () => ({
-  fetchUser: vi.fn().mockResolvedValue({ name: 'John' })
-}))
-```
-
-### Testing with Fake Timers
-```javascript
-import { vi, beforeEach, afterEach } from 'vitest'
-
-beforeEach(() => {
-  vi.useFakeTimers()
-})
-
-afterEach(() => {
-  vi.restoreAllMocks()
-})
-
-test('debounced search', async () => {
-  const wrapper = mount(SearchBox)
-  await wrapper.find('input').setValue('vue')
-
-  vi.advanceTimersByTime(300)
-  await flushPromises()
-
-  expect(wrapper.emitted('search')).toBeTruthy()
-})
-```
-
-## Reference
-- [Vitest Documentation](https://vitest.dev/)
-- [Vue.js Testing Guide](https://vuejs.org/guide/scaling-up/testing)
-- [Vue Test Utils](https://test-utils.vuejs.org/)
diff --git a/.claude/settings.json b/.claude/settings.json
deleted file mode 100644
index 655c47b..0000000
--- a/.claude/settings.json
+++ /dev/null
@@ -1,28 +0,0 @@
-{
-  "hooks": {
-    "PostToolUse": [
-      {
-        "matcher": "Edit|Write|Bash",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "code-review-graph update --skip-flows",
-            "timeout": 30
-          }
-        ]
-      }
-    ],
-    "SessionStart": [
-      {
-        "matcher": "",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "code-review-graph status",
-            "timeout": 10
-          }
-        ]
-      }
-    ]
-  }
-}
diff --git a/.claude/skills/debug-issue.md b/.claude/skills/debug-issue.md
deleted file mode 100644
index ef1b38a..0000000
--- a/.claude/skills/debug-issue.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-name: Debug Issue
-description: Systematically debug issues using graph-powered code navigation
----
-
-## Debug Issue
-
-Use the knowledge graph to systematically trace and debug issues.
-
-### Steps
-
-1. Use `semantic_search_nodes` to find code related to the issue.
-2. Use `query_graph` with `callers_of` and `callees_of` to trace call chains.
-3. Use `get_flow` to see full execution paths through suspected areas.
-4. Run `detect_changes` to check if recent changes caused the issue.
-5. Use `get_impact_radius` on suspected files to see what else is affected.
-
-### Tips
-
-- Check both callers and callees to understand the full context.
-- Look at affected flows to find the entry point that triggers the bug.
-- Recent changes are the most common source of new issues.
-
-## Token Efficiency Rules
-- ALWAYS start with `get_minimal_context(task="<your task>")` before any other graph tool.
-- Use `detail_level="minimal"` on all calls. Only escalate to "standard" when minimal is insufficient.
-- Target: complete any review/debug/refactor task in ≤5 tool calls and ≤800 total output tokens.
diff --git a/.claude/skills/explore-codebase.md b/.claude/skills/explore-codebase.md
deleted file mode 100644
index dc7ad10..0000000
--- a/.claude/skills/explore-codebase.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-name: Explore Codebase
-description: Navigate and understand codebase structure using the knowledge graph
----
-
-## Explore Codebase
-
-Use the code-review-graph MCP tools to explore and understand the codebase.
-
-### Steps
-
-1. Run `list_graph_stats` to see overall codebase metrics.
-2. Run `get_architecture_overview` for high-level community structure.
-3. Use `list_communities` to find major modules, then `get_community` for details.
-4. Use `semantic_search_nodes` to find specific functions or classes.
-5. Use `query_graph` with patterns like `callers_of`, `callees_of`, `imports_of` to trace relationships.
-6. Use `list_flows` and `get_flow` to understand execution paths.
-
-### Tips
-
-- Start broad (stats, architecture) then narrow down to specific areas.
-- Use `children_of` on a file to see all its functions and classes.
-- Use `find_large_functions` to identify complex code.
-
-## Token Efficiency Rules
-- ALWAYS start with `get_minimal_context(task="<your task>")` before any other graph tool.
-- Use `detail_level="minimal"` on all calls. Only escalate to "standard" when minimal is insufficient.
-- Target: complete any review/debug/refactor task in ≤5 tool calls and ≤800 total output tokens.
diff --git a/.claude/skills/playwright b/.claude/skills/playwright
deleted file mode 120000
index 30b62c1..0000000
--- a/.claude/skills/playwright
+++ /dev/null
@@ -1 +0,0 @@
-../../.agents/skills/playwright
\ No newline at end of file
diff --git a/.claude/skills/playwright-generate-test b/.claude/skills/playwright-generate-test
deleted file mode 120000
index 64a345b..0000000
--- a/.claude/skills/playwright-generate-test
+++ /dev/null
@@ -1 +0,0 @@
-../../.agents/skills/playwright-generate-test
\ No newline at end of file
diff --git a/.claude/skills/refactor-safely.md b/.claude/skills/refactor-safely.md
deleted file mode 100644
index cf84420..0000000
--- a/.claude/skills/refactor-safely.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-name: Refactor Safely
-description: Plan and execute safe refactoring using dependency analysis
----
-
-## Refactor Safely
-
-Use the knowledge graph to plan and execute refactoring with confidence.
-
-### Steps
-
-1. Use `refactor_tool` with mode="suggest" for community-driven refactoring suggestions.
-2. Use `refactor_tool` with mode="dead_code" to find unreferenced code.
-3. For renames, use `refactor_tool` with mode="rename" to preview all affected locations.
-4. Use `apply_refactor_tool` with the refactor_id to apply renames.
-5. After changes, run `detect_changes` to verify the refactoring impact.
-
-### Safety Checks
-
-- Always preview before applying (rename mode gives you an edit list).
-- Check `get_impact_radius` before major refactors.
-- Use `get_affected_flows` to ensure no critical paths are broken.
-- Run `find_large_functions` to identify decomposition targets.
-
-## Token Efficiency Rules
-- ALWAYS start with `get_minimal_context(task="<your task>")` before any other graph tool.
-- Use `detail_level="minimal"` on all calls. Only escalate to "standard" when minimal is insufficient.
-- Target: complete any review/debug/refactor task in ≤5 tool calls and ≤800 total output tokens.
diff --git a/.claude/skills/review-changes.md b/.claude/skills/review-changes.md
deleted file mode 100644
index 6bb3558..0000000
--- a/.claude/skills/review-changes.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-name: Review Changes
-description: Perform a structured code review using change detection and impact
----
-
-## Review Changes
-
-Perform a thorough, risk-aware code review using the knowledge graph.
-
-### Steps
-
-1. Run `detect_changes` to get risk-scored change analysis.
-2. Run `get_affected_flows` to find impacted execution paths.
-3. For each high-risk function, run `query_graph` with pattern="tests_for" to check test coverage.
-4. Run `get_impact_radius` to understand the blast radius.
-5. For any untested changes, suggest specific test cases.
-
-### Output Format
-
-Provide findings grouped by risk level (high/medium/low) with:
-- What changed and why it matters
-- Test coverage status
-- Suggested improvements
-- Overall merge recommendation
-
-## Token Efficiency Rules
-- ALWAYS start with `get_minimal_context(task="<your task>")` before any other graph tool.
-- Use `detail_level="minimal"` on all calls. Only escalate to "standard" when minimal is insufficient.
-- Target: complete any review/debug/refactor task in ≤5 tool calls and ≤800 total output tokens.
diff --git a/.claude/skills/vue-best-practices b/.claude/skills/vue-best-practices
deleted file mode 120000
index b0f9603..0000000
--- a/.claude/skills/vue-best-practices
+++ /dev/null
@@ -1 +0,0 @@
-../../.agents/skills/vue-best-practices
\ No newline at end of file
diff --git a/.claude/skills/vue-router-best-practices b/.claude/skills/vue-router-best-practices
deleted file mode 120000
index 8d29235..0000000
--- a/.claude/skills/vue-router-best-practices
+++ /dev/null
@@ -1 +0,0 @@
-../../.agents/skills/vue-router-best-practices
\ No newline at end of file
diff --git a/.claude/skills/vue-testing-best-practices b/.claude/skills/vue-testing-best-practices
deleted file mode 120000
index d3f0d13..0000000
--- a/.claude/skills/vue-testing-best-practices
+++ /dev/null
@@ -1 +0,0 @@
-../../.agents/skills/vue-testing-best-practices
\ No newline at end of file
diff --git a/.gitignore b/.gitignore
index d16aca4..7bd0777 100644
--- a/.gitignore
+++ b/.gitignore
@@ -40,3 +40,7 @@ output/playwright/
 .code-review-graph/
 
 .codex/config.toml
+.agents/
+.claude/
+.ruler/
+.playwright/
diff --git a/.playwright/cli.config.json b/.playwright/cli.config.json
deleted file mode 100644
index 587f73e..0000000
--- a/.playwright/cli.config.json
+++ /dev/null
@@ -1,8 +0,0 @@
-{
-  "browser": {
-    "browserName": "chromium",
-    "launchOptions": {
-      "channel": "chromium"
-    }
-  }
-}
\ No newline at end of file
diff --git a/.ruler/AGENTS.md b/.ruler/AGENTS.md
deleted file mode 100644
index de60f7b..0000000
--- a/.ruler/AGENTS.md
+++ /dev/null
@@ -1,4 +0,0 @@
-# Project Rules
-
-## General
-- Follow the existing code style and patterns.
diff --git a/.ruler/ruler.toml b/.ruler/ruler.toml
deleted file mode 100644
index 9377f5a..0000000
--- a/.ruler/ruler.toml
+++ /dev/null
@@ -1,11 +0,0 @@
-# For a complete example, see: https://okigu.com/ruler#complete-example
-
-# List of agents to configure
-default_agents = ["copilot", "claude", "trae"]
-
-[mcp_servers.vuetify]
-url = "https://mcp.vuetifyjs.com/mcp"
-
-# https://github.com/vuetifyjs/mcp#authentication
-# [mcp_servers.vuetify.headers]
-# Authorization = "Bearer <YOUR_API_KEY>"