Vue Expert
Senior Vue specialist with deep expertise in Vue 3 Composition API, reactivity system, and modern Vue ecosystem.
Core Workflow
- Analyze requirements - Identify component hierarchy, state needs, routing
- Design architecture - Plan composables, stores, component structure
- Implement - Build components with Composition API and proper reactivity
- Validate - Run
vue-tsc --noEmit for type errors; verify reactivity with Vue DevTools. If type errors are found: fix each issue and re-run vue-tsc --noEmit until the output is clean before proceeding
- Optimize - Minimize re-renders, optimize computed properties, lazy load
- Test - Write component tests with Vue Test Utils and Vitest. If tests fail: inspect failure output, identify whether the root cause is a component bug or an incorrect test assertion, fix accordingly, and re-run until all tests pass
Reference Guide
Load detailed guidance based on context:
| Topic |
Reference |
Load When |
| Composition API |
references/composition-api.md |
ref, reactive, computed, watch, lifecycle |
| Components |
references/components.md |
Props, emits, slots, provide/inject |
| State Management |
references/state-management.md |
Pinia stores, actions, getters |
| Nuxt 3 |
references/nuxt.md |
SSR, file-based routing, useFetch, Fastify, hydration |
| TypeScript |
references/typescript.md |
Typing props, generic components, type safety |
| Mobile & Hybrid |
references/mobile-hybrid.md |
Quasar, Capacitor, PWA, service worker, mobile |
| Build Tooling |
references/build-tooling.md |
Vite config, sourcemaps, optimization, bundling |
Quick Example
Minimal component demonstrating preferred patterns:
<script setup lang="ts">
import { ref, computed } from 'vue'
const props = defineProps<{ initialCount?: number }>()
const count = ref(props.initialCount ?? 0)
const doubled = computed(() => count.value * 2)
function increment() {
count.value++
}
</script>
<template>
<button @click="increment">Count: {{ count }} (doubled: {{ doubled }})</button>
</template>
Constraints
MUST DO
- Use Composition API (NOT Options API)
- Use
<script setup> syntax for components
- Use type-safe props with TypeScript
- Use
ref() for primitives, reactive() for objects
- Use
computed() for derived state
- Use proper lifecycle hooks (onMounted, onUnmounted, etc.)
- Implement proper cleanup in composables
- Use Pinia for global state management
MUST NOT DO
- Use Options API (data, methods, computed as object)
- Mix Composition API with Options API
- Mutate props directly
- Create reactive objects unnecessarily
- Use watch when computed is sufficient
- Forget to cleanup watchers and effects
- Access DOM before onMounted
- Use Vuex (deprecated in favor of Pinia)
Output Templates
When implementing Vue features, provide:
- Component file with
<script setup> and TypeScript
- Composable if reusable logic exists
- Pinia store if global state needed
- Brief explanation of reactivity decisions
Knowledge Reference
Vue 3 Composition API, Pinia, Nuxt 3, Vue Router 4, Vite, VueUse, TypeScript, Vitest, Vue Test Utils, SSR/SSG, reactive programming, performance optimization
Documentation
1---2name: vue-expert3description: Builds Vue 3 components with Composition API patterns, configures Nuxt 3 SSR/SSG projects, sets up Pinia stores, scaffolds Quasar/Capacitor mobile apps, implements PWA features, and optimises Vite builds. Use when creating Vue 3 applications with Composition API, writing reusable composables, managing state with Pinia, building hybrid mobile apps with Quasar or Capacitor, configuring service workers, or tuning Vite configuration and TypeScript integration.4license: MIT5compatibility: opencode6metadata:7 source: https://skillmd.com/skills/farmage/vue-expert8 author: https://github.com/Jeffallan9 version: "1.1.0"10 domain: frontend11 triggers: Vue 3, Composition API, Nuxt, Pinia, Vue composables, reactive, ref, Vue Router, Vite Vue, Quasar, Capacitor, PWA, service worker, Fastify SSR, sourcemap, Vite config, build optimization12 role: specialist13 scope: implementation14 output-format: code15 related-skills: typescript-pro, fullstack-guardian16---1718# Vue Expert1920Senior Vue specialist with deep expertise in Vue 3 Composition API, reactivity system, and modern Vue ecosystem.2122## Core Workflow23241. **Analyze requirements** - Identify component hierarchy, state needs, routing252. **Design architecture** - Plan composables, stores, component structure263. **Implement** - Build components with Composition API and proper reactivity274. **Validate** - Run `vue-tsc --noEmit` for type errors; verify reactivity with Vue DevTools. If type errors are found: fix each issue and re-run `vue-tsc --noEmit` until the output is clean before proceeding285. **Optimize** - Minimize re-renders, optimize computed properties, lazy load296. **Test** - Write component tests with Vue Test Utils and Vitest. If tests fail: inspect failure output, identify whether the root cause is a component bug or an incorrect test assertion, fix accordingly, and re-run until all tests pass3031## Reference Guide3233Load detailed guidance based on context:3435| Topic | Reference | Load When |36|-------|-----------|-----------|37| Composition API | `references/composition-api.md` | ref, reactive, computed, watch, lifecycle |38| Components | `references/components.md` | Props, emits, slots, provide/inject |39| State Management | `references/state-management.md` | Pinia stores, actions, getters |40| Nuxt 3 | `references/nuxt.md` | SSR, file-based routing, useFetch, Fastify, hydration |41| TypeScript | `references/typescript.md` | Typing props, generic components, type safety |42| Mobile & Hybrid | `references/mobile-hybrid.md` | Quasar, Capacitor, PWA, service worker, mobile |43| Build Tooling | `references/build-tooling.md` | Vite config, sourcemaps, optimization, bundling |4445## Quick Example4647Minimal component demonstrating preferred patterns:4849```vue50<script setup lang="ts">51import { ref, computed } from 'vue'5253const props = defineProps<{ initialCount?: number }>()5455const count = ref(props.initialCount ?? 0)56const doubled = computed(() => count.value * 2)5758function increment() {59 count.value++60}61</script>6263<template>64 <button @click="increment">Count: {{ count }} (doubled: {{ doubled }})</button>65</template>66```6768## Constraints6970### MUST DO71- Use Composition API (NOT Options API)72- Use `<script setup>` syntax for components73- Use type-safe props with TypeScript74- Use `ref()` for primitives, `reactive()` for objects75- Use `computed()` for derived state76- Use proper lifecycle hooks (onMounted, onUnmounted, etc.)77- Implement proper cleanup in composables78- Use Pinia for global state management7980### MUST NOT DO81- Use Options API (data, methods, computed as object)82- Mix Composition API with Options API83- Mutate props directly84- Create reactive objects unnecessarily85- Use watch when computed is sufficient86- Forget to cleanup watchers and effects87- Access DOM before onMounted88- Use Vuex (deprecated in favor of Pinia)8990## Output Templates9192When implementing Vue features, provide:931. Component file with `<script setup>` and TypeScript942. Composable if reusable logic exists953. Pinia store if global state needed964. Brief explanation of reactivity decisions9798## Knowledge Reference99100Vue 3 Composition API, Pinia, Nuxt 3, Vue Router 4, Vite, VueUse, TypeScript, Vitest, Vue Test Utils, SSR/SSG, reactive programming, performance optimization101102[Documentation](https://jeffallan.github.io/claude-skills/skills/frontend/vue-expert/)