vue-expert-js

Standardize Vue 3 workflows with vanilla JavaScript and JSDoc type safety.

9|2|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/stephanj/claude-code-collections --skill vue-expert-js-stephanj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vue-expert-js
Source: https://github.com/stephanj/claude-code-collections/tree/main/skills/vue-expert-js
Command: npx skills add https://github.com/stephanj/claude-code-collections --skill vue-expert-js-stephanj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of maintaining type safety and modern architectural standards in Vue 3 projects that utilize vanilla JavaScript instead of TypeScript.

Core Features & Use Cases

  • JSDoc Type Safety: Provides standardized patterns for documenting props, emits, and composables using JSDoc.
  • Composition API Patterns: Offers best practices for building modular, reusable logic with the Composition API.
  • Use Case: Use this when migrating legacy Vue 2 codebases to Vue 3 or when working on projects where the team prefers JavaScript but requires the structural benefits of type documentation.

Quick Start

Invoke the vue-expert-js skill to generate a new composable with JSDoc annotations for a user authentication module.

Frequently Asked Questions about vue-expert-js

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain type safety in Vue 3 without using TypeScript?

You can maintain type safety in Vue 3 without TypeScript by using JSDoc annotations to document props, emits, and composables. This approach provides standardized type documentation and structural benefits while keeping your codebase in vanilla JavaScript.

What is the best way to structure Vue 3 Composition API patterns in JavaScript?

The best way to structure Composition API patterns in JavaScript is to follow predefined reference guides that enforce modular code architecture. This ensures reusable logic and consistent component structures across non-TypeScript Vue 3 projects.

Can I migrate a legacy Vue 2 codebase to Vue 3 while keeping vanilla JavaScript?

Yes, you can migrate legacy Vue 2 codebases to Vue 3 while keeping vanilla JavaScript. Standardized workflows facilitate implementing Composition API patterns and Pinia state management without requiring a TypeScript migration.

How do I document Pinia state management and composables using JSDoc?

Document Pinia state management and composables using JSDoc by applying standardized annotation patterns for props, emits, and modular logic. This enforces consistent documentation and type checking within your Vue 3 JavaScript environment.

When should I not use TypeScript for a Vue 3 application?

You should avoid TypeScript for Vue 3 when your team prefers vanilla JavaScript but still requires structural type documentation benefits. Using JSDoc with predefined architectural constraints provides type safety without TypeScript's overhead.