agentleFS
santiago-migonisantiago-migoni/claude-skills/skills/vue-expert/SKILL.md

vue-expert

Skill0 starsChanged 11 months agoMITView on GitHub

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.

20 other projects use a version of this, 11 of them edited.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. 9 are common, 1 is distinctive, and 4 are very specific to this project.

  • 9

    Common

    Most of the 15 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Validate: - Run vue-tsc --noEmit for type errors.

    line 26
  2. Distinctive:

    Test: - Write component tests with Vue Test Utils and Vitest.

    line 28
  3. Common:

    Use Composition API (NOT Options API)

    line 70
  4. Very specific:

    Use <script setup> syntax for components

    line 71
  5. Common:

    Use type-safe props with TypeScript

    line 72
  6. Very specific:

    Use ref() for primitives, reactive() for objects

    line 73
  7. Very specific:

    Use computed() for derived state

    line 74
  8. Common:

    Use proper lifecycle hooks (onMounted, onUnmounted, etc.)

    line 75
  9. Common:

    Use Pinia for global state management

    line 77
  10. Common:

    Use Options API (data, methods, computed as object)

    line 80
  11. Common:

    Create reactive objects unnecessarily

    line 83
  12. Common:

    Use watch when computed is sufficient

    line 84
  13. Common:

    Use Vuex (deprecated in favor of Pinia)

    line 87
  14. Common:

    When implementing Vue features, provide:

    line 91

“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

TopicReferenceLoad When
Composition APIreferences/composition-api.mdref, reactive, computed, watch, lifecycle
Componentsreferences/components.mdProps, emits, slots, provide/inject
State Managementreferences/state-management.mdPinia stores, actions, getters
Nuxt 3references/nuxt.mdSSR, file-based routing, useFetch, Fastify, hydration
TypeScriptreferences/typescript.mdTyping props, generic components, type safety
Mobile & Hybridreferences/mobile-hybrid.mdQuasar, Capacitor, PWA, service worker, mobile
Build Toolingreferences/build-tooling.mdVite 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:

  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 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

Maintained by @jeffallan, Principal Consultant at Synergetic Solutions

Documentation

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.