
Vue Expert
Implement Vue 3 Composition API apps, Nuxt SSR/SSG, Pinia state, and Quasar/Capacitor mobile or PWA surfaces with typed, validated builds.
Overview
vue-expert is an agent skill for the Build phase that implements Vue 3 Composition API applications, Nuxt 3 projects, Pinia state, and Quasar/Capacitor mobile or PWA features with vue-tsc validation.
Install
npx skills add https://github.com/jeffallan/claude-skills --skill vue-expertWhat is this skill?
- Vue 3 Composition API: components, composables, ref/reactive patterns, Vue Router
- Nuxt 3 SSR/SSG scaffolding and Fastify SSR integration called out in triggers
- Pinia store design plus Quasar and Capacitor for hybrid mobile apps
- PWA: service worker implementation and build optimization via Vite config and sourcemaps
- 4-step Core Workflow ending in vue-tsc --noEmit validation loop until type-clean
- 4-step Core Workflow: analyze, design architecture, implement, validate
- Metadata version 1.1.0 with MIT license
Adoption & trust: 2.6k installs on skills.sh; 9.7k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are building or refactoring a Vue 3 app and need correct reactivity, store layout, and Vite/Nuxt config without trial-and-error Composition API mistakes.
Who is it for?
Indie SaaS or mobile-hybrid products on Vue 3, Nuxt 3, Pinia, Quasar, or Capacitor with TypeScript discipline.
Skip if: Greenfield projects explicitly committed to React, Svelte, or static HTML with no Vue stack.
When should I use this skill?
Vue 3, Composition API, Nuxt, Pinia, Vue composables, Quasar, Capacitor, PWA, service worker, Vite config, or build optimization for Vue.
What do I get? / Deliverables
You get structured Vue 3/Nuxt implementation with a validated, type-clean codebase ready for ship-phase testing.
- Vue 3 components and composables
- Pinia store modules
- Nuxt/Vite/PWA configuration patches
Recommended Skills
Journey fit
Canonical shelf is Build because the skill is an implementation specialist for Vue ecosystem code, not idea discovery or launch distribution. Frontend subphase covers components, composables, routing, Vite tuning, and hybrid mobile shells.
How it compares
Skill-package frontend specialist—not a generic linter; use instead of ad-hoc Vue snippets without composable architecture or vue-tsc gates.
Common Questions / FAQ
Who is vue-expert for?
Solo builders and small teams implementing Vue 3 apps with Composition API, Nuxt, Pinia, or Quasar/Capacitor who want agent-guided architecture and typing discipline.
When should I use vue-expert?
During Build/frontend when creating components and composables, configuring Nuxt SSR/SSG, setting up Pinia, adding PWA service workers, or optimizing Vite Vue builds.
Is vue-expert safe to install?
Review the Security Audits panel on this Prism page; the skill emits code and may suggest shell commands like vue-tsc—audit before running in CI or production repos.
SKILL.md
READMESKILL.md - Vue Expert
# Vue Expert Senior Vue specialist with deep expertise in Vue 3 Composition API, reactivity system, and modern Vue ecosystem. ## Core Workflow 1. **Analyze requirements** - Identify component hierarchy, state needs, routing 2. **Design architecture** - Plan composables, stores, component structure 3. **Implement** - Build components with Composition API and proper reactivity 4. **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 5. **Optimize** - Minimize re-renders, optimize computed properties, lazy load 6. **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: ```vue <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: 1. Component file with `<script setup>` and TypeScript 2. Composable if reusable logic exists 3. Pinia store if global state needed 4. Brief explanation of reactivit