vue-expert-js

Create Vue 3 components and composables with JSDoc type annotations.

Updated Jun 16, 2026
One-click install
npx skills add https://github.com/Design-System-ET/genexus-dev-opencode --skill vue-expert-js-design-system-et
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vue-expert-js
Source: https://github.com/Design-System-ET/genexus-dev-opencode/tree/main/skills/vue-expert-js
Command: npx skills add https://github.com/Design-System-ET/genexus-dev-opencode --skill vue-expert-js-design-system-et

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the friction of building modern Vue 3 applications when TypeScript is not an option, providing a structured way to maintain type safety and documentation using standard JSDoc annotations.

Core Features & Use Cases

  • JSDoc-Driven Typing: Enforces strict type coverage for props, emits, and composables using @typedef and @param annotations.
  • Composition API Workflow: Provides patterns for <script setup> components and .mjs modules without requiring a TS compiler.
  • Use Case: Ideal for teams migrating from Vue 2 to Vue 3 who want to leverage the Composition API while maintaining a vanilla JavaScript codebase with robust IDE type hints.

Quick Start

Use the vue-expert-js skill to generate a new Vue 3 component with JSDoc-typed props and a corresponding composable for state management.

Frequently Asked Questions about vue-expert-js

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

FAQPage Schema
How do I build Vue 3 components with the Composition API using plain JavaScript instead of TypeScript?

You can build Vue 3 components using plain JavaScript by leveraging JSDoc annotations for type safety. This approach provides IDE type hints and enforces strict type coverage for props and emits without needing a TypeScript compiler.

What is the best way to maintain type safety in a Vue 3 project avoiding TypeScript?

The best way to maintain type safety without TypeScript is using JSDoc-driven typing. By applying @typedef and @param annotations, you achieve full type coverage and standardized documentation for public APIs in your Vue 3 application.

Can I use JSDoc annotations to type composables in a Vue 3 script setup?

Yes, you can use JSDoc annotations to type composables in a Vue 3 script setup. This enables strict type checking and modular ESM structure for .mjs modules, ensuring robust IDE support while keeping a vanilla JavaScript codebase.

Does Vue 3 support automated linting verification for JSDoc type annotations?

Vue 3 supports automated linting verification for JSDoc type annotations through specialized workflows. This enforces strict type coverage for props, emits, and composables, ensuring your vanilla JavaScript codebase meets standardized documentation requirements.

Why should I use JSDoc instead of TypeScript for a Vue 2 to Vue 3 migration?

Using JSDoc instead of TypeScript during a Vue 2 to Vue 3 migration lets you adopt the Composition API while keeping your existing vanilla JavaScript codebase. It provides robust IDE type hints and enforces type safety without introducing a TS compiler dependency.

How do I generate Vue 3 composables with JSDoc-typed state management?

You generate Vue 3 composables with JSDoc-typed state management by creating .mjs modules with @typedef and @param annotations. This approach provides full type coverage and standardized documentation for public APIs without requiring a TypeScript compiler.