skillbundle
ExploreOfficialAdd skillDashboardPricing
ExploreOfficialAdd skillDashboardPricing
Install
npx skills add ...
Overview
Documentation
  1. Home
  2. vuejs-ai
  3. skills
  4. vue-options-api-best-practices

vue-options-api-best-practices

Compare
Install
npx skills add vuejs-ai/skills --skill vue-options-api-best-practices
Overview
Documentation
Install
npx skills add vuejs-ai/skills --skill vue-options-api-best-practices
Overview

Vue 3 Options API style (data(), methods, this context). Each reference shows Options API solution only.

Also available at

The same skill content is published under more than one repo. The install counts are split across them; any of these commands works.

Other names for this repo

  • hyf0/vue-skillsRenamed2.2k installs

Installs

7.1K
Rank #1,648·+167 past 7d

Repository

vuejs-ai/skills

GitHub stars

2.7k

Updated

Jun 4, 2026

Security

  • Gen Agent Trust Hubpass
  • Socketpass
  • Snykpass
  • Runlayerpass
  • ZeroLeakspass
Documentation

Vue.js Options API best practices, TypeScript integration, and common gotchas.

TypeScript

  • Need to enable TypeScript type inference for component properties → See ts-options-api-use-definecomponent
  • Enabling type safety for Options API this context → See ts-strict-mode-options-api
  • Using old TypeScript versions with prop validators → See ts-options-api-arrow-functions-validators
  • Event handler parameters need proper type safety → See ts-options-api-type-event-handlers
  • Need to type object or array props with interfaces → See ts-options-api-proptype-complex-types
  • Injected properties missing TypeScript types completely → See ts-options-api-provide-inject-limitations
  • Complex computed properties lack clear type documentation → See ts-options-api-computed-return-types

Methods & Lifecycle

  • Methods aren't binding to component instance context → See no-arrow-functions-in-methods
  • Lifecycle hooks losing access to component data → See no-arrow-functions-in-lifecycle-hooks
  • Debounced functions sharing state across component instances → See stateful-methods-lifecycle