vue-best-practices

Enforce Vue 3 prop, emit, and template typing practices across components.

Updated Jan 22, 2025
One-click install
npx skills add https://github.com/lafllamme/personal-page --skill vue-best-practices-lafllamme
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: vue-best-practices
Source: https://github.com/lafllamme/personal-page/tree/main/.cursor/skills/vue-best-practices
Command: npx skills add https://github.com/lafllamme/personal-page --skill vue-best-practices-lafllamme

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Vue development often suffers from inconsistent typing across components, leading to runtime errors and costly refactors.

Core Features & Use Cases

  • Enforces correct prop/emit/types across Vue 3 components.
  • Guides wrapper component typing and template checks with Volar/vue-tsc.
  • Use case: migrating a large Vue 2 project to Vue 3 with strong type safety.

Quick Start

Review your Vue components to ensure prop typings and template checks are aligned, then enable vue-tsc and Volar configurations across the project.

Frequently Asked Questions about vue-best-practices

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce Vue 3 component typing best practices for props and emits?β–Ό

Vue-tsc and Volar provide accurate template type checking for Vue 3 components by validating prop, emit, and slot typings, preventing runtime errors during component development and refactoring.

What is the best way to configure Volar for accurate template type checking in Vue 3?β–Ό

Configuring Volar for template type checking involves aligning your component prop typings with vue-tsc settings to accurately validate emits, slots, and wrapper components across the project.

Can I use vue-tsc to type check wrapper components and slots in Vue 3?β–Ό

Yes, vue-tsc can type check wrapper components and slots by enforcing correct Vue 3 typing practices, ensuring that all component interfaces satisfy strict type safety guidelines during refactoring.

Does Vue 3 TypeScript typing support migrating a large Vue 2 project with strong type safety?β–Ό

Vue 3 TypeScript typing supports migrating large Vue 2 projects by enforcing consistent prop and emit typings across components, which reduces runtime errors and costly refactors during the transition.

Why does my Vue 3 template type checking fail with inconsistent component typings?β–Ό

Vue 3 template type checking fails when components have inconsistent typing practices, but enabling vue-tsc and Volar configurations enforces correct prop and emit typings to resolve these validation errors.