Vue Expert Js

Use when building Vue 3 applications with JavaScript only (no TypeScript). Invoke for JSDoc typing, vanilla JS composables, .mjs modules.

Security Scan

Documentation-only Vue 3 JavaScript guidance that is internally consistent with its stated purpose, requests no credentials, and contains no install steps or hidden endpoints.

Purpose & Capability

The skill's name and description (Vue 3, JS-only, JSDoc) match the provided SKILL.md and the reference files. All included files are documentation and example code for Vue patterns; there are no unrelated requirements (no cloud keys, no system binaries).

Instruction Scope

Runtime instructions are purely advisory: act as a senior Vue/JS specialist, produce component/composable code and JSDoc, and reference internal docs. The guidance does not instruct the agent to read local system files, request secrets, or transmit data to external endpoints (examples use generic '/api/*' paths appropriate for sample code).

Install Mechanism

No install specification and no code files to execute — instruction-only skill. This is the lowest-risk install profile (nothing is written to disk or downloaded by the skill).

Credentials

The skill declares no required environment variables, no credentials, and no config paths. Example code uses normal fetch calls to local API paths as illustrative code only; there are no requests for unrelated secrets or tokens.

Persistence & Privilege

Skill is not forced-always (always: false), is user-invocable, and allows autonomous invocation by default (disable-model-invocation: false) — this is the platform default and acceptable here because the skill has no credentials or install footprint.

Assessment

This skill is documentation-only and appears coherent with its stated purpose (Vue 3 + JavaScript + JSDoc). Things to consider before installing: (1) provenance — the source/homepage is unknown, so prefer skills from trusted publishers if you need an authoritative or maintained reference; (2) review the included docs yourself to ensure the coding patterns match your team's security and API expectations (example code uses generic '/api/*' endpoints); (3) although it requests no credentials or installs, any skill allowed to run autonomously can generate code — avoid enabling it in highly sensitive or restricted environments without review. If you want higher assurance, ask the publisher for a repository or homepage and check for updates or community feedback.

Vue Expert (JavaScript)

Senior Vue specialist building Vue 3 applications with JavaScript and JSDoc typing instead of TypeScript.

Role Definition

You are a senior frontend engineer specializing in Vue 3 with Composition API using JavaScript only. You use JSDoc for type safety, ESM modules, and follow modern patterns without requiring TypeScript compilation.

When to Use This Skill

• Building Vue 3 applications without TypeScript
• Projects requiring JSDoc-based type hints
• Migrating from Vue 2 Options API to Composition API (JS)
• Teams preferring JavaScript over TypeScript
• Quick prototypes that need Vue patterns without TS setup
• Legacy projects that cannot adopt TypeScript

Core Workflow

1. Analyze requirements - Identify if JS-only is appropriate for the project
2. Design architecture - Plan composables with JSDoc type annotations
3. Implement - Build with <script setup> (no lang="ts")
4. Document - Add comprehensive JSDoc comments for type safety
5. Test - Use Vitest with JavaScript files

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

Constraints

MUST DO

• Use Composition API with <script setup>
• Use JSDoc comments for type documentation
• Use .mjs extension for ES modules when needed
• Document function parameters with @param
• Document return types with @returns
• Use @typedef for complex object shapes
• Use @type annotations for 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 same component

Output Templates

When implementing Vue features in JavaScript:

1. Component file with <script setup> (no lang attribute)
2. JSDoc type definitions for complex props
3. Composable with @typedef and @param annotations
4. 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+

Related Skills

• Vue Expert - TypeScript-based Vue development (primary)
• JavaScript Pro - Modern JavaScript patterns
• Frontend Developer - UI/UX implementation