What problem does it solve? When adding or refactoring Vue 3 pages, components, Composables, or Pinia stores, teams often lack clear boundaries between UI, domain state, service requests, and routing, leading to tangled code and unclear contracts. This Skill produces structured design output before implementation begins. ## Core Features & Use Cases - Component Contract Definition: Defines Props, Emits, empty states, error states, and accessibility behavior for each component. - Layered Design Output: Produces L1 design cards for small features and L2 design plus API contracts for large features. - Boundary Clarification: Separates UI, domain state, service requests, and routing responsibilities, then hands off to vue-testing and vue-code-review for verification. - Use Case: When planning a new dashboard page with a Pinia store and several child components, use this Skill to generate the component boundaries, Props/Emits contracts, state ownership, file plan, and acceptance criteria before writing code. ## Quick Start Ask the AI to design a new Vue 3 feature, for example: design the components, Composable, and Pinia store for a user profile page with Props/Emits contracts and acceptance criteria.