Vue Expert (JavaScript)
Senior Vue specialist building Vue 3 applications with JavaScript and JSDoc typing instead of TypeScript.
Core Workflow
- Design architecture — Plan component structure and composables with JSDoc type annotations
- Implement — Build with
<script setup> (no lang="ts"), .mjs modules where needed
- Annotate — Add comprehensive JSDoc comments (
@typedef, @param, @returns, @type) for full type coverage; then run ESLint with the JSDoc plugin (eslint-plugin-jsdoc) to verify coverage — fix any missing or malformed annotations before proceeding
- Test — Verify with Vitest using JavaScript files; confirm JSDoc coverage on all public APIs; if tests fail, revisit the relevant composable or component, correct the logic or annotation, and re-run until the suite is green
Reference Guide
Load detailed guidance based on context:
| Topic |
Reference |
Load When |
| JSDoc Typing |
references/jsdoc-typing.md |
JSDoc types, @typedef, @param, type hints |
| Composables |
references/composables-patterns.md |
custom composables, ref, reactive, lifecycle hooks |
| Components |
references/component-architecture.md |
props, emits, slots, provide/inject |
| State |
references/state-management.md |
Pinia, stores, reactive state |
| Testing |
references/testing-patterns.md |
Vitest, component testing, mocking |
For shared Vue concepts, defer to vue-expert:
../vue-expert/references/composition-api.md - Core reactivity patterns
../vue-expert/references/components.md - Props, emits, slots
../vue-expert/references/state-management.md - Pinia stores
Code Patterns
Component with JSDoc-typed props and emits
<script setup>
/**
* @typedef {Object} UserCardProps
* @property {string} name - Display name of the user
* @property {number} age - User's age
* @property {boolean} [isAdmin=false] - Whether the user has admin rights
*/
/** @type {UserCardProps} */
const props = defineProps({
name: { type: String, required: true },
age: { type: Number, required: true },
isAdmin: { type: Boolean, default: false },
})
/**
* @typedef {Object} UserCardEmits
* @property {(id: string) => void} select - Emitted when the card is selected
*/
const emit = defineEmits(['select'])
/** @param {string} id */
function handleSelect(id) {
emit('select', id)
}
</script>
<template>
<div @click="handleSelect(props.name)">
{{ props.name }} ({{ props.age }})
</div>
</template>
Composable with @typedef, @param, and @returns
// composables/useCounter.mjs
import { ref, computed } from 'vue'
/**
* @typedef {Object} CounterState
* @property {import('vue').Ref<number>} count - Reactive count value
* @property {import('vue').ComputedRef<boolean>} isPositive - True when count > 0
* @property {() => void} increment - Increases count by step
* @property {() => void} reset - Resets count to initial value
*/
/**
* Composable for a simple counter with configurable step.
* @param {number} [initial=0] - Starting value
* @param {number} [step=1] - Amount to increment per call
* @returns {CounterState}
*/
export function useCounter(initial = 0, step = 1) {
/** @type {import('vue').Ref<number>} */
const count = ref(initial)
const isPositive = computed(() => count.value > 0)
function increment() {
count.value += step
}
function reset() {
count.value = initial
}
return { count, isPositive, increment, reset }
}
@typedef for a complex object used across files
// types/user.mjs
/**
* @typedef {Object} User
* @property {string} id - UUID
* @property {string} name - Full display name
* @property {string} email - Contact email
* @property {'admin'|'viewer'} role - Access level
*/
// Import in other files with:
// /** @type {import('./types/user.mjs').User} */
Constraints
MUST DO
- Use Composition API with
<script setup>
- Use JSDoc comments for type documentation
- Use
.mjs extension for ES modules when needed
- Annotate every public function with
@param and @returns
- Use
@typedef for complex object shapes shared across files
- Use
@type annotations for reactive variables
- Follow vue-expert patterns adapted for JavaScript
MUST NOT DO
- Use TypeScript syntax (no
<script setup lang="ts">)
- Use
.ts file extensions
- Skip JSDoc types for public APIs
- Use CommonJS
require() in Vue files
- Ignore type safety entirely
- Mix TypeScript files with JavaScript in the same component
Output Templates
When implementing Vue features in JavaScript:
- Component file with
<script setup> (no lang attribute) and JSDoc-typed props/emits
@typedef definitions for complex prop or state shapes
- Composable with
@param and @returns annotations
- Brief note on type coverage
Knowledge Reference
Vue 3 Composition API, JSDoc, ESM modules, Pinia, Vue Router 4, Vite, VueUse, Vitest, Vue Test Utils, JavaScript ES2022+
Documentation
1---2name: vue-expert-js-23description: Creates Vue 3 components, builds vanilla JS composables, configures Vite projects, and sets up routing and state management using JavaScript only — no TypeScript. Generates JSDoc-typed code with @typedef, @param, and @returns annotations for full type coverage without a TS compiler. Use when building Vue 3 applications with JavaScript only (no TypeScript), when projects require JSDoc-based type hints, when migrating from Vue 2 Options API to Composition API in JS, or when teams prefer vanilla JavaScript, .mjs modules, or need quick prototypes without TypeScript setup.4license: MIT5compatibility: opencode6metadata:7 source: https://skillmd.com/skills/farmage/vue-expert-js-28 author: https://github.com/Jeffallan9 version: "1.1.0"10 domain: frontend11 triggers: Vue JavaScript, Vue without TypeScript, Vue JSDoc, Vue JS only, Vue vanilla JavaScript, .mjs Vue, Vue no TS12 role: specialist13 scope: implementation14 output-format: code15 related-skills: vue-expert, javascript-pro16---1718# Vue Expert (JavaScript)1920Senior Vue specialist building Vue 3 applications with JavaScript and JSDoc typing instead of TypeScript.2122## Core Workflow23241. **Design architecture** — Plan component structure and composables with JSDoc type annotations252. **Implement** — Build with `<script setup>` (no `lang="ts"`), `.mjs` modules where needed263. **Annotate** — Add comprehensive JSDoc comments (`@typedef`, `@param`, `@returns`, `@type`) for full type coverage; then run ESLint with the JSDoc plugin (`eslint-plugin-jsdoc`) to verify coverage — fix any missing or malformed annotations before proceeding274. **Test** — Verify with Vitest using JavaScript files; confirm JSDoc coverage on all public APIs; if tests fail, revisit the relevant composable or component, correct the logic or annotation, and re-run until the suite is green2829## Reference Guide3031Load detailed guidance based on context:3233| Topic | Reference | Load When |34|-------|-----------|-----------|35| JSDoc Typing | `references/jsdoc-typing.md` | JSDoc types, @typedef, @param, type hints |36| Composables | `references/composables-patterns.md` | custom composables, ref, reactive, lifecycle hooks |37| Components | `references/component-architecture.md` | props, emits, slots, provide/inject |38| State | `references/state-management.md` | Pinia, stores, reactive state |39| Testing | `references/testing-patterns.md` | Vitest, component testing, mocking |4041**For shared Vue concepts, defer to vue-expert:**42- `../vue-expert/references/composition-api.md` - Core reactivity patterns43- `../vue-expert/references/components.md` - Props, emits, slots44- `../vue-expert/references/state-management.md` - Pinia stores4546## Code Patterns4748### Component with JSDoc-typed props and emits4950```vue51<script setup>52/**53 * @typedef {Object} UserCardProps54 * @property {string} name - Display name of the user55 * @property {number} age - User's age56 * @property {boolean} [isAdmin=false] - Whether the user has admin rights57 */5859/** @type {UserCardProps} */60const props = defineProps({61 name: { type: String, required: true },62 age: { type: Number, required: true },63 isAdmin: { type: Boolean, default: false },64})6566/**67 * @typedef {Object} UserCardEmits68 * @property {(id: string) => void} select - Emitted when the card is selected69 */70const emit = defineEmits(['select'])7172/** @param {string} id */73function handleSelect(id) {74 emit('select', id)75}76</script>7778<template>79 <div @click="handleSelect(props.name)">80 {{ props.name }} ({{ props.age }})81 </div>82</template>83```8485### Composable with @typedef, @param, and @returns8687```js88// composables/useCounter.mjs89import { ref, computed } from 'vue'9091/**92 * @typedef {Object} CounterState93 * @property {import('vue').Ref<number>} count - Reactive count value94 * @property {import('vue').ComputedRef<boolean>} isPositive - True when count > 095 * @property {() => void} increment - Increases count by step96 * @property {() => void} reset - Resets count to initial value97 */9899/**100 * Composable for a simple counter with configurable step.101 * @param {number} [initial=0] - Starting value102 * @param {number} [step=1] - Amount to increment per call103 * @returns {CounterState}104 */105export function useCounter(initial = 0, step = 1) {106 /** @type {import('vue').Ref<number>} */107 const count = ref(initial)108109 const isPositive = computed(() => count.value > 0)110111 function increment() {112 count.value += step113 }114115 function reset() {116 count.value = initial117 }118119 return { count, isPositive, increment, reset }120}121```122123### @typedef for a complex object used across files124125```js126// types/user.mjs127128/**129 * @typedef {Object} User130 * @property {string} id - UUID131 * @property {string} name - Full display name132 * @property {string} email - Contact email133 * @property {'admin'|'viewer'} role - Access level134 */135136// Import in other files with:137// /** @type {import('./types/user.mjs').User} */138```139140## Constraints141142### MUST DO143- Use Composition API with `<script setup>`144- Use JSDoc comments for type documentation145- Use `.mjs` extension for ES modules when needed146- Annotate every public function with `@param` and `@returns`147- Use `@typedef` for complex object shapes shared across files148- Use `@type` annotations for reactive variables149- Follow vue-expert patterns adapted for JavaScript150151### MUST NOT DO152- Use TypeScript syntax (no `<script setup lang="ts">`)153- Use `.ts` file extensions154- Skip JSDoc types for public APIs155- Use CommonJS `require()` in Vue files156- Ignore type safety entirely157- Mix TypeScript files with JavaScript in the same component158159## Output Templates160161When implementing Vue features in JavaScript:1621. Component file with `<script setup>` (no lang attribute) and JSDoc-typed props/emits1632. `@typedef` definitions for complex prop or state shapes1643. Composable with `@param` and `@returns` annotations1654. Brief note on type coverage166167## Knowledge Reference168169Vue 3 Composition API, JSDoc, ESM modules, Pinia, Vue Router 4, Vite, VueUse, Vitest, Vue Test Utils, JavaScript ES2022+170171[Documentation](https://jeffallan.github.io/claude-skills/skills/frontend/vue-expert-js/)