← LeaderboardThe Skill Leaderboard

vue-options-api-best-practices

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

Description awaits a fresh source check.

Published by vuejs-ai ↗vuejs-ai/skills

Try your first task

Start a fresh conversation. Replace the highlighted placeholders.

Use vue-options-api-best-practices to refactor [Vue component] to Vue 3 Options API, addressing [TypeScript requirement] while preserving [current behavior].

Required inputs

[Vue component]
[TypeScript requirement]
[current behavior]

User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗

SKILL.md

name: vue-options-api-best-practicesdescription: "Vue 3 Options API style (data(), methods, this context). Each reference shows Options API solution only."version: 2.0.0license: MITauthor: github.com/vuejs-ai

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