agentleFS
Domenico-Tenace-Open-LabsDomenico-Tenace-Open-Labs/web-dev-agent/skills/vue-expert/SKILL.md

vue-expert

Skill3 starsChanged 14 days agoMITView on GitHub

Vue 3 / Nuxt conventions — Composition API with <script setup>, typed props/emits, composables, Pinia stores, Vite build config. Load when the project uses Vue 3 (.vue SFC, nuxt.config.*, Pinia stores); also Quasar/Capacitor mobile and PWA/service-worker work.

19 other projects use a version of this, 14 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use shopify-expert, rails-expert and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • JeffallanSkill

    shopify-expert

    Builds and debugs Shopify themes (.liquid files, theme.json, sections), develops custom Shopify apps (shopify.app.toml, OAuth, webhooks), and implements Storefront API integrations for headless storefronts. Use when building or customizing Shopify themes, creating Hydrogen or custom React storefronts, developing Shopify apps, implementing checkout UI extensions or Shopify Functions, optimizing performance, or integrating third-party services. Invoke for Liquid templating, Storefront API, app development, checkout customization, Shopify Plus features, App Bridge, Polaris, or Shopify CLI workflows.

    Also in 7 projects that use this

  • JeffallanSkill

    rails-expert

    Rails 7+ specialist that optimizes Active Record queries with includes/eager_load, implements Turbo Frames and Turbo Streams for partial page updates, configures Action Cable for WebSocket connections, sets up Sidekiq workers for background job processing, and writes comprehensive RSpec test suites. Use when building Rails 7+ web applications with Hotwire, real-time features, or background job processing. Invoke for Active Record optimization, Turbo Frames/Streams, Action Cable, Sidekiq, RSpec Rails.

    Also in 11 projects that use this

  • +10 more from Jeffallan

The file

We split this skill into the rules it gives an agent

7 rules. 4 are common, 2 are distinctive, and 1 is very specific to this project.

  • 4

    Common

    Most of the 18 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    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 type errors.

    line 18
  2. Common:

    Use Composition API (NOT Options API)

    line 63
  3. Common:

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

    line 74
  4. Common:

    Create reactive objects unnecessarily

    line 77
  5. Distinctive:

    Use watch when computed suffices

    line 78
  6. Distinctive:

    Use Vuex (deprecated — Pinia)

    line 81
  7. Common:

    When implementing Vue features, provide:

    line 85

“Common” is measured: kept by at least 6 in 10 of the 18 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, deep expertise Vue 3 Composition API, reactivity system, modern Vue ecosystem. Derived from Jeffallan's vue-expert skill (MIT).

Styling-agnostic: pair with skill bulma-expert when project uses Bulma — no duplication.

Core Workflow

  1. Analyze requirements - component hierarchy, state needs, routing
  2. Design architecture - plan composables, stores, component structure
  3. Implement - build components with Composition API + proper reactivity
  4. Validate - run vue-tsc --noEmit type errors; verify reactivity Vue DevTools. Errors → fix each, re-run until clean
  5. Optimize - minimize re-renders, optimize computed, lazy load
  6. Test - component tests Vue Test Utils + Vitest. Fail → find root cause (component bug vs wrong assertion), fix, re-run until 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
  • Type-safe props with TypeScript
  • ref() primitives, reactive() objects
  • computed() derived state
  • Proper lifecycle hooks (onMounted, onUnmounted, etc.)
  • Proper cleanup in composables
  • Pinia for global state

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 suffices
  • Forget cleanup of watchers/effects
  • Access DOM before onMounted
  • Use Vuex (deprecated — Pinia)

Output Templates

When implementing Vue features, provide:

  1. Component file <script setup> + 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

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.