What problem does it solve? Vue 3 projects often lack a consistent testing strategy, leading to untested component interactions, fragile composable state logic, and regressions in critical user paths. This Skill provides a risk-based testing approach that matches verification depth to change impact. ## Core Features & Use Cases - Risk-Based Test Selection: Choose minimal sufficient verification by level—L0 runs affected tests or records manual verification, L1 covers component interactions, composable state, and API success/failure paths, L2 adds contract integration and key E2E flows. - Proper Mocking Boundaries: Mock only external boundaries (HTTP, routing, time) while keeping business logic under test real, avoiding false confidence from over-mocked tests. - Use Case: After modifying a Vue 3 composable that manages form state, apply L1 verification to test the composable's state transitions and the component's interaction with it, mocking only the HTTP layer. ## Quick Start Write Vitest tests for my Vue 3 component and its composable, mocking only the HTTP and router boundaries.