agentleFS
Sign inStart free
zackleconzacklecon/claude-skills/skills/vue-expert-js/SKILL.md

vue-expert-js

Skill3 starsChanged 10 months agoMITView on GitHub

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

9 other projects use a version of this, 9 of them edited.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. 4 are common, 2 are distinctive, and 8 are very specific to this project.

  • 4

    Common

    Most of the 9 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 8

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Document: - Add comprehensive JSDoc comments for type safety

    line 38
  2. Distinctive:

    Test: - Use Vitest with JavaScript files

    line 39
  3. Very specific:

    Use Composition API with <script setup>

    line 61
  4. Common:

    Use JSDoc comments for type documentation

    line 62
  5. Common:

    Use .mjs extension for ES modules when needed

    line 63
  6. Very specific:

    Document function parameters with @param

    line 64
  7. Very specific:

    Document return types with @returns

    line 65
  8. Very specific:

    Use @typedef for complex object shapes

    line 66
  9. Very specific:

    Use @type annotations for variables

    line 67
  10. Common:

    Follow vue-expert patterns adapted for JavaScript

    line 68
  11. Very specific:

    Use TypeScript syntax (no <script setup lang="ts">)

    line 71
  12. Very specific:

    Use .ts file extensions

    line 72
  13. Very specific:

    Use CommonJS require() in Vue files

    line 74
  14. Common:

    When implementing Vue features in JavaScript:

    line 80

“Common” is measured: kept by at least 6 in 10 of the 9 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 (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:

TopicReferenceLoad When
JSDoc Typingreferences/jsdoc-typing.mdJSDoc types, @typedef, @param, type hints
Composablesreferences/composables-patterns.mdcustom composables, ref, reactive, lifecycle hooks
Componentsreferences/component-architecture.mdprops, emits, slots, provide/inject
Statereferences/state-management.mdPinia, stores, reactive state
Testingreferences/testing-patterns.mdVitest, 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+

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.

Check your setup, free