domains / families / software-engineering / vue-best-practices

vue-best-practices

combined

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.

When to use

• Vue.js tasks
• Vue 3
• SSR
• Volar
• vue-tsc
• .vue files
• Vue Router
• Pinia

When not to use

• Options API unless project explicitly requires it

Skill page

Conflict

The two copies are different generations of the same skill. The first (v18) is a high-level workflow that mandates reading specific reference files (reactivity.md, sfc.md, etc.) and planning component boundaries before coding. The second (v17) is a detailed index of specific 'gotchas' and performance optimizations (e.g., ref-value-access, computed-no-side-effects) with its own set of reference files. The v18 copy lacks the granular troubleshooting index of v17, while v17 lacks the explicit architectural planning workflow of v18. Combining them provides both the structural workflow and the detailed technical reference list.