Back to catalog
Human reviewedDevelopment

Skill dossier

vue-expert

Source declaration

Builds Vue 3 components with Composition API patterns, configures Nuxt 3 SSR/SSG projects, sets up Pinia stores, scaffolds Quasar/Capacitor mobile apps, implements PWA features, and optimises Vite builds. Use when creating Vue 3 applications with Composition API, writing reusable composables, managing state with Pinia, building hybrid mobile apps with Quasar or Capacitor, configuring service workers, or tuning Vite configuration and TypeScript integration.

The author's original description, preserved in English. It describes intent, not verified performance.

Builds Vue 3 components with Composition API patterns, configures Nuxt 3 SSR/SSG projects, sets up Pinia stores, scaffolds Quasar/Capacitor mobile apps, implements PWA features, and optimises Vite builds. Use when creating Vue 3 applications with Composition API, writing reusable composables, managing state with Pinia, building hybrid mobile apps with Quasar or Capacitor, configuring service workers, or tuning Vite configuration and TypeScript integration.

developmentreferences

Research summary

Human reviewed

Skill Atlas editorial review · editorial-preview-1.0.0

Guides Vue 3 development with the Composition API and script setup, covering Pinia, Nuxt 3, Quasar/Capacitor, PWA and Vite, validated with vue-tsc and Vitest.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Plans component hierarchy, composables and stores.
  • Builds components with script setup, TypeScript props and Pinia state.
  • Runs vue-tsc --noEmit and fixes type errors until clean.
  • Writes component tests with Vue Test Utils and Vitest.

Limitations & scope

  • Mandates Composition API and forbids Options API, so it does not suit legacy Vue 2 code as written.
  • Mobile, PWA and Nuxt details live in reference files that must be loaded.
  • Test and type-check results are not verified here.

Relevant for

  • Vue 3 application developers
  • Teams adopting Pinia and Nuxt 3
  • Developers building hybrid mobile apps with Quasar or Capacitor

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
8
Markdown files
8
scripts
0
references
7
Size
76.3 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/vue-expert/references/build-tooling.mdReference9.4 KB
skills/vue-expert/references/components.mdReference8.8 KB
skills/vue-expert/references/composition-api.mdReference5.8 KB
skills/vue-expert/references/mobile-hybrid.mdReference13.5 KB
skills/vue-expert/references/nuxt.mdReference14.1 KB
skills/vue-expert/references/state-management.mdReference9.6 KB
skills/vue-expert/references/typescript.mdReference10.7 KB
skills/vue-expert/SKILL.mdInstruction4.4 KB

SKILL.md frontmatter

{
  "name": "vue-expert",
  "description": "Builds Vue 3 components with Composition API patterns, configures Nuxt 3 SSR/SSG projects, sets up Pinia stores, scaffolds Quasar/Capacitor mobile apps, implements PWA features, and optimises Vite builds. Use when creating Vue 3 applications with Composition API, writing reusable composables, managing state with Pinia, building hybrid mobile apps with Quasar or Capacitor, configuring service workers, or tuning Vite configuration and TypeScript integration.",
  "license": "MIT",
  "metadata": {
    "author": "https://github.com/Jeffallan",
    "company": "https://synergetic.solutions",
    "version": "1.1.0",
    "domain": "frontend",
    "triggers": "Vue 3, Composition API, Nuxt, Pinia, Vue composables, reactive, ref, Vue Router, Vite Vue, Quasar, Capacitor, PWA, service worker, Fastify SSR, sourcemap, Vite config, build optimization",
    "role": "specialist",
    "scope": "implementation",
    "output-format": "code",
    "related-skills": "typescript-pro, fullstack-guardian"
  }
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Input

    Analyze requirements

    Identify component hierarchy, state needs and routing.

  2. 02
    Action

    Implement with Composition API

    Build components with Composition API and proper reactivity.

  3. 03
    Decision

    Validate types

    Run vue-tsc --noEmit and fix each issue until the output is clean before proceeding.

  4. 04
    Output

    Deliver Vue output

    Provide a script setup component, composable if needed, Pinia store if needed, and reactivity notes.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

325 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useObserved
Medium

Network access is mentioned

33 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 33 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

287 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 287 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Credential or secret material is referenced

4 occurrences

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 4 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

File deletion is described or implemented

Deletion syntax occurs in this line, including possible documentation. Review its exact target, recursive scope, and safeguards. The analyzer did not execute it. This rule matched 1 location(s) in the collected text; 1 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Editorial security note

Review service worker, Capacitor and SSR configuration the agent generates, since they affect caching and runtime permissions.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
git clone https://github.com/Jeffallan/claude-skills.git cd claude-skills # Copy this skill directory into one of: # ~/.claude/skills/vue-expert # .claude/skills/vue-expert
  1. Open the pinned source at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/vue-expert/SKILL.md.
  2. Review the license, prerequisites and all bundled reference files.
  3. Copy the skill directory into a personal or project-level Claude Code skills directory.
  4. Restart or refresh Claude Code so the skill can be discovered.
Verify installation

Confirm SKILL.md is discoverable at the destination, then ask Claude Code to use vue-expert on a small task.

Prerequisites

  • Mandates Composition API and forbids Options API, so it does not suit legacy Vue 2 code as written.
  • Mobile, PWA and Nuxt details live in reference files that must be loaded.
  • Test and type-check results are not verified here.

Example prompts

Representative task

Use the vue-expert skill to build a TypeScript script setup component with a Pinia-backed cart store and a reusable composable, then run vue-tsc --noEmit and add Vitest tests.

Inspect before use

Read the vue-expert skill at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/vue-expert/SKILL.md. Explain its workflow, required tools, permissions and the main risks before I decide whether to install it.

A decision, with its limits attached

Strengths

  • Clear reactivity rules, such as ref for primitives and computed for derived state.
  • Validation steps for type checking and testing with fix-and-rerun loops.

Considerations

  • Skill scope is wide, from Nuxt SSR to mobile PWA, so depth depends on reference loading.
  • Strict TypeScript preference may not fit JavaScript-only projects; see the vue-expert-js sibling.
Research conclusion

A dependable default for modern Vue 3 TypeScript projects that follow the Composition API.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

Jeffallanclaude-skillsskills/vue-expert
Source type
Community
Commit
67c1961b180dc92cf08983344627109e983e8f51
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
MIT
Repository stars
12,464
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.