All skills
hyf0 avatar

/vue-best-practices

@b9d14d0 official
by hyf0hyf0/vue-skills2.9k stars
167

MUST be used for Vue.js tasks. Strongly recommends Composition API with `<script setup>` and TypeScript as the standard approach. Covers Vue 3, SSR, Volar, vue-tsc. Load for any Vue, .vue files, Vue Router, Pinia, or Vite with Vue work. ALWAYS use Composition API unless the project explicitly requires Options API.

Use this Skill: https://skilld.dev/gh/hyf0/vue-skills/vue-best-practices

This session only. Nothing lands on disk.

referencesplugins.md

≈971 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Vue Plugin Best Practices

Impact: MEDIUM - Vue plugins should follow the app.use() contract, expose explicit capabilities, and use collision-safe injection keys. This keeps plugin setup predictable and composable across large apps.

Task List

  • Export plugins as an object with install() or as an install function
  • Use the app instance in install() to register components/directives/provides
  • Type plugin APIs with Plugin (and options tuple types when needed)
  • Use symbol keys (prefer InjectionKey<T>) for provide/inject in plugins
  • Add a small typed composable wrapper for required injections to fail fast

Structure Plugins for app.use()

A Vue plugin must be either:

  • An object with install(app, options?)
  • A function with the same signature

BAD:

const notAPlugin = {
  doSomething() {}
}

app.use(notAPlugin)

GOOD:

import type { App } from 'vue'

interface PluginOptions {
  prefix?: string
  debug?: boolean
}

const myPlugin = {
  install(app: App, options: PluginOptions = {}) {
    const { prefix = 'my', debug = false } = options

    if (debug) {
      console.log('Installing myPlugin with prefix:', prefix)
    }

    app.provide('myPlugin', { prefix })
  }
}

app.use(myPlugin, { prefix: 'custom', debug: true })

GOOD:

import type { App } from 'vue'

function simplePlugin(app: App, options?: { message: string }) {
  app.config.globalProperties.$greet = () => options?.message ?? 'Hello!'
}

app.use(simplePlugin, { message: 'Welcome!' })

Register Capabilities Explicitly in install()

Inside install(), wire behavior through Vue application APIs:

  • app.component() for global components
  • app.directive() for global directives
  • app.provide() for injectable services and config
  • app.config.globalProperties for optional global helpers (sparingly)

BAD:

const uselessPlugin = {
  install(app, options) {
    const service = createService(options)
  }
}

GOOD:

const usefulPlugin = {
  install(app, options) {
    const service = createService(options)
    app.provide(serviceKey, service)
  }
}

Type Plugin Contracts

Use Vue's Plugin type to keep install signatures and options type-safe.

import type { App, Plugin } from 'vue'

interface MyOptions {
  apiKey: string
}

const myPlugin: Plugin<[MyOptions]> = {
  install(app: App, options: MyOptions) {
    app.provide(apiKeyKey, options.apiKey)
  }
}

Use Symbol Injection Keys in Plugins

String keys can collide ('http', 'config', 'i18n'). Use symbol keys with InjectionKey<T> so injections are unique and typed.

BAD:

export default {
  install(app) {
    app.provide('http', axios)
    app.provide('config', appConfig)
  }
}

GOOD:

import type { InjectionKey } from 'vue'
import type { AxiosInstance } from 'axios'

interface AppConfig {
  apiUrl: string
  timeout: number
}

export const httpKey: InjectionKey<AxiosInstance> = Symbol('http')
export const configKey: InjectionKey<AppConfig> = Symbol('appConfig')

export default {
  install(app) {
    app.provide(httpKey, axios)
    app.provide(configKey, { apiUrl: '/api', timeout: 5000 })
  }
}

Provide Required Injection Helpers

Wrap required injections in composables that throw clear setup errors.

import { inject } from 'vue'
import { authKey, type AuthService } from '@/injection-keys'

export function useAuth(): AuthService {
  const auth = inject(authKey)
  if (!auth) {
    throw new Error('Auth plugin not installed. Did you forget app.use(authPlugin)?')
  }
  return auth
}

Source: SKILL.md on GitHub

No alerts16d5 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    This skill provides a comprehensive set of best practices for Vue.js development, focusing on the Composition API, reactivity, and performance optimization. It includes standard coding guidelines and explicitly recommends security best practices such as sanitizing untrusted content to prevent XSS.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: LOW · No issues

  • Runlayer7mo

    23 files scanned · No issues

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at b9d14d0. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 months ago.

Steadyupdated 8 months ago
metadata
{
  "author": "github.com/vuejs-ai",
  "version": "18.0.0"
}
  • Vue
  • TypeScript
  • composition-api
  • vue3
  • best-practices
  • component-design
  • reactivity
  • vite

README badge

README badge for hyf0/vue-skills/vue-best-practices

Provides a structured workflow for Vue 3 development using Composition API with `<script setup>` and TypeScript. Covers component splitting, reactivity patterns, data flow, composables, and optional features like transitions and async components, with performance optimization as a post-functionality pass.

Generated from the current SKILL.md.

Does this skill work with Vue 2 or only Vue 3?
This skill targets Vue 3 with Composition API and `<script setup>`. For Vue 2 or Options API projects, it recommends loading alternative skills if available.
Should I use Options API or Composition API with this skill?
Always use Composition API with `<script setup>` and TypeScript unless the project explicitly requires Options API, in which case you should load the `vue-options-api-best-practices` skill instead.
Does this skill provide reference documentation or just instructions?
The skill includes must-read references covering reactivity, SFC structure, component data flow, and composables that should be kept in active context throughout your work.
When should I add features like slots, Teleport, or Transition?
These optional features should only be loaded when your requirements explicitly call for them. The skill defaults to simpler patterns and treats advanced features as post-functionality additions.
Does this skill require TypeScript?
Yes. The skill strongly recommends TypeScript as part of the standard Composition API + `<script setup>` approach for Vue 3.

Generated from the current SKILL.md. These answers refresh after source changes.